PiotrNowara (Talk | contribs) m |
PiotrNowara (Talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
|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. | |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. | ||
|Domain=General, | |Domain=General, | ||
| − | |CompetencyQuestion=Are there any criterion setters that determine this thing (or this domain)?, What criterion is defined by given criterion setter | + | |CompetencyQuestion=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)? |
|ContentODPDescription=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'). | |ContentODPDescription=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'). | ||
|ReusableOWLBuildingBlock=http://criteria-modeling.googlecode.com/svn/trunk/criterion_setter.owl | |ReusableOWLBuildingBlock=http://criteria-modeling.googlecode.com/svn/trunk/criterion_setter.owl | ||
| Line 18: | Line 18: | ||
{{Element list header}} | {{Element list header}} | ||
{{Additional information header}} | {{Additional information header}} | ||
| − | + | See also: http://code.google.com/p/requirement-ontology/ | |
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
{{Modeling issues about me}} | {{Modeling issues about me}} | ||
{{My references}} | {{My references}} | ||
|
Last modified date is: 2011-10-10 |
Diagram
| 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: | |
| Competency Questions: | |
| 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): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The CriterionSetter Content OP locally defines the following ontology elements:
See also: http://code.google.com/p/requirement-ontology/
No scenario is added to this Content OP.
This revision (revision ID 10866) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
