The State Machine Diagram models the behavior of a system by describing the various states an object may be in, and the transitions between those states. They are generally used to describe the behavior of an object spanning several use cases.
Two types of processes can achieve this:
1.Actions, which are associated to transitions, are short-term processes that cannot be interrupted (for example, internal error /notify admin in the diagram below)
2.State Activities (behaviors), which are associated to states, are longer-term processes that may be interrupted by other events (for example, listen for incoming connections, in the diagram below).
A state machine can have any number of State Machine Diagrams (or State Diagrams) in UModel.
Sample State Machine diagram
The State machine diagram illustrated above is available in the following sample UModel project: C:\Users\<username>\Documents\Altova\UModel2020\UModelExamples\Bank_MultiLanguage.ump.