NonTerminalState

Pattern

This class has been associated with the following pattern:

Pattern:Activity Pattern

Subclass Of

State

Description

An English description of the definition (what distinguishes this sense of the term?).

A non-terminal state has child states, which may define some classes of manifestations, or further define some other complex state types. A state cannot be both non-terminal and terminal.NonTerminalStates have the following core properties: o hasDecomp: identifies two or more States that the state may be immediately decomposed into, i.e., its direct children.

NonTerminalState has the following supplemental properties: o hasSubState: identifies a state that the complex state decomposes into, at any level (i.e., its child state, grandchild state, etcetera). The hasSubState property is transitive and a super-property of the hasDecomp property.

Required by Use Case(s)

(why is this specialized definition needed?)

CDM References

What other classes or properties reference this term?

• TerminalState ‎ (← links)
• ISO5087-1:DisjunctiveState ‎ (← 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

Annotations

Annotation	Value

Manchester Syntax Specification

Property	Restriction	Value
disjointWith		TerminalState
HasDecomp	only	State and min 2 State
HasSubState	only	State

Supplementary Figures

Figure	Caption