| ... | ... | @@ -62,7 +62,8 @@ One level of hierarchy (e.g. *region*) may contain any number of *terminate pseu |
|
|
|
The overall execution of the state machine is discontinued, if one *terminate pseudostates* at any level is reached.
|
|
|
|
|
|
|
|
# Obligations for the lectures and the final exam in "Softwaretechnik" (Tips for Modeling)
|
|
|
|
When creating a **state machine diagram**, remember that it must contain all necessary information (states, activities, actions, transitions, events, guards, and triggers). Otherwise this type of diagram is useless and can be thrown away. Especially for transitions between states it is important to specify the relevant triggers, guards, and behaviors.
|
|
|
|
When creating a **state machine diagram**, remember that it must contain all necessary information (e.g. states, transitions, triggers, guards and effects).
|
|
|
|
Especially for transitions between states it is important to specify the relevant triggers, guards, and behaviors.
|
|
|
|
An example class diagram is shown in [Example State Machine Diagram](#an-example-state-machine-diagram-for-the-given-scenario).
|
|
|
|
|
|
|
|
# What is a State?
|
| ... | ... | |
