State::doActivity

Explains what a completion transition is and how to simulate and explore it in Cameo Simulation Toolkit for MagicDraw UML, MagicDraw SysML, or Cameo Systems Modeler.

Please note that this is NOT a recommendation to use completion transitions!

Completion events have dispatching priority. That is, they are dispatched ahead of any pending Event occurrences in the event pool.

Source

Unified Modeling Language 2.5.1

In case of simple States, a completion event is generated when the associated entry and doActivity Behaviors have completed executing. If no such Behaviors are defined, the completion event is generated upon entry into the State.

Source

Unified Modeling Language 2.5.1

Transitions

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:03: UML Behavior: StateMachines quick start

Slide kind

UML StateMachine Diagram

The entry, doActivity, and effect Behaviors defined on a submachine State are specific that particular usage of its Submachine

Composite state entry and exit points

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:03: UML Behavior: StateMachines quick start

Slide kind

UML StateMachine Diagram

MagicDraw/Cameo: GOTCHA: ‘entry’, ‘exit’, ‘doActivity’ are all subsets of ‘ownedElement’; to use an existing Activity without changing its owner you need to create a “wrapper” Activity. Beware the tool does not simply move your Activity!

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.

Source

Unified Modeling Language 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 ...

Source

Unified Modeling Language 2.5.1

A State may also have an associated doActivity Behavior. This Behavior commences execution when the State is entered (but only after the State entry Behavior has completed) and executes concurrently with any other Behaviors that may be associated ...

Source

Unified Modeling Language 2.5.1

Effect, Entry, Do, Exit

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:03: UML Behavior: StateMachines quick start

Slide kind

UML StateMachine Diagram

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

Source

Unified Modeling Language 2.5.1

Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: StateMachine with doActivity and a Transition with a ChangeEvent trigger

Keywords

Video style

A very simple demonstration of a StateMachine with a doActivity and a Transition that uses a trigger with a ChangeEvent for checking a value. Uses SysML but the same applies to UML.

Uses Magic Model Analyst^® (Cameo Simulation Toolkit^®) for MagicDraw SysML and Cameo System Modeler Enterprise Edition.

Subscribe to State::doActivity