SysMLv1: Cameo Simulation Toolkit: StateMachine shallowHistory Pseudostate [with mini video]

Gallery
Tutorial
TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]
Section
Topic level
ESSENTIAL
UML keywords
Trigger::event
State
Transition
Trigger
Transition::trigger
PseudostateKind::shallowHistory
Keywords
Slide kind
SysML Block Definition Diagram (BDD)
SysML StateMachine Diagram
UML2.5.1: 'Shallow history (shallowHistory) represents a return to only the topmost substate of the most recent state configuration, which is entered using the default entry rule.'
In the following BDD fragment and StateMachine setup, if the state machine is initialised and in inner 'StateA', how many times will "Enter B" be printed after responding to the following signal events: 'AtoB', 'LeaveComposite', 'ToHistory'?
Click on the image to view it full size
Watch simulation
Watch a high resolution version of the video on Vimeo.
When signal 'AtoB' is received the state machine will enter inner 'StateB' and print "Enter B". When signal 'LeaveComposite' and then 'ToHistory' are received, the shallow history will direct the state machine to RE-ENTER the 'StateB', so the entry Behavior is invoked and "Enter B" is printed a 2nd time.
We are offering a 30% discount off all SysML/MBSE course bookings secured by 31st March 2025! Contact us now to apply!
Up next
SysMLv1: Cameo Simulation Toolkit: StateMachine deepHistory Pseudostate [with mini video]
Notes
Snippets (quotes/extracts)
  [UML-2.5.1] Shallow history (shallowHistory) represents a return to only the topmost substate of the most recent state configuration, which is entered using the default entry rule.
  [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.
Related slides (includes other tutorials)
Pseudostates - deepHistory and shallowHistory
SysMLv1: Cameo Simulation Toolkit: HOWTO send a Signal via a Port to an intended recipient via a mediating secure RoutingHub [with mini video]
UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY
StateMachines - simplified metaclass hierarchy
Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity
SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: TimeEvent on Transition [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: StructuredActivityNode with AcceptEventAction + TimeEvent [with mini video]
Related slides (backlinks, includes other tutorials)
Visit also
Course: Model-Based Systems Engineering with the OMG's Systems Modeling Language® (v1) and the MagicDraw/Cameo (CATIA Magic™) tools for SysML
TRAIL: UML Behavior: Activities and Actions
01:04: UML Behavior: Activities quick start
UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY
UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY
Semantics of a Foundational Subset for Executable UML Models 1.4
UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY
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
Section: SysML-1.6 specification diagrams: 13 StateMachines
Visit also (backlinks)
External links
HIGH RESOLUTION version on Vimeo