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
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
SendSignalAction::target: The InputPin that provides the target object to which the Signal instance 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 hybrid diagram 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
Activity example: send and catch Signal Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:04: UML Behavior: Activities quick start Slide kind hybrid diagram SysML Activity Diagram SysML Block Definition Diagram (BDD)
