Using submachines

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
State::/isSubmachineState
submachine
PseudostateKind::entryPoint
PseudostateKind::exitPoint
Transition::effect
State::submachine
State::containingStateMachine()
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
The entry, doActivity, and effect Behaviors defined on a submachine State are specific that particular usage of its Submachine
The absence of explicit triggers or guards on Transition symbols in this diagram is for brevity only and does not imply completion Transitions with implicit triggers.
Up next
Pseudostates - initial, fork, join, terminate
Notes
[ASSERTION] The entry, doActivity, and effect Behaviors defined on a submachine State are specific that particular usage of its Submachine
Snippets (quotes/extracts)
  [UML-2.5.1] Submachines are a means by which a single StateMachine specification can be reused multiple times. They are similar to encapsulated composite States in that they need to bind incoming and outgoing Transitions to their internal Vertices.
  [UML-2.5.1] A submachine StateMachine can be entered via its default (initial) Pseudostate or via any of its entry points (i.e., it may imply entering a non-orthogonal or an orthogonal composite State with Regions). Entering via the initial Pseudostate ...
  [UML-2.5.1] An entry point is equivalent to a junction Pseudostate (fork in cases where the composite State is orthogonal): Entering via an entry point implies that the entry Behavior of the composite state is executed, followed by the Transition from the entry ...
  [UML-2.5.1] NOTE. Each submachine State represents a distinct instantiation of a submachine, even when two or more submachine States reference the same submachine.
  [UML-2.5.1] The entry, exit, and effect Behaviors and internal Transitions are defined as contained in the submachine State.
  [UML-2.5.1] The concept of ConnectionPointReference is provided to support binding between the submachine State and the referenced StateMachine.
  [UML-2.5.1] A ConnectionPointReference represents a point on the submachine State at which a Transition either terminates or originates. That is, they serve as targets for incoming Transitions to submachine States, as well as sources for outgoing Transitions ...
  [UML-2.5.1] Each ConnectionPointReference is matched by a corresponding entry or exit point in the referenced submachine StateMachine. This provides the necessary binding mechanism between the submachine invocation and its specification.
Visit also
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)