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

Icon class
icon_class
fas fa-film
icon_class_computed
fas fa-film
UML keywords
Operation
CallOperationAction
AcceptEventAction
StateMachine
State
Transition
Transition::guard
ActivityEdge::guard
composite State
Keywords

Video style

This video accompanies this detailed tutorial trail: HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study.

This full length tutorial is a case study of the telephone dialer StateMachine shown in 'Figure 14.7 Composite State with two States' of the UML-2.5.1 specification. The StateMachine is simulated in Cameo Systems Modeler®, together with a small ecosystem of Classes and Activities, to show also how Activities can be used as supporting entry and exit Behaviors of StateMachines.

Uses Cameo Systems Modeler® for MagicDraw® UML and the MD SysML Plugin (also bundled with Cameo Systems Modeler®). Also employs the Action Language for Foundational UML (Alf) - which requires an additional Alf Plugin - to access Operations on some Transition guards. An Appendix illustrates how to use the vendor-specific Action Language Helper (ALH) APIs in place of Alf to access Operations on Transition guards.

Uses Unified Modeling Language (UML®) model diagrams, but is equally applicable to Systems Modeling Language (SysML®).

© Copyright 2020 Darren R C Kelly (Webel IT Australia). All rights reserved.

Visit also
UML and SysML training seminars and workshops
UML zone
Cameo Simulation Toolkit (CST) zone
Course: Model-based systems engineering with the OMG's Systems Modeling Language (SysML®) and the SysML Plugin for MagicDraw® and Cameo™
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: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: Send and receive a Signal using a SendSignalAction and an AcceptEventAction
Visit also (backlinks)
Screencast: UML/SysML: HOWTO Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity
Screencast: UML/SysML StateMachines: How a completion transition works (and why you should avoid them)
Screencast: HOWTO: Send and receive a Signal via Ports in SysML and Cameo Simulation Toolkit
Parameter vs ActivityParameterNode vs Pin
Starting an Action that has an InputPin
Activity example: send and catch Signal
uml101 - Activity Diagram - notation - REFERENCE CARD
Transitions
Submachines: entryPoint and exitPoint
Composite state entry and exit points
Effect, Entry, Do, Exit
State configurations
Kinds of States
uml101 - StateMachines - NOTATION REFERENCE CARD
A quick look at accessing an Operation on a Transition or ActivityEdge guard with Alf vs ALH
The WhenValid Activity as effect Behavior
HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study