Software & Systems Process Engineering Metamodel Avatar
  1. OMG Specification

Software & Systems Process Engineering Metamodel — Closed Issues

  • Acronym: SPEM
  • Issues Count: 4
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
SPEM11-6 Constraint [C46] in section 8.5 contradicts definition of Discipline SPEM 1.0 SPEM 1.1 Resolved closed
SPEM11-7 Figure 2.4 Foundation Core Package SPEM 1.0 SPEM 1.1 Resolved closed
SPEM11-4 Need for a minimal extensibility mechanism in the SPEM metamodel. SPEM 1.0b1 SPEM 1.1 Closed; No Change closed
SPEM11-5 Trace should not apply only on WorkDefinition but on every model element SPEM 1.0 SPEM 1.1 Resolved closed

Issues Descriptions

Constraint [C46] in section 8.5 contradicts definition of Discipline

  • Key: SPEM11-6
  • Legacy Issue Number: 5643
  • Status: closed  
  • Source: Osellus, Inc. ( Vivienne Suen)
  • Summary:

    Constraint [C46] in section 8.5 contradicts the definition of Discipline in the previous section. The standard says:

    "[C46] Disciplines only categorize Activities."

    However, in the previous section, Disciplines are defined as categorizing Activities, Guidances, and WorkProducts. We should consider getting rid of [C46].

  • Reported: SPEM 1.0 — Thu, 12 Sep 2002 04:00 GMT
  • Disposition: Resolved — SPEM 1.1
  • Disposition Summary:

    see below
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Figure 2.4 Foundation Core Package

  • Key: SPEM11-7
  • Legacy Issue Number: 6623
  • Status: closed  
  • Source: N-Soft ( Nadia Szucs)
  • Summary:

    The Figure 2.4 Foundation Core Package - Backbone will look "cleaner" if the element "Feature" will be moved to a position in between elements "Parameter" and "Constraint". This would allow to adjust the diagram so that the composition association between "Model Element" and "Namespaces" may stand alone, not crossing the inheritance association.

  • Reported: SPEM 1.0 — Mon, 17 Nov 2003 05:00 GMT
  • Disposition: Resolved — SPEM 1.1
  • Disposition Summary:

    This is a diagrammatic change, with no alteration to the text or metamodel.
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Need for a minimal extensibility mechanism in the SPEM metamodel.

  • Key: SPEM11-4
  • Legacy Issue Number: 4888
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • Summary:

    4. Need for a minimal extensibility mechanism in the SPEM metamodel.
    When using the SPEM UML profile one can use tagged values to
    annotate model elements. In order not to loose this information
    when expressing the SPEM model in terms of the metamodel, we need
    an equivalent mechanism in the metamodel counterpart.
    Suggestion: add a Property metaclass with a name and value attributes
    to be attached to any model element.

  • Reported: SPEM 1.0b1 — Fri, 22 Feb 2002 05:00 GMT
  • Disposition: Closed; No Change — SPEM 1.1
  • Disposition Summary:

    No Data Available
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Trace should not apply only on WorkDefinition but on every model element

  • Key: SPEM11-5
  • Legacy Issue Number: 5331
  • Status: closed  
  • Source: Softeam ( Philippe Desfray)
  • Summary:

    The SPEM standard says :

    "A Trace dependency acts between WorkDefinitions and is mainly
    used to trace requirements and changes across models. It has the same
    semantics as UML Trace."

    Trace should not apply only on WorkDefinition but on every model element. We
    could have for examples a requirement on process, and trace a specific
    activity to the requirement, thus expressing that we have defined this
    activity to fulfill the requirement. This is in line with the UML semantics.
  • Reported: SPEM 1.0 — Wed, 29 May 2002 04:00 GMT
  • Disposition: Resolved — SPEM 1.1
  • Disposition Summary:

    This is a change to the specification text, with no change to the metamodel.
  • Updated: Fri, 6 Mar 2015 20:58 GMT