Pseudostates - deepHistory and shallowHistory

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
ADVANCED
UML keywords
StateMachine
StateMachine Diagram
State
Transition
Vertex
PseudostateKind
PseudostateKind::shallowHistory
PseudostateKind::deepHistory
Keywords
Slide kind
UML StateMachine Diagram
This content has been marked as discussing an ADVANCED topic!
NOTATION REFERENCE ONLY: This diagram is not meant to be executable!
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.
Click on the image to view it full size
Up next
Transitions
Notes
Snippets (quotes/extracts)
  [UML-2.5.1] deepHistory – This type of Pseudostate is a kind of variable that represents the most recent active state configuration of its owning Region. ... a Transition terminating on this Pseudostate implies restoring the Region to that same state ...
  [UML-2.5.1] deepHistory – ... The entry Behaviors of all States in the restored state configuration are performed in the appropriate order starting with the outermost State
  [UML-2.5.1] A deepHistory Pseudostate can only be defined for composite States and, at most one such Pseudostate can be contained in a Region of a composite State.
  [UML-2.5.1] shallowHistory – ... this type of Pseudostate is a kind of variable that represents the most recent active substate of its containing Region, but not the substates of that substate. A Transition terminating on this Pseudostate implies rest
  [UML-2.5.1] shallowHistory – ... A single outgoing Transition from this Pseudostate may be defined terminating on a substate of the composite State. This substate is the default shallow history state of the composite State.
  [UML-2.5.1] shallowHistory Pseudostate can only be defined for composite States and, at most one such Pseudostate can be included in a Region of a composite State.
  [UML-2.5.1] In cases where a Transition terminates on a history Pseudostate when the State has not been entered before (i.e., no prior history) or it had reached its FinalState, there is an option to force a transition to a specific substate, using the default ...
  [UML-2.5.1] This is a Transition that originates in the history Pseudostate and terminates on a specific Vertex (the default history state) of the Region containing the history Pseudostate. This Transition is only taken if execution leads to the history Pseudostate a
  [UML-2.5.1] Otherwise, the appropriate history entry into the Region is executed (see above). If no default history Transition is defined, then standard default entry of the Region is performed ....
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY
Related slides (backlinks, includes other tutorials)