CCFORM Logo

 

 

Home Ontology Design Downlaod Documentation Contact Person

 

Valid XHTML 1.1!

Customer Complaint Ontology

The "Complaint Problems" module

Final Draft 21 May 2005


The diagram below shows the Complaint Problems module. It represents a taxonomy of the most common complaint problems. As shown below, we distinguish between a ‘Complaint’ and a ‘Problem’. A ‘Complaint’ describes one or more ‘Problems’. While the concept ‘Problem’ is defined as “A source of difficulty or dissatisfaction”, the concept ‘Complaint’ is defined as “An expression of grievance or resentment issued by a complainant against a compliant-recipient, describing a problem(s) that needs to be resolved”.

For the definition of each vocabulary in this diagram please see the CC-Glossary. Notice that according to our ontology design, each relation in this diagram is a lexon in the CC-Lexons; this methodological principle is called Ontology double-articulation.

This module is represented using the ORM graphical notation. The verbalization (i.e. the pseudo-natural-language reading) of the rules in this diagram, and the ORM markup (i.e. the XML-based serialization) of this diagram can be found below.

Diagram:

ORM representation

Verbalization:

Each Purchase Phase Problem must has at least one Contract. (Mandatory)
Each Post-purchase Phase Problem must has at least one Contract. (Uniqueness)
Each Purchase Phase Problem must has at most one Contract. (Uniqueness)
Each Post-purchase Phase Problem must has at most one Contract. (Uniqueness)
Each Problem should be either Non-Contract Problem or Contract Problem. (Exclusive)
Each Contract Problem should be either Post-purchase Phase Problem or Pre-purchase Phase Problem. (Exclusive)

ORM Markup: