InvocationAction::onPort

If onPort is given, then the Port shall be an owned or inherited feature of the type of the target InputPin of the Action.

Source

Unified Modeling Language 2.5.1

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

SysML Block Definition Diagram (BDD)

SysML StateMachine Diagram

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

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)

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

SysML Block Definition Diagram (BDD)

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

SysML Activity Diagram

SysML Block Definition Diagram (BDD)

SysMLv1: Cameo Simulation Toolkit: 2024x: GOTCHA: SendSignalAction: Nested Ports won't appear in the selection dialog for 'onPort' (or work for Drag n' Drop) unless «InvocationOnNestedPortAction» has been applied (they are filtered out).

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

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.

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

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

InvocationAction::onPort : Port [0..1] For CallOperationActions, SendSignalActions, and SendObjectActions, an optional Port of the target object through which the invocation request is sent.

Source

Unified Modeling Language 2.5.1

UML/SysML: When sending a Signal (message) via a Port the 'target' is the owner of the Port through which the message will be sent, it is NOT the final recipient! So the 'target' is essentially the "sender"!

Activities of Keypad

Gallery

Tutorial

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

Section

Slide kind

SysML Activity Diagram

One of the most important reasons to use a Port to send a Signal is that only the connection context, not the sender, knows the ultimate recipient (at the end of a specific Connector).

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

Jump to first slide

IBD with Keypad, two specific Receiver sub-types, and a Display

Sections

fUML-1.4 EXCLUDES InvocationAction::onPort

Subscribe to InvocationAction::onPort