Activity example: send and catch Signal

This is actually a SysML Activity Diagram with dashed-line ControlFlow symbols, and a Block is used instead of a Class. It also shows a SysML style «activity» on a BDD.

See it running in Magic Model Analyst^® (Cameo Simulation Toolkit^®) in this video:

Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: Send and receive a Signal using a SendSignalAction and an AcceptEventAction

Up next

ActivityPartitions using “swimlane” notation

Notes

[CAPABILITY, FEATURE, TOOL] MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome!

[DISPLAY, TIP]{INFORMATIVE} In a SysML Activity Diagram a control flow may be notated with a dashed line and stick arrowhead; this helps distinguish a ControlFlow from an ObjectFlow symbol.

Snippets (quotes/extracts)

[UML-2.5.1] An OpaqueAction is an Action whose specification may be given in a textual concrete syntax other than UML. An OpaqueAction may also be used as a temporary placeholder before some other kind of Action is chosen.

[UML-2.5.1] If an AcceptEventAction is used in an Activity, there are special rules for when it is enabled ..

[UML-2.5.1] If the AcceptEventAction has no incoming edges, by the usual rules, it is enabled when its immediately containing Activity (or StructuredActivityNode) begins execution.

[UML-2.5.1] However, in addition, an AcceptEventAction with no incoming edges remains enabled after it accepts an Event occurrence.

[UML-2.5.1] A ForkNode is a ControlNode that splits a flow into multiple concurrent flows. A ForkNode shall have exactly one incoming ActivityEdge, though it may have multiple outgoing ActivityEdges.

[UML-2.5.1] A JoinNode is a ControlNode that synchronizes multiple flows. A JoinNode shall have exactly one outgoing ActivityEdge but may have multiple incoming ActivityEdges.

Visit also

Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: Send and receive a Signal using a SendSignalAction and an AcceptEventAction

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

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

Visit also (backlinks)

Related slides (includes other tutorials)

UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY

UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY

Related slides (backlinks, includes other tutorials)

Flags