Trigger

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

The event that enables this trigger is called a completion event and it signifies that all Behaviors associated with the source State of the completion Transition have completed execution.

Source

Unified Modeling Language 2.5.1

14.2.3.8.3 Completion Transitions and completion events: A special kind of Transition is a completion Transition, which has an implicit trigger.

Source

Unified Modeling Language 2.5.1

Trigger::event : Event [1..1] The Event that detected by the Trigger.

Source

Unified Modeling Language 2.5.1

Trigger::port : Port [0..*] A optional Port of through which the given effect is detected.

Source

Unified Modeling Language 2.5.1

When multiple triggers are defined for a Transition, they are logically disjunctive, that is, if any of them are enabled, the Transition will be triggered.

Source

Unified Modeling Language 2.5.1

A Transition may own a set of Triggers, each of which specifies an Event whose occurrence, when dispatched, may trigger traversal of the Transition. A Transition trigger is said to be enabled if the dispatched Event occurrence matches its Event type.

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

Transition::trigger : Trigger [0..*] ... Specifies the Triggers that may fire the transition

Source

Unified Modeling Language 2.5.1

StateMachine execution is represented by transitions from one active state configuration to another in response to Event occurrences that match the Triggers of the StateMachine.

Source

Unified Modeling Language 2.5.1

uml101 - StateMachines - NOTATION REFERENCE CARD

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

01:03: UML Behavior: StateMachines quick start

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

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.

Behavior StateMachines can be used to specify any of the following

StateMachines - simplified metaclass hierarchy

UML Event types for triggering Transitions

uml101 - StateMachines - NOTATION REFERENCE CARD

Kinds of States

State configurations

Effect, Entry, Do, Exit

Composite state entry and exit points

Submachines: entryPoint and exitPoint

Using submachines

Pseudostates - initial, fork, join, terminate

Pseudostates - junction

Pseudostates - choice

Pseudostates - deepHistory and shallowHistory

Transitions

Completion transitions and implicit triggers

A SignalEvent represents the receipt of an asynchronous Signal instance.

Source

Unified Modeling Language 2.5.1

A CallEvent models the receipt by an object of a message invoking a call of an Operation.

Source

Unified Modeling Language 2.5.1

A trigger for an AnyReceiveEvent is triggered by the receipt of any message that is not explicitly handled by any related trigger.

Source

Unified Modeling Language 2.5.1

An Event is the specification of some occurrence that may potentially trigger effects by an object.

Source

Unified Modeling Language 2.5.1

UML Event types for triggering 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 Profile Diagram

Figure 9-2: Stereotypes for Actions on Nested Ports

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6 specification diagrams: 09 Ports and Flows

Slide kind

UML Profile Diagram

Figure D.8 - Finite State Machine Associated with “Drive the Vehicle”

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6: HSUV sample

Slide kind

SysML StateMachine Diagram

UML StateMachine Diagram

trigger_with_ports: If a Trigger specifies one or more ports, the event of the Trigger must be a MessageEvent.

Source

Unified Modeling Language 2.5.1

A Trigger may be qualified by the Port on which the Event occurred.

Source

Unified Modeling Language 2.5.1

A Trigger specifies a specific point at which an Event occurrence may trigger an effect in a Behavior.

Source

Unified Modeling Language 2.5.1

StateMachine for the Dialer class

Gallery

Tutorial

HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study

Section

Slide kind

UML StateMachine Diagram

If it has isUnmarshall=true, then it must have result OutputPins corresponding to each of the attributes of the Signal of the SignalEvent (in order), and the attribute values of the Signal instance associated with an accepted SignalEvent occurrence ...

Source

Unified Modeling Language 2.5.1

If an accept signal action has isUnmarshall=false, then it must have a single result OutputPin on which the Signal instance associated with an accepted SignalEvent occurrence is placed.

Source

Unified Modeling Language 2.5.1

If the Trigger on the AcceptEventAction is chosen, then it completes and produces output on any result OutputPins.

Source

Unified Modeling Language 2.5.1

The context object for an AcceptEventAction is the context object of the Behavior execution within which the AcceptEventAction is executing (which may be the Behavior execution itself ...)

Source

Unified Modeling Language 2.5.1

AcceptEventAction is an Action with Triggers for one or more Events. When an AcceptEventAction is executed, it waits for an Event occurrence to be dispatched from the event pool of the context object for its execution that matches one of its Triggers.

Source

Unified Modeling Language 2.5.1

An AcceptEventAction with a trigger for a SignalEvent is informally called an accept signal action.

Source

Unified Modeling Language 2.5.1

<assignment-specification> is optional and may be omitted even if the Operation has Parameters. No standard mapping is defined from an assignment specification to the UML abstract syntax. A conforming tool is not required to support this notation. ...

Source

Unified Modeling Language 2.5.1

<assigned-name> is an implicit assignment of the argument value for the corresponding Parameter of the Operation to a Property or Variable of the context object for the triggered Behavior.

Source

Unified Modeling Language 2.5.1

A CallEvent is denoted by the name of the triggering Operation, optionally followed by an assignment specification: <call-event> ::= <name> [‘(‘ [<assignment-specification>] ‘)’] <assignment-specification> ::= <assigned-name> [‘,’ <assigned-name>]*

Source

Unified Modeling Language 2.5.1

The Signal trigger simulator in Cameo Simulation Toolkit 19SP3 does not support run-time user-defined attribute values (but you can define defaults)

Cameo Simulation Toolkit DOES NOT leverage a Reception on a Class/Block at all! Use an AcceptEventAction with a SignalEvent trigger or an 'effect' on a Transition instead. There is a formal fUML restriction that a Reception should not have a method.

If the triggers of an AcceptEventAction are all for ChangeEvents and/or CallEvents, then the AcceptEventAction has no result OutputPins (unless the AcceptEventAction is an AcceptCallAction ...)

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 Trigger