Trigger::event

SysMLv1: CAUTION: Only a Signal can be used for a SendSignalAction or MessageEvent trigger of an AcceptEventAction, not a Block or ValueType, even if they are valid types for a SysML FlowProperty! But you can "wrap" a Block or ValueType in a Signal.

Screencast: SysML/MBSE: An air conditioner refrigerant cycle in Cameo Simulation Toolkit

Keywords

Video style

This video only shows the Activities and StateMachines. For the underlying Block model please visit this accompanying slide trail:

TRAIL: SysML: Simple model of an air conditioner with a refrigerant cycle and StateMachine driven by Activities in MagicDraw/Cameo

Chain on a CallBehaviorAction for an Operation trigger of a Transition with an effect

Gallery

Tutorial

HOWTO return chain on a CallBehaviorAction for an Operation trigger of a Transition with an effect

Section

Slide kind

hybrid diagram

SysML Activity Diagram

SysML Block Definition Diagram (BDD)

SysML StateMachine Diagram

HOWTO return chain on a CallBehaviorAction for an Operation trigger of a Transition with an effect

Jump to first slide

Chain on a CallBehaviorAction for an Operation trigger of a Transition with an effect

Sections

Screencast: UML/SysML: HOWTO Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

Keywords

Video style

Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

Gallery

Tutorial

UML/SysML: HOWTO Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

Section

Slide kind

hybrid diagram

UML Activity Diagram

UML Class Diagram

UML StateMachine Diagram

UML/SysML: HOWTO Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

Jump to first slide

Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

Sections

Screencast: UML/SysML StateMachines: How a completion transition works (and why you should avoid them)

Keywords

Video style

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

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

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

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

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

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

Subscribe to Trigger::event