Submissions:Criterion
From Odp
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 10867 |
Graphical representation
Diagram
General description
| Name: | Criterion |
|---|---|
| Submitted by: | PiotrNowara |
| Also Known As: | |
| Intent: | The purpose of this pattern is to provide a basis for criteria modeling. For more advanced use see the 'criterion setter' pattern that enables describing entities that define criteria (such as requirements, constraints etc.). |
| Domains: | |
| Competency Questions: |
|
| Solution description: | The criterion is defined as a subclass of description. 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: | http://criteria-modeling.googlecode.com/svn/trunk/criterion.owl (1023) |
| Consequences: | |
| Scenarios: | |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
Elements
The Criterion Content OP locally defines the following ontology elements:
Additional information
See also: http://code.google.com/p/requirement-ontology/
Scenarios
Scenarios about Criterion
No scenario is added to this Content OP.
Reviews
Reviews about Criterion
There is no review about this proposal. This revision (revision ID 10867) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
Modeling issues about Criterion
There is no Modeling issue related to this proposal.
References
