Issues for Mailing list of the SPEM 2.0 Finalization Task Force

To comment on any of these issues, send email to spem2-ftf@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 12210: specification lacks an overview
Issue 12515: Profile Notation of Process Element
Issue 12517: Section 13.1 figure 13.3
Issue 13128: associations "categorizedElement" and "subcategory" are not implemented
Issue 15113: Reference to unavailable documents

Issue 12210: specification lacks an overview (spem2-ftf)

Click here for this issue's archive.
Source: Cordys (Mr. Fred A. Cummins, fred.a.cummins(at)gmail.com)
Nature: Enhancement
Severity: Significant
Summary:
The specification lacks an overview that provides an undestanding of how the problem domain is being addressed. This is important for non-implementers, particularly potential customers of implementations, to understand why they should care if a product implements SPEM

Resolution:
Revised Text:
Actions taken:
February 4, 2008: received issue

Issue 12515: Profile Notation of Process Element (spem2-ftf)

Click
here for this issue's archive.
Nature: Revision
Severity: Minor
Summary:
In SPEM 2.0 Profile Notation of Process Element you say: SuperClass of Process Element: BreakDownElement. I believe that's not correct because in BreakDownElement's specification BreakdownElement is a child of Process Element

Resolution:
Revised Text:
Actions taken:
May 30, 2008: received isuse

Issue 12517: Section 13.1 figure 13.3 (spem2-ftf)

Click
here for this issue's archive.
Nature: Clarification
Severity: Minor
Summary:
Below Figure 13.4 (page 98) text says: "Figure 13.3 depicts a SPEM 2.0 Profile presentation of an Activity called 'Define the System'..." but Figure 13.3 shows a Taxonomy and key relationships of Breakdown

Resolution:
Revised Text:
Actions taken:
June 6, 2008: received issue

Issue 13128: associations "categorizedElement" and "subcategory" are not implemented (spem2-ftf)

Click
here for this issue's archive.
Nature: Clarification
Severity: Significant
Summary:
Using the categorization within the SPEM 2.0 Profile we found the following: It seems, that the associations "categorizedElement" and "subcategory" are not implemented. The Category element does not have the two associations in its menue and there are no stereotypes with related names. It is not possible to categorize elements. Associations and stereotypes do not exist in provided ptc/2007-08-09 XMI files also. 

Resolution:
Revised Text:
Actions taken:
November 27, 2008: received issue

Discussion:


Issue 15113: Reference to unavailable documents (spem2-ftf)

Click
here for this issue's archive.
Nature: Clarification
Severity: Significant
Summary:
n Section 2 (Conformance) of the SPEM 2.0 spec, there is a reference to documents "ad/06-11-04" (XMI Schemata) and "ad/06-11-05" .  Neither of these are available.  I'd like to access the XMI Schemata for SPEM 2.0 if possible.

Resolution:
Revised Text:
Actions taken:
March 3, 2010: received issue