| ... | ... | @@ -6,7 +6,7 @@ |
|
|
|
# Usage Scenarios
|
|
|
|
The **state machine diagram** is used to illustrate the life-cycle of single objects and the behavior of operations within a software system.
|
|
|
|
This kind of diagram can be greatly used to get a detailed understanding of the behavior of objects, conditions and flows within the overall system.
|
|
|
|
For example, you can use it in the early design phase of a new software system to model the behavior of a specific component to describe it's workflow. Especially, when the behavior of an object (lifecycle) or operation is not well understood yet.
|
|
|
|
For example, you can use it in the early design phase of a new software system to model the behavior of a specific component to describe its workflow. Especially, when the behavior of an object (lifecycle) or operation is not well understood yet.
|
|
|
|
|
|
|
|
# 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.
|
| ... | ... | |
