Revision as of 10:59, 3 May 2016 (view source) CristianaSantos (Talk | contribs) ← Older edit		Revision as of 15:33, 1 June 2016 (view source) CristianaSantos (Talk | contribs) m (Article is waiting for review.) Newer edit →
Line 84:		Line 84:
	{{Modeling issues about me}}		{{Modeling issues about me}}
	{{My references}}		{{My references}}
		+	[[Category:Waiting for review]]

---

Revision as of 15:33, 1 June 2016

Graphical representation

Diagram

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:	The solution is implemented as an OWL file
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:

Additional information

Scenarios

Reviews

Modeling issues

References

Add a reference