An Interrupt signal will be received before the OpaqueAction that prints “Finished” within the InterruptibleActivityRegion can be reached, and “Interrupted” will be printed instead.

Visit also: SysMLv1/UML2: Although fUML does not support InterruptibleActivityRegion, Cameo Simulation Toolkit does support InterruptibleActivityRegion

Visit also: SysMLv1/UML: Whilst the term 'InterruptibleRegion' is referenced in UML-2.5.1 and fUML-1.4, there is no metaclass InterruptibleRegion. The corresponding Metaclass is InterruptibleActivityRegion.

To mark the end of the Australian financial year we are offering a 25% DISCOUNT off SysMLv2 Workshop Seminar group course bookings fully pre-paid by 30th June 2026. This deal ends soon! Contact us now to apply!

Up next

SysMLv1: Cameo Simulation Toolkit: Activity Diagram simulation: Tokens in a CentralBufferNode [with mini video]

Notes

[TIP, TOOL, WORKAROUND]{INFORMATIVE} SysMLv1/UML2: Although fUML does not support InterruptibleActivityRegion, Cameo Simulation Toolkit does support InterruptibleActivityRegion

[CAVEAT] fUML-1.4 EXCLUDES InterruptibleRegion

[] SysMLv1/UML: Whilst the term 'InterruptibleRegion' is referenced in UML-2.5.1 and fUML-1.4, there is no metaclass InterruptibleRegion. The corresponding Metaclass is InterruptibleActivityRegion.

Snippets (quotes/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.

Related slides (includes other tutorials)

StructuredActitivityNodes (structured actions) - ADVANCED REFERENCE ONLY

UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY

UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY