A state represents a distinct context for the behavior of an object. A state can be active or inactive during execution. A state becomes active when it is entered as a result of a transition, and becomes inactive if it is exited as a result of a transition. A state can be exited and entered as a result of the same transition (referred to as self-transition).
|
State |
Description |
|
A composite state is a state with one or more regions. | |
|
Completion of a region. | |
|
simple state |
A state that does not have regions or hierarchy. For clarity, it is referred to as a simple state. |
|
A submachine contains nested states. The submachine lets you divide a complex start chart into subsystems. |
A pseudostate refers to any element in the state chart that is not occupied for any duration. Pseudostates are typically used to connect transitions into more complex state transition paths.
|
Pseudostate |
Description |
|
Splits transition into multiple paths | |
|
Represents the most recent active configuration of the composite state | |
|
Allow connections from a state to a submachine state | |
|
Allows entry into multiple regions of a composite state | |
|
Represents the most recent active substate of its containing state | |
|
Represents the source for a single transition | |
|
Exits multiple regions of a composite state | |
|
Chains together multiple transitions | |
|
Causes the state chart to terminate all execution |