Issue 4787: SPEM issue: URL to issues reporting form is '404'
Issue 4888: Need for a minimal extensibility mechanism in the SPEM metamodel.
Issue 5331: Trace should not apply only on WorkDefinition but on every model element
Issue 5643: Constraint [C46] in section 8.5 contradicts definition of Discipline
Issue 6623: Figure 2.4 Foundation Core Package
Issue 4787: SPEM issue: URL to issues reporting form is '404' (spem-rtf)
Click here for this issue's archive.
Source: University of British Columbia (Professor Philippe Kruchten, pbk(at)ece.ubc.ca)
Nature: Uncategorized Issue
Severity:
Summary:
Ref: http://www.omg.org/cgi-bin/doc?ptc/2001-12-06 on page 5 it says: All OMG specifications are subject to continuous review and improvement. As part of this process we encourage readers to report any ambiguities, inconsistencies, or inaccuracies they may find by completing the Issue Reporting Form at http://www.omg.org/library/issuerpt.htm This page does not exist.
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.
This is addressed by UML 2.0, and is being handled under the SPEM 2.0 RFP.
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.
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].
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.