State configurations Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:03: UML Behavior: StateMachines quick start Slide kind UML StateMachine Diagram
Kinds of States Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:03: UML Behavior: StateMachines quick start Slide kind UML StateMachine Diagram
uml101 - StateMachines - NOTATION REFERENCE CARD Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:03: UML Behavior: StateMachines quick start Slide kind UML StateMachine Diagram
A FinalState has no entry, doActivity, or exit Behavior, no outgoing Transitions, no Regions, and cannot reference a submachine
14.5.2 FinalState ... If the enclosing Region is directly contained in a StateMachine and all other Regions in that StateMachine also are completed, then it means that the entire StateMachine behavior is completed. Source Unified Modeling Language 2.5.1
14.5.2 FinalState - A special kind of State, which, when entered, signifies that the enclosing Region has completed. Source Unified Modeling Language 2.5.1
StateMachine for the Dialer class Gallery Tutorial HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study Section Slide kind UML StateMachine Diagram
14.2.3.6 FinalState: FinalState is a special kind of State signifying that the enclosing Region has completed. Thus, a Transition to a FinalState represents the completion of the behaviors of the Region containing the FinalState. Source Unified Modeling Language 2.5.1
a submachine Statemachine can be exited as a result of: reaching its FinalState; triggering of a group Transition originating from a submachine State, or; via any of its exit points. Source Unified Modeling Language 2.5.1