SysMLv1: Cameo Simulation Toolkit: Activity & StateMachine simulation: relative TimeEvent triggers, Transitions & doActivity [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
Activity
CallBehaviorAction
Trigger::event
TimeEvent::isRelative
TimeEvent
State
Transition
Trigger
Transition::trigger
Keywords
Slide kind
SysML Activity Diagram
SysML Block Definition Diagram (BDD)
SysML StateMachine Diagram
In the following Block, Activity, and StateMachine setup and according to the shown TimeEvents will “Done Second” ever be printed?
Click on the image to view it full size
Watch simulation
Watch a high resolution version of the video on Vimeo.
An 'isRelative' TimeEvent will trigger the Transition from state 'Second' to state 'Escaped' before the doActivity 'DoSecond' (which may be interrupted by a Transition) can print “Done Second”.
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 shallowHistory Pseudostate [with mini video]
Notes
Snippets (quotes/extracts)
  [UML-2.5.1] terminate – Entering a terminate Pseudostate implies that the execution of the StateMachine is terminated immediately. The StateMachine does not exit any States nor does it perform any exit Behaviors. Any executing doActivity Behaviors are ... aborted
  [UML-2.5.1] ... if a doActivity Behavior is defined for the State, this Behavior commences execution immediately after the entry Behavior is executed. It executes concurrently with any subsequent Behaviors associated with entering the State, such as the entry ...
  [UML-2.5.1] If the State has a doActivity Behavior that is still executing when the State is exited, that Behavior is aborted before the exit Behavior commences execution.
Related slides (includes other tutorials)
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