AcceptEventAction::isUnmarshall

ISSUE: Cameo Simulation Toolkit: v2024x: Although does not respect inheritance of attributes of Signals on SendSignalAction or un-marshalling AcceptEventAction DOES require them on 'effect' Behaviors.

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]

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]

Section

Slide kind

SysML Activity Diagram

SysML Block Definition Diagram (BDD)

ISSUE: Cameo Simulation Toolkit: v2024x: Does not show argument Pins corresponding to inherited attributes of Signal on SendSignalAction or an un-marshalling AcceptEventAction. No known UML2.5.1 or fUML-1.4 constraint; no obvious tool display option.

Simulation video of sending an receiving a Signal via a Port in Cameo Simulation Toolkit

Gallery

Tutorial

HOWTO: Send and receive a Signal via Ports in SysML and Cameo Simulation Toolkit

Section

Slide kind

Activity of Display

Gallery

Tutorial

HOWTO: Send and receive a Signal via Ports in SysML and Cameo Simulation Toolkit

Section

Slide kind

SysML Activity Diagram

Activity of Receiver

Gallery

Tutorial

HOWTO: Send and receive a Signal via Ports in SysML and Cameo Simulation Toolkit

Section

Slide kind

SysML Activity Diagram

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

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

Subscribe to AcceptEventAction::isUnmarshall