Legacy Issue Number: 18678
Source: PTC ( Phillip Astle)
In the Constraints section the specification states the following:
'An Action appearing in an “AllocateActivityPartition” will be the /client (from) end of an “allocate” dependency. The element that represents the “AllocateActivityPartition” will be the /supplier (to) end of the same “allocate” dependency.'
For Actions owned by an Activity and shown inside the partition, this constraint is clear. However, if you have a StructuredActivityNode inside a partition and that StructuredActivityNode owns an Action, how many Allocate dependencies should there be? Should there be:
a) One allocate from the StructuredActivityNode only?
b) One allocate dependency from the StructuredActivityNode and one from the Action inside the StructuredActivityNode?
To make things clearer, instead of the constraints section saying:
'An Action appearing IN an "An Action appearing in an “AllocateActivityPartition”'
It should say something along the lines of:
'An Action referenced in the "node" role of an “AllocateActivityPartition”'
This would remove the ambiguity of what "in" means and allow users to decide when Allocate dependencies are created.
Reported: SysML 1.3 — Fri, 19 Apr 2013 04:00 GMT
Disposition: Deferred — SysML 1.6
Postponed to the next RTF
Updated: Mon, 1 Apr 2019 18:16 GMT