01:04: UML Behavior: Activities quick start

Icon class
icon_class_computed
far fa-bookmark
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
UML keywords
Behavior
Action
Activity
Keywords
A very quick introduction to UML Activities and Actions. Please note that SysML® introduces many useful additions to Activity modelling as covered later in the main SysML trail.
This trail section is currently mostly just annotated diagrams only - with no additional text explanations except for linked Notes and Snippet spec extracts
This tutorial trail section includes some simulation example micro-videos

If you are already a "UML ninja" by all means skip to the SysML starting point:

08:01: The building Blocks of SysML
Start section here
uml101 - Activity Diagram - notation - REFERENCE CARD

Slides in this section

If you want to navigate the entire section including the additional explanatory text click on the title link of the first slide to view the full slide page, then use the next links to move through the slide pages. If you just want to view the slide images only in sequence, click on any slide to view it larger in a viewer, then click again to move through each slide in this tutorial trail section.
uml101 - Activity Diagram - notation - REFERENCE CARD
Activity example: send and catch Signal
ActivityPartitions using “swimlane” notation
Starting an Action that has an InputPin
Starting an Action that has an InputPin with multiplicity
Starting an Action that has a ControlPin
Starting an Action that has a ValuePin - LIMITED SUPPORT
Parameter vs ActivityParameterNode vs Pin
ActivityParameterNode cases - REFERENCE CARD
UML2 Types of Pins - metaclasses
OR with DecisionNode and MergeNode
AND with ForkNode and JoinNode
ForkNode and JoinNode with optional ControlFlow guards - LIMITED SUPPORT
INCORRECT InitialNode no implicit fork
CORRECT InitialNode explicit fork
OPTION double InitialNode
ExecutableNode has implicit fork
Loop: running example using DecisionNode and MergeNode and an Integer property in a context
LoopNode: basic running example
LoopNode with loopVariable - ADVANCED REFERENCE
LoopNode: running loopVariable example
ExpansionRegion: running «iterative» example
StructuredActitivityNodes (structured actions) - ADVANCED REFERENCE ONLY
You may also like to view these related tutorial trails and videos:
HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study
HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit
HOWTO return chain on a CallBehaviorAction for an Operation trigger of a Transition with an effect
UML/SysML: HOWTO Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity
HOWTO: Send and receive a Signal via Ports in SysML and Cameo Simulation Toolkit
Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: Send and receive a Signal using a SendSignalAction and an AcceptEventAction
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
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: StateMachine with entry Activity and Transition guard
TRAIL: SysML: Simple model of an air conditioner with a refrigerant cycle and StateMachine driven by Activities in MagicDraw/Cameo
Screencast: SysML/MBSE: An air conditioner refrigerant cycle in Cameo Simulation Toolkit
Screencast: The Webel Digital Twin Pattern for SysML: Part 1: Simulating acquisition or creation of physical assets using Activities and StateMachines in Cameo Simulation Toolkit.
Next trail section
08:01: The building Blocks of SysML
SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: StructuredActivityNode with AcceptEventAction + TimeEvent [with mini video]
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 send a Signal via a nested Port using Action Language Helper (ALH) [with mini video]
SysMLv1: Cameo Simulation Toolkit: Cases for StateMachine Transitions with 'effect' Behaviors and/or States with 'entry' Behaviors triggered by a Signal with an attribute [with mini video]
SysMLv1: Cameo Simulation Toolkit: Cases for Transitions triggered by Signals sent direct to a remote target vs via Ports [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO handle sending and receiving families of related Signal types with reuse of send/receive and processing logic [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO send a Signal via a Port to an intended recipient via a mediating secure RoutingHub [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOW send to an intended recipient via a shared Port? ATTEMPT: Using multiple Connectors to every candidate recipient without a mediating hub [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO: Send a Signal via a nested Port using InvocationOnNestedPortAction and 'onNestedPort' together with 'onPort' [with mini video]
TIP: SysMLv1/UML: Cameo Simulation Toolkit: HOWTO convert an fUML ReadLine CLI String to a Boolean for cleaner DecisionNode tests against a LiteralBoolean [true] guard.
TIP/GOTCHA: SysMLv1/fUML: Cameo Simulation Toolkit: If you have a ControlFlow loop with a DecisionNode test you MUST have a MergeNode for the continuation path ControlFlow (typically entered also from an InitialNode or other loop starting point).
TIP/GOTCHA: SysMLv1/UML: Cameo Simulation Toolkit: If you use a «decisionInputFlow» to a DecisionNode you MUST also have a ControlFlow to the DecisionNode; if you don't use an explicit «decisionInputFlow» you don't need the "extra" ControlFlow
MagicDraw/Cameo: UML/SysML: TIP: Activity Diagrams: Learn how to use the Refactor > Extract feature to divide-and-conquer and identify cleaner flow and logic. Get control of those crossed wires!
Webel: MagicDraw/Cameo: UML/SysML: TIP: Activity Diagrams, StateMachine Diagrams, and port-based IBDs: Keep it loose initially with oblique (no break) paths, then square it up with rectangular paths at the very end
UML/SysML: TIP: Using Cameo Simulation Toolkit will strengthen your use of Activity Diagrams even when they are "just" analysis diagrams