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

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
TIP
TOOL
WORKAROUND
Policy level
INFORMATIVE
Specification keywords
fUML-1.3
fUML-1.4
SysML-1.6
SysML-1.7
UML-2.5.1
UML keywords
"InterruptibleRegion"
InterruptibleActivityRegion
StructuredActivityNode
AcceptEventAction
TimeEvent
Keywords
fUML-1.4: 'InterruptibleRegion – Interruptible regions are excluded from fUML because they are considered to be more appropriate for “higher level” process modeling and outside the scope of fUML.'

Please note that whilst 'InterruptibleRegion' is referenced in UML-2.5.1 and fUML-1.4, there is no metaclass InterruptibleRegion. Visit also InterruptibleActivityRegion.

Although fUML and Magic Model Analyst® (Cameo Simulation Toolkit®) do not support InterruptibleActivityRegion, one can still interrupt a StructuredActivityNode using a basic AcceptEventAction or a AcceptEventAction with a TimeEvent. Simply have a ControlFlow from the "interrupting" AcceptEventAction to an ActivityFinal within the StructuredActivityNode, or a ControlFlow from the "interrupting" AcceptEventAction to outside the StructuredActivityNode.

Relates to
SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: TimeEvent on Transition [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: StructuredActivityNode with AcceptEventAction + TimeEvent [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: StructuredActivityNode with AcceptEventAction + TimeEvent [with mini video]
Related notes
Related notes (backlinks)
Related snippets (extracts)
  [fUML-1.4] InterruptibleRegion – Interruptible regions are excluded from fUML because they are considered to be more appropriate for “higher level” process modeling and outside the scope of fUML.
Visit also
Visit also (backlinks)