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
Topic level
ESSENTIAL
UML keywords
StateMachine
StateMachine Diagram
State
Transition
PseudostateKind::initial
PseudostateKind::choice
PseudostateKind::fork
FinalState
submachine
State::/isSubmachineState
Region
orthogonal Region
composite State
State::/isComposite
State::/isOrthogonal
State::/isSimple
state configuration
valid state configuration
Keywords
Slide kind
UML StateMachine Diagram
NOTATION REFERENCE ONLY: This diagram is not meant to be executable!
Click on the image to view it full size
Up next
Effect, Entry, Do, Exit
Notes
Snippets (quotes/extracts)
  [UML-2.5.1] In general, a StateMachine can have multiple Regions, each of which may contain States of its own, some of which may be composites with their own multiple Regions, etc.
  [UML-2.5.1] Consequently, a particular “state” of an executing StateMachine instance is represented by one or more hierarchies of States, starting with the topmost Regions of the StateMachine and down through the composition hierarchy to the simple, or leaf, States.
  [UML-2.5.1] Similarly, we can talk about such a hierarchy of substates within a composite State. This complex hierarchy of States is referred to as a state configuration (of a State or a StateMachine).
  [UML-2.5.1] For example, one valid state configuration for an execution of the StateMachine depicted in Figure 14.9 is: <CourseAttempt - Studying – (Studying::Lab2, Studying::TermProject, Studying::FinalTest)>.
  [UML-2.5.1] An executing StateMachine instance can only be in exactly one state configuration at a time, which is referred to as its active state configuration.
  [UML-2.5.1] StateMachine execution is represented by transitions from one active state configuration to another in response to Event occurrences that match the Triggers of the StateMachine.
  [UML-2.5.1] A State is said to be active if it is part of the active state configuration.
Visit also
Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: StateMachine with entry Activity and Transition guard
Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: StateMachine with doActivity and a Transition with a ChangeEvent trigger
Screencast: Tutorial: UML/SysML: StateMachines vs Activities: Operation-driven Transition case study - UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit
StateMachine diagram for comparing action language access to an operation for a guard
HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study
Visit also (backlinks)
Related slides (includes other tutorials)
UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY
StateMachine diagram for comparing action language access to an operation for a guard
Overview: Controller class (and its Activity), Dialer Class (and its StateMachine), Number class
StateMachine for the Dialer class
Behavior StateMachines can be used to specify any of the following
The number.append Activity as entry Behavior for the PartialDial State
The number.print Activity as exit Behavior for the PartialDial State
Figure D.8 - Finite State Machine Associated with “Drive the Vehicle”
Figure 13-1: Block definition diagram with state machines as blocks associated with submachines and types of parameters
Related slides (backlinks, includes other tutorials)