Difference between revisions of "SBVR Exchange Metamodel"

From Eclipsepedia

Jump to: navigation, search
(Issue 1: designation::signifier)
Line 9: Line 9:
 
* [[Media:SBVR_concept-representation.gif | concept representation diagram]] -- Shows a subset of associations between '''concept''', '''representation''', and '''designation'''.
 
* [[Media:SBVR_concept-representation.gif | concept representation diagram]] -- Shows a subset of associations between '''concept''', '''representation''', and '''designation'''.
  
'''representation::expression''' has multiplicity [1..1] and is thus required in all specializations. The SBVR 1.0 specification indicates that '''designation::signifier''' {subsets expression}, but this is not included in the CMOF model.
+
'''representation::expression''' has multiplicity [1..1] and is thus required in all specializations. The SBVR 1.0 specification indicates that '''designation::signifier''' {subsets expression}, but this is not included in the CMOF model. Without the subsets reference, the designation subclass will contain values for both expression and signifier.
 +
* Change '''designation::signifier''' to add '''{subsets expression}'''
  
 
The specification also shows that '''designation::signifier''' has multiplicity [1..1], but it is [0..*] in the CMOF model. This expanded multiplicity is also incompatible with use of {subsets}.
 
The specification also shows that '''designation::signifier''' has multiplicity [1..1], but it is [0..*] in the CMOF model. This expanded multiplicity is also incompatible with use of {subsets}.
 +
* Change '''designation::signifier''' multiplicity to [1..1]
  
 
=== Issue 2: ===
 
=== Issue 2: ===

Revision as of 14:09, 10 April 2008

This page summarizes issues that were encountered in the SBVR 1.0 metamodel CMOF definition and how they are resolved in this EMF-based implementation.

  • The SBVR CMOF model as published with the OMG specification
  • The revised model is available as SBVR.uml in CVS org.eclpse.sbvr/models

Contents

Issues

Issue 1: designation::signifier

Class diagram created from the original SBVR 1.0 metamodel specification:

representation::expression has multiplicity [1..1] and is thus required in all specializations. The SBVR 1.0 specification indicates that designation::signifier {subsets expression}, but this is not included in the CMOF model. Without the subsets reference, the designation subclass will contain values for both expression and signifier.

  • Change designation::signifier to add {subsets expression}

The specification also shows that designation::signifier has multiplicity [1..1], but it is [0..*] in the CMOF model. This expanded multiplicity is also incompatible with use of {subsets}.

  • Change designation::signifier multiplicity to [1..1]

Issue 2:

Issue 3:

Resolutions

Track the resolution by OMG SBVR revision task force committee.