Last modified date is: 2011-10-10

Graphical representation

Diagram

General description

Name:	CriterionSetter
Submitted by:	PiotrNowara
Also Known As:
Intent:	The purpose of this pattern is to provide a broader context for criteria modeling. Possible specializations could introduce new kinds of criteria setters representing criteria in detailed contexts (for example: a pattern for describing the success/failure condition for some actions). Possible criteria setters may include requirements, recommendations, constraints etc.
Domains:	General
Competency Questions:	What defines this criterion? Are there any criterion setters that determine this thing (or this domain)? What criterion is defined by given criterion setter? What domains (and/or domain objects) are affected by a given criterion setter (for example by a requirement)?
Solution description:	This is a specialization of criterion pattern. The criterion setter can be used as an abstract container for requirements, recommendations, constraints etc. The owl file linked below contains a simple example of how this pattern could be implemented for modeling a requirement (see 'Examples').
Reusable OWL Building Block:	1 (935)
Consequences:
Scenarios:
Known Uses:
Web References:
Other References:
Examples (OWL files):	http://criteria-modeling.googlecode.com/svn/trunk/criterion_example_1.owl
Extracted From:
Reengineered From:
Has Components:
Specialization Of:	Submissions:Criterion
Related CPs:	Submissions:DescriptionAndSituation

The CriterionSetter Content OP locally defines the following ontology elements:

Scenarios about CriterionSetter

No scenario is added to this Content OP.

Reviews about CriterionSetter

There is no review about this proposal.

Some subquery has no valid condition.

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

Modeling issues about CriterionSetter

There is no Modeling issue related to this proposal.

Some subquery has no valid condition.