Software & Systems Process Engineering Metamodel Avatar
  1. OMG Specification

Software & Systems Process Engineering Metamodel — Open Issues

  • Acronym: SPEM
  • Issues Count: 8
  • Description: Issues not resolved
Open Closed All
Issues not resolved

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

definition of what constitutes a development method

  • Key: SPEM11-3
  • Legacy Issue Number: 14075
  • Status: open  
  • Source: The Marlo Group ( Wayne Jenkins)
  • Summary:

    think it is crucial that the definition of what constitutes a development method is added to this specification. Observe that many concepts within the document define aspects of a method (e.g. method plug-in, method content, method configuration, etc) but at no stage is the concept of a method defined. The reason I think this is important is that the concept of "enactment" (seen in section 16) should be applied to a method rather than a process. For example, when I enact a development method I create a code repository and processes for its use — I do not just enact the processes. To support this model Figure 6.1 could change the configuration statement to "Configure a cohesive method customized for my project needs". The reason I need this alteration is that I am using the TOGAF method plug-in with the Eclipse Practice Framework. Here, the enactment of the TOGAF method for an organisation requires the creation of an architecture repository (in direct analogy to a code repository above). The current SPEM conceptual model does not seem to adequately cover this scenario

  • Reported: SPEM 1.1 — Mon, 13 Jul 2009 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Explicit relationship for WorkProduct composition

  • Key: SPEM11-1
  • Legacy Issue Number: 4832
  • Status: open  
  • Source: 88solutions ( Pete Rivett)
  • Summary:

    In 7.1 (Associations): Using UML aggregation to represent WorkProduct
    composition is painful in the metamodel since it requires Association,
    AssociationEnd and Multiplicity objects etc. To link 2 WorkProducts will
    thus take 7 objects (Association, 2 AssociationEnds, 2 Multiplicities, 2
    Ranges) none of which carry any useful information. In contrast,
    WorkDefinition has a direct subWork association.

    Proposed resolution: introduce a new recursive association on WorkProduct
    with ends subWork(0..) and parentWork(0..).

  • Reported: SPEM 1.0b1 — Tue, 12 Feb 2002 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

figure 12-4 page 85

  • Key: SPEM11-2
  • Legacy Issue Number: 9515
  • Status: open  
  • Source: Anonymous
  • Summary:

    The representation of "Example of Activity Diagram" is weird. It mixes data
    flow and control flow.

    Between two activities there should be a plain arrow if one comes after the
    other, and not a dashed arrow going from the 1st activity to an artifact and
    then another dashed arrow going from the artifact to the second activity. The
    fact that one activity comes after another is a control flow, the fact that a
    part from that one artifact is passing from one to the other is different.

    Because of this confusion, the strangest thing happens: synchronization bars
    are showed to synchronize activities with artifacts! This has no meaning.
    Only plain arroaw should leave and arrive to synchronization bars. They would
    go to or from activities, showing that two activities happen concurrently.
    The flow of data between the activities (artifacts and dashed arrows are
    something different)

  • Reported: SPEM 1.1 — Wed, 29 Mar 2006 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 ( Fred 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