BDD representation of activity hierarchy
-
Key: SYSML17-255
-
Status: closed
-
Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
-
Summary:
I would question whether it was correct to change section 11.3.1.1 "Activity" by replacing the BDD representation of activity hierarchy (as per v1.3) with adjunct action properties (introduced in v1.4). Whilst the latter is possible with the AdjunctProperty facility, the prior method, inherited from UML, is still valid. That is, unless the UML activity hierarchy is expressly deprecated from SysML. Even then, it will leave end users with the question of what the additional benefit is of the adjunct property as applied to call behaviour actions.
-
Reported: SysML 1.5b1 — Thu, 19 Sep 2019 15:45 GMT
-
Disposition: Closed; No Change — SysML 1.7
-
Disposition Summary:
Closed, no change: Restrict bdd presentation of activities
There is no need that SysML restricts the modeling of activities in block definition diagrams like it is allowed by UML rules. The paragraph above Figure 11-1 in 11.3.1.1.1 says "Properties with AdjunctProperty applied ... can be used", it doesn't say they must be used.
-
Updated: Thu, 22 Dec 2022 13:45 GMT
-
Attachments:
- decomposition.png 180 kB (image/png)