Issue 15014: Inconsistency between specification and provided Meta Model (smm-ftf)
Source:  (, )
Nature: Revision
Severity: Significant
Summary: 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.
Resolution: 
Revised Text: 
Actions taken:
January 31, 2010: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 31 Jan 2010 11:18:02 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          Marcus Engelhardt
Company:       Fraunhofer FOKUS
mailFrom:      marcus.engelhardt@fokus.fraunhofer.de
Notification:  Yes
Specification: SMM
Section:       all
FormalNumber:  ptc/2009-03-03
Version:       Beta 1
RevisionDate:  03/01/2009
Page:          all
Title:         Inconsistency between specification and provided Meta Model
Nature:        Revision
Severity:      Significant
test:          3qw8
B1:            Report Issue


Description:


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.