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

Video style

Accompanies slide trail

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 Magic Cyber-Systems Engineer ® (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 Magic Model Analyst® (Cameo Simulation Toolkit®) for MagicDraw® UML and the MagicDraw SysML Plugin (also bundled with Magic Cyber-Systems Engineer® (Cameo Systems Modeler®) Enterprise Edition). 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.

Notes
Snippets (quotes/extracts)
Next suggested video
Visit also
Visit also (backlinks)
External links