SignalEvent

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

© Copyright 2021 Darren R C Kelly (Webel IT Australia). All rights reserved.

StateMachine for Refrigerant states

Gallery

Tutorial

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

Section

Slide kind

SysML StateMachine Diagram

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

Keywords

Video style

© Copyright 2020 Darren R C Kelly (Webel IT Australia). All rights reserved.

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

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

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

A SignalEvent represents the receipt of an asynchronous Signal instance.

Source

Unified Modeling Language 2.5.1

A MessageEvent specifies the receipt by an object of either an Operation call or a Signal instance.

Source

Unified Modeling Language 2.5.1

When Monitor Traction is enabled, it begins listening for signals coming in from the wheel and accelerometer, as indicated by the signal receipt symbols on the left, which begin listening automatically when the activity is enabled.

Source

OMG Systems Modeling Language (SysML) 1.6

Figure 11-11: Continuous system example 2 {EXPLICIT PINS}

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: 11 Activities

Slide kind

SysML Activity Diagram

Figure 11-11: Continuous system example 2 {ELIDED PINS}

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: 11 Activities

Slide kind

SysML Activity 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

To get synchronisation of multiple AcceptEventAction "loops" to work in Cameo Simulation Toolkit one sometimes needs an additional ForkNode

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

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

Source

Unified Modeling Language 2.5.1

Cameo Simulation Toolkit DOES NOT leverage a Reception on a Class/Block at all (due to an fUML restriction), use an AcceptEventAction with a SignalEvent trigger instead!

Subscribe to SignalEvent