Issues for UML Profile for Scheduling 1.1 Revision Task Force

To comment on any of these issues, send email to uml-scheduling-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 5987: PAstep should apply to more model elements
Issue 5988: PAoccurrence has wrong type
Issue 5999: Extensions should be minimized in order to clarify resulting model
Issue 6271: : error in the table describing the stereotype ŤGRMreleaseť
Issue 6272: section 8.2.2.3

Issue 5987: PAstep should apply to more model elements (uml-scheduling-rtf)

Click here for this issue's archive.
Source: Carleton University (Dr. Murray Woodside, cmw(at)sce.carleton.ca)
Nature: Uncategorized Issue
Severity:
Summary:

The PAstep stereotype should apply also to Action and ActionExecution
(similar to 
SAaction). This is needed for modeling.


        - In fact the software sense of PAstep and SAaction are identical
for steps 
which are primitive (not decomposed into a sub-scenario). Thus the
stereotype should 
perhaps apply to Transition as well.

Resolution: see below
Revised Text: Revised Text: -- add the following entries to the Base Class column in the "PAstep" stereotype definition table: Action ActionExecution Transition
Actions taken:
July 3, 2003: received issue
September 24, 2004: closed issue

Discussion:

Agreed. Easy fix with no backward compatibility issues

Issue 5988: PAoccurrence has wrong type (uml-scheduling-rtf)

Click here for this issue's archive.
Source: Carleton University (Dr. Murray Woodside, cmw(at)sce.carleton.ca)
Nature: Uncategorized Issue
Severity:
Summary:

In the PAopenLoad stereotype, the tag PAoccurrence attribute name should not
be 
population, but a name standing for arrival pattern. 
OpenWorkload::arrivalPattern would do.

Resolution: see below
Revised Text: 1. In the definition table for the tagged values of "PAopenLoad", change the Domain Attribute Name entry for the PAoccurrence tag from "OpenWorkload::population" to "OpenWorkload::arrival"
Actions taken:
July 3, 2003: received issue
September 24, 2004: closed issue

Issue 5999: Extensions should be minimized in order to clarify resulting model (uml-scheduling-rtf)

Click here for this issue's archive.
Source: Commissariat a l Energie Atomique-CEA (Dr. Sebastien Gerard, sebastien.gerard(at)cea.fr)
Nature: Uncategorized Issue
Severity:
Summary:

2 - the name of extessions should be minimized in order to clarify
> resulting model. I propose to omit the prefix of every extenssion and to
> use the oncept of namespace in case of possible naming conflict. Moreover
> Package name describing the various sub-profile should be also reduced

Resolution: closed, no change
Revised Text:
Actions taken:
July 18, 2003: received issue
September 24, 2004: closed issue

Discussion:

This is a major change in terms of backward compatibility issues and beyond the scope of an RTF.

Issue 6271: : error in the table describing the stereotype ŤGRMreleaseť (uml-scheduling-rtf)

Click here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:

p4-37 : error in the table describing the stereotype ŤGRMreleaseť
should be ŤGRMacquireť instead of ŤGRMreleaseť

Resolution: see below
Revised Text: Change "GRMacquire" to "GRMrelease" on p3-38 in the stereotype Column for "GRMrelease".
Actions taken:
September 24, 2003: received issue
September 24, 2004: closed issue

Issue 6272: section 8.2.2.3 (uml-scheduling-rtf)

Click here for this issue's archive.
Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org)
Nature: Uncategorized Issue
Severity:
Summary:

The stereotype given in the stereotype column for PAopenLoad is PAclosedLoad

Resolution: see below
Revised Text: Change "PAclosedLoad" to "PAopenLoad" in the stereotype column for "PAopenLoad".
Actions taken:
September 24, 2003: received issue
September 24, 2004: closed issue