Issue 18678: Unclear is StructuredActivityNode owned Actions should be Allocated (sysml-rtf)
Source: PTC (Mr. Phillip Astle, nobody)
Nature: Clarification
Severity: Significant
Summary: 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.
Resolution: Defer

Postponed to the next RTF
Revised Text: 
Actions taken:
April 19, 2013: received issue
January 3, 2017: Deferred
April 6, 2017: closed issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 19 Apr 2013 08:48:21 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-Tracker: AAAAAA==


*******************************************************************************
Name:            Phil Astle
Employer:        Atego
mailFrom:        phil.astle@atego.com
Terms_Agreement: I agree
Specification:   OMG Systems Modeling Language (OMG SysML.)
Section:         15.3.2.3 AllocateActivityPartition(from Allocations)
FormalNumber:    formal/2012-06-01
Version:         1.3
Doc_Year:        Year
Doc_Month:       Month
Doc_Day:         Day
Page:            134
Title:           Unclear is StructuredActivityNode owned Actions should be Allocated
Nature:          Clarification
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


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.