Difference between revisions of "State"
| Line 37: | Line 37: | ||
{{Supplementary Figures | {{Supplementary Figures | ||
|Figure Row={{Figure Row | |Figure Row={{Figure Row | ||
| − | |Figure=Act-1.png | + | |Figure=Act-1.png |
|Caption=Figure 1: A generic activity cluster. | |Caption=Figure 1: A generic activity cluster. | ||
}}{{Figure Row | }}{{Figure Row | ||
| − | |Figure=Act-2.png | + | |Figure=Act-2.png |
|Caption=Figure 2: Example use of the Activity Ontology. | |Caption=Figure 2: Example use of the Activity Ontology. | ||
}} | }} | ||
}} | }} | ||
Revision as of 21:58, 3 July 2021
Pattern
This class has been associated with the following pattern:
Subclass Of
Description
An English description of the definition (what distinguishes this sense of the term?).
A state specifies some snapshot of objects in the domain as they exist at some point in time.
Class Diagram Description
An activity cluster provides a basic structure for representing activity specifications. Illustrated in Figure 1, it consists of an activity connected to an enabling and caused state, each of which may be a state tree that defines complex states via decomposition into conjunctions and disjunctions of states.
Figure 2 illustrates the use of the Activity Ontology to describe a class of objects that should be identified as “Drive to Work” activities, where the effect of such an activity is a Conjunctive state. The conjunctive state is decomposed into two terminal states, meaning that it should be interpreted as a state where both sub-states (DriverAtWork and CarAtWork) are true.
Required by Use Case(s)
(why is this specialized definition needed?)
CDM References
What other classes or properties reference this term?
- ISO5087-1:Activity (← links)
- TerminalState (← links)
- NonTerminalState (← links)
- RecurringEvent (← links)
- ISO5087-1:Allocation (← links)
- Goal (← links)
- Pattern:Activity Pattern (← links)
Interface Specification References
This class has been associated with the following interface specification items:
Sources
Sources considered when developing the class:
Status
Pending Approval
Has Subclass(es)
Annotations
| Annotation | Value |
|---|
Manchester Syntax Specification
| Property | Restriction | Value |
|---|---|---|
| PreconditionOf | only | Activity |
| Enables | only | Activity |
| EffectOf | only | Activity |
| CausedBy | only | Activity |
| ScheduledFor | max 1 | TemporalEntity |
| HasStatus | exactly 1 | StateStatus |
Supplementary Figures
| Figure | Caption |
|---|---|
| Figure 1: A generic activity cluster. | |
| Figure 2: Example use of the Activity Ontology. |
