-
Key: SYSML12-8
-
Legacy Issue Number: 13157
-
Status: closed
-
Source: INCOSE ( Sanford Friedenthal)
-
Summary:
Issue: Inability to name interruptible activity regions. Discussion. Interruptible regions are useful constructs in SysML to enable termination of activity nodes. This is useful in a variety of cases, such as when one wants to terminate actions with streaming and continuous flows. In more complex behaviors with multiple interruptible regions, it is desired to be able to identify these regions by name. This may be useful when defining the owned behavior of a block with an activity that has multiple interruptible regions that represnt behavior in a similar way to state machines, where an accept event action may cause the behavior of the block to transition to another interruptible region of its behavior. Proposed resolution: An interruptible region in UML and SysML is currently an activity group which subclasses element. Create a stereotype of interruptible region called name interruptible region that subclasses Named Element (a similar approach is applied to activity partitions in UML
-
Reported: SysML 1.1 — Sun, 14 Dec 2008 05:00 GMT
-
Disposition: Resolved — SysML 1.2
-
Disposition Summary:
This is addressed in UML 2.3. Assume this revision of SysML will be based on
UML 2.3, and update the Activities diagram table in SysML. -
Updated: Fri, 6 Mar 2015 20:58 GMT
SYSML12 — Section: 11.3.2 Inability to name interruptible activity regions
- Key: SYSML12-8
- OMG Task Force: SysML 1.2 RTF