Legacy Issue Number: 15014
Source: Fraunhofer FOKUS ( Marcus Engelhardt)
Comparing the specification and the provided meta model, numerous inconsistencies between both appear. For example:
Naming differentials: Most of the meta classes with an underscore in their name mentioned in the specification document are named differently without the underscore.
Some association ends are missing in the provided model, e.g. categoryElement for the association between SMMCategory and Measure. (In our opinion, this association should be called measureElement to separate from the reflexive Association of the SMMCategory class having the same name.)
Numerous multiplicity values in the meta model differ from the specification. For example, the association between the SMMModell class and the SMMElement class has the upper bound value 1.
The subclasses of CollectiveMeasure (AdditiveMeasure and MaximumMeasure) mentioned in the specification do not occur in the meta model.
Reported: SMM 1.0b2 — Sun, 31 Jan 2010 05:00 GMT
Disposition: Closed; No Change — SMM 1.2
Inconsistencies between meta-model and specification have been fixed in SMM 1.1
These inconsistencies between meta-model and specification have already been fixed in SMM 1.1, due to resolution of other issues. E.g., in SMM 1.1, names no longer have underscores, all association ends are provided in the model, and multiplicity issues have been fixed. All classes and sub-classes appear in the model.
Updated: Mon, 2 Apr 2018 18:08 GMT
SMM12 — Inconsistency between specification and provided Meta Model
- Key: SMM12-84
- OMG Task Force: Structured Metrics Metamodel 1.2 RTF