The OCL expression related to the BinaryMeasurement Class refers to the context RatioMeasurement instead of BinaryMeasurement.

Context of OCL expression of BinnaryMeasurement was fixed already

The context of the OCL expression of BinaryMeasurement was already fixed in SMM 1.1, due to resolution of other issue(s).

The operation attribute is declared to be of type Operation while this type is not specified in the document. Moreover, e.g. in Figure 5, it is declared to be of type string.

Operation association has been fixed in SMM 1.1 already

Section 10.7 of SMM 1.1 defines Operation Class. Figure 5 and other references to Operation have been fixed too. These fixes have been applied due to resolution of other issues at that time.

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.

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.

In some cases, it is helpful to compose several measures to a single audit to run these measures at once without the necessity to select the individual measures manually prior to each computation. Although it would be possible to model such as relationship using a subclass of the MeasureRelationship class, we recommend to introduce a class Audit that simply has an association to the Measure class to model the membership of a measure to a specific audit.

No change needed

The ObservedMeasure Class was introduced to SMM after publication of ptc/09-03-03 and that Class composes a collection of Measurements of one or more Measures, but of a single Observation. The ObservedMeasure Class, as such, fulfills the features of the requested Audit Class.

The chosen way of modeling names for model elements is not done straightforward and hampers the practical usage of the meta model. The SMM meta model contains several classes having an attribute called name. Moreover, all meta classes are derived from the abstract meta class SMM_Element, which should possess such an attribute according to the specification. Hence, this attribute can be considered of being modeled redundantly.
Regarding the provided EMOF model, the SMM_Element does not have any attribute so that the specified attributes name, short_description and description are missing.

According to best practices, we recommend to introduce a new class called SMM_NamedElement as a subclass of SMM_Element and as the base class of all meta classes having a name attribute. This facilitates to determine the name of a model element.

Issue is subsumed in issue SMM12-92

This issue is subsumed in issue SMM12-92

It is not stated clear how to assign threshold values to dimensional measures. On page 9 of the specification document, it is mentioned that a measure has a range which can be interpreted as “the set of possible measurement results”. However, there is no corresponding attribute mentioned in the specification or meta model.

We suggest to add two attributes lowerThreshold and upperThreshold to the DimensionalMeasure meta class to model a measure’s range.

Remove "range"

Modify the third paragraph of Sub-clause 10.1 (General) of Clause 10 (Measures), to delete the phrase "; a range, the set of possible measurement results;".