In the following BDD fragment and StateMachine setup, if the state machine is initialised and in inner 'StateA', how many times will "Enter InnerComposite" be printed after responding to the following signal events: 'ToInner', '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 'ToInner' is received the state machine will enter state 'InnerComposite', so the entry Behavior of 'InnerComposite' will print "Enter InnerComposite". Then 'DeepStateA' is entered (which will print "Enter DeepStateA"). When 'AtoB' is received the state machine will enter 'DeepStateB' (and print "Enter DeepStateB"). When signal 'LeaveComposite' and then 'ToHistory' are received, the deep history will direct the state machine to RE-ENTER 'DeepStateB' VIA both 'Composite' and 'InnerComposite', so the entry Behavior of 'InnerComposite' is invoked and "Enter InnerComposite" 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 with deferred Signal event Trigger [with mini video]

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] Deep history (deepHistory) represents the full state configuration of the most recent visit to the containing Region.

[UML-2.5.1] The effect is the same as if the Transition terminating on the deepHistory Pseudostate had, instead, terminated on the innermost State of the preserved state configuration, including execution of all entry Behaviors encountered along the way.

Related slides (includes other tutorials)

Pseudostates - deepHistory and shallowHistory