Submissions:Complaint Design Pattern Revision as of 10:52, 3 May 2016 by CristianaSantos (Talk | contribs) (Imported from OWL file.) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

Last modified date is: 2016-05-03

Graphical representation

Diagram (this article has no graphical representation)

General description

Name:	COP
Submitted by:	CristianaSantos
Also Known As:
Intent:	To represent the core constituents of a complaint
Domains:
Competency Questions:	What is the claim of the complainant? Which facts happened in 'this' date or in 'this' place? Who is involved in this complaint? Who is the complaint recipient? What motivates the complaint? Which facts describe the complaint? What evidences are used to prove the narrated fact? Which medium was used to express the complaint?
Solution description:
Reusable OWL Building Block:	1 (0)
Consequences:	Heterogeneous models for complaints can be aligned to this pattern, which then acts as a semantic facade to different complaint management applications (such as complaint handling process, customer complaint management, customer relation management)
Scenarios:	A complaint refers to the narrated facts of an agent, grounded with motive and a request, through a specific medium (used to generate the complaint document), where evidence may support the facts.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:

Elements

The Complaint Design Pattern Content OP locally defines the following ontology elements:

Submissions:Complaint Design Pattern/basedOn

basedOn page

Submissions:Complaint Design Pattern/expressedIn

expressedIn page

Submissions:Complaint Design Pattern/hasComplaintMotivation

hasComplaintMotivation page

Submissions:Complaint Design Pattern/hasRequest

hasRequest page

Submissions:Complaint Design Pattern/hasRole

hasRole page

Submissions:Complaint Design Pattern/justifiedBy

justifiedBy page

Submissions:Complaint Design Pattern/madeBy

madeBy page

Submissions:Complaint Design Pattern/supportedBy

supportedBy page

Submissions:Complaint Design Pattern/hasSpace

hasSpace page

Submissions:Complaint Design Pattern/hasStampTime

hasStampTime page

Submissions:Complaint Design Pattern/hasTimeOccurrence

hasTimeOccurrence page

Submissions:Complaint Design Pattern/Agent

Agent page

Submissions:Complaint Design Pattern/Complainant

Complainant page

Submissions:Complaint Design Pattern/Complaint

Complaint page

Submissions:Complaint Design Pattern/Complaint Recipient

Complaint_Recipient page

Submissions:Complaint Design Pattern/Evidence

Evidence page

Submissions:Complaint Design Pattern/Fact

Fact page

Submissions:Complaint Design Pattern/Medium

Medium page

Submissions:Complaint Design Pattern/Motivation

Motivation page

Submissions:Complaint Design Pattern/Request

Request page

Submissions:Complaint Design Pattern/ThirdParty

ThirdParty page

Scenarios

Scenarios about Complaint Design Pattern

No scenario is added to this Content OP.

Reviews

Reviews about Complaint Design Pattern

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 12491) takes in account the reviews: none

Other info at evaluation tab

Modeling issues

Modeling issues about Complaint Design Pattern

There is no Modeling issue related to this proposal.

Some subquery has no valid condition.

References

Add a reference