Diagram
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: | 1 (565) |
Consequences: | |
Scenarios: | |
Known Uses: | |
Web References: | |
Other References: | |
Examples (OWL files): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
The Criterion Content OP locally defines the following ontology elements:
No scenario is added to this Content OP.
This revision (revision ID 10334) takes in account the reviews: none
Other info at evaluation tab