-
Key: SYSML16-82
-
Legacy Issue Number: 16945
-
Status: closed
-
Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
-
Summary:
I like the feature of SysML to decompose activities in a block definition diagram based on the callbehavior semantics (Fig. 11.1. SysML spec.).
For example I use that extensively in the FAS methodology (Functional Architectures for Systems).
I have a question about the composite relationship between activities. The SysML specification seems to be unclear about that.
When modeling an activity with a CallbehaviorAction of another activity, does that automatically creates the association between the
activities in the model? I think it must do that. Unfortunately tools seems to have a different behavior.
-
Reported: SysML 1.4 — Sun, 8 Jan 2012 05:00 GMT
-
Disposition: Deferred — SysML 1.6
-
Disposition Summary:
Defer
Postponed to the next RTF
-
Updated: Mon, 1 Apr 2019 18:16 GMT
SYSML16 — Question about the Activity decomposition in Block Definition Diagrams
- Key: SYSML16-82
- OMG Task Force: SysML 1.6 RTF