${taskforce.name} Avatar
  1. OMG Task Force

SPEM 2.0 FTF — Open Issues

  • Key: SPEM2
  • Issues Count: 5
Create Issue
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
SPEM2-5 Reference to unavailable documents SPEM 2.0 open
SPEM2-4 associations "categorizedElement" and "subcategory" are not implemented SPEM 2.0 open
SPEM2-3 Section 13.1 figure 13.3 SPEM 2.0 open
SPEM2-2 Profile Notation of Process Element SPEM 2.0 open
SPEM2-1 specification lacks an overview SPEM 2.0b1 open

Issues Descriptions

Reference to unavailable documents

  • Key: SPEM2-5
  • Legacy Issue Number: 15113
  • Status: open  
  • Source: ICF International ( Dallas Vaughan)
  • 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.

  • Reported: SPEM 2.0 — Wed, 3 Mar 2010 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

associations "categorizedElement" and "subcategory" are not implemented

  • Key: SPEM2-4
  • Legacy Issue Number: 13128
  • Status: open  
  • Source: No Magic ( Saulius Pavalkis)
  • 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.

  • Reported: SPEM 2.0 — Thu, 27 Nov 2008 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section 13.1 figure 13.3

  • Key: SPEM2-3
  • Legacy Issue Number: 12517
  • Status: open  
  • Source: Im student ( Ignacio El Kadre)
  • 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
  • Reported: SPEM 2.0 — Fri, 6 Jun 2008 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Profile Notation of Process Element

  • Key: SPEM2-2
  • Legacy Issue Number: 12515
  • Status: open  
  • Source: Im student ( Ignacio El Kadre)
  • 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
  • Reported: SPEM 2.0 — Fri, 30 May 2008 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

specification lacks an overview

  • Key: SPEM2-1
  • Legacy Issue Number: 12210
  • Status: open  
  • Source: Agile Enterprise Design ( Mr. Fred A. Cummins)
  • 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
  • Reported: SPEM 2.0b1 — Mon, 4 Feb 2008 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT