AcceptEventAction

SysML Internal Block Diagram (IBD)

SysML StateMachine Diagram

SysMLv1/UML2: Whilst fUML does not support InterruptibleActivityRegion, there are still ways to interrupt a StructuredActivityNode in Cameo Simulation Toolkit

SysMLv1: Cameo Simulation Toolkit: Cases for Transitions triggered by Signals sent direct to a remote target vs via Ports [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 StateMachine Diagram

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

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

SysMLv1: Cameo Simulation Toolkit: HOWTO send a Signal via a Port to an intended recipient via a mediating secure RoutingHub [with mini video]

Gallery

Tutorial

Section

Slide kind

SysML Internal Block Diagram (IBD)

SysMLv1: Cameo Simulation Toolkit: HOW send to an intended recipient via a shared Port? ATTEMPT: Using multiple Connectors to every candidate recipient without a mediating hub [with mini video]

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 Internal Block Diagram (IBD)

SysMLv1: Cameo Simulation Toolkit: HOWTO: Send a Signal via a nested Port using InvocationOnNestedPortAction and 'onNestedPort' together with 'onPort' [with mini video]

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

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

TIP: SysMLv1: Cameo Simulation Toolkit®: HOWTO handle receiving multiple Signal events in parallel within a repeated loop [with mini video]

Gallery

Tutorial

Section

Slide kind

SysML StateMachine Diagram

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.

BUG: Cameo Simulation Toolkit 19SP3: StateMachine: Crashes with an irrelevant "memory error" report if you fire a signal Trigger during execution of an 'entry' Activity with a timer

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

Keywords

Video style

This video accompanies this mini tutorial trail: HOWTO: Send and receive a Signal via Ports in SysML and Cameo Simulation Toolkit.

Activity of Display

Gallery

Tutorial

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

Section

Slide kind

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

Starting an Action that has a ValuePin - LIMITED SUPPORT

Gallery

Tutorial

Section

Slide kind

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

Starting an Action that has a ControlPin

Gallery

Tutorial

Section

Slide kind

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

Starting an Action that has an InputPin with multiplicity

Gallery

Tutorial

Section

Slide kind

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

Starting an Action that has an InputPin

Gallery

Tutorial

Section

Slide kind

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

Activity example: send and catch Signal

Gallery

Tutorial

Section

Slide kind

hybrid diagram

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

uml101 - Activity Diagram - notation - REFERENCE CARD

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

Section

Slide kind

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

UML Event types for triggering Transitions

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

Section

01:03: UML Behavior: StateMachines quick start

Slide kind

UML Profile 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

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

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

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

Gallery

Tutorial

Section

Section: SysML-1.6 specification diagrams: 11 Activities

Slide kind

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

Screencast: Tutorial: UML/SysML: StateMachines vs Activities: Operation-driven Transition case study - UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit

Keywords

Video style

This video accompanies this detailed tutorial trail: HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study.

This full length tutorial is a case study of the telephone dialer StateMachine shown in 'Figure 14.7 Composite State with two States' of the UML-2.5.1 specification.

Read more about Screencast: Tutorial: UML/SysML: StateMachines vs Activities: Operation-driven Transition case study - UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit

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

The Controller Activity (classifierBehavior of the Controller class)

Gallery

Tutorial

Section

Slide kind

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

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

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

Source

If a matching Event occurrence for an AcceptEventAction is dispatched from the event pool, then the AcceptEventAction is enabled to continue. However, if the containing Behavior execution has more than one waiting Trigger that matches ...

Source

An AcceptEventAction is a wait point ... except only the AcceptEventAction waits, rather than the whole Activity (Activities can have other Actions executing while AcceptEventActions are waiting).

Source

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