Difference between revisions of "SBVR Exchange Metamodel"

From Eclipsepedia

Jump to: navigation, search
Line 1: Line 1:
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.
+
= Overview =
 +
This page describes the SBVR 1.0 CMOF metamodel that may be used to load and save XMI files (with '.xmi' extension) compliant with the SBVR 1.0 specification.
  
 
* The [http://www.omg.org/spec/SBVR/20070901/SBVR-model.xml SBVR CMOF model] as published with the OMG specification
 
* The [http://www.omg.org/spec/SBVR/20070901/SBVR-model.xml SBVR CMOF model] as published with the OMG specification
* The revised model is available as SBVR.uml in CVS org.eclpse.sbvr/models
+
* The model used for code generation is available in CVS: org.eclpse.sbvr.xmi/model/SBVR.uml
 +
 
 +
Class diagrams created from the original SBVR 1.0 metamodel specification:
 +
* [[Media:SBVR_concept-representation.gif | concept representation diagram]] -- Shows a subset of associations between '''concept''', '''representation''', and '''designation'''.
 +
* [[Media:SBVR_set.gif | set diagram]] -- Shows subclasses of '''set''' and their associations.
 +
* [[Media:SBVR_dictionary.gif | terminological dictionary diagram]] -- Shows associations between '''terminological dictionary''', '''vocabulary''', and '''body of shared meanings'''.
 +
 
 +
General observations about the SBVR CMOF model from the specification:
 +
* SBVR is defined in terms of SBVR language
 +
** the CMOF metamodel is generated from the SBVR language
 +
** the CMOF model in the specification was not created or edited using a UML modeling tool
 +
* There is '''no''' use of composite aggregation anywhere in the model
 +
* All associations own both property ends and none are navigable from the end classes.
  
 
= Issues =
 
= Issues =
 +
The following issues were discovered while implementing the SBVR CMOF serialization metamodel.
 +
 
=== Issue 1: designation::signifier ===
 
=== Issue 1: designation::signifier ===
 
Class diagram created from the original SBVR 1.0 metamodel specification:
 
Class diagram created from the original SBVR 1.0 metamodel specification:
Line 20: Line 35:
  
 
= Resolutions =
 
= Resolutions =
Track the resolution by OMG SBVR revision task force committee.
+
Track the resolution of issues by OMG SBVR revision task force committee.
  
 
[[Category:Modeling]]
 
[[Category:Modeling]]
 
[[Category:MDT]]
 
[[Category:MDT]]
 
[[Category:SBVR]]
 
[[Category:SBVR]]

Revision as of 15:05, 1 May 2008

Contents

Overview

This page describes the SBVR 1.0 CMOF metamodel that may be used to load and save XMI files (with '.xmi' extension) compliant with the SBVR 1.0 specification.

  • The SBVR CMOF model as published with the OMG specification
  • The model used for code generation is available in CVS: org.eclpse.sbvr.xmi/model/SBVR.uml

Class diagrams created from the original SBVR 1.0 metamodel specification:

General observations about the SBVR CMOF model from the specification:

  • SBVR is defined in terms of SBVR language
    • the CMOF metamodel is generated from the SBVR language
    • the CMOF model in the specification was not created or edited using a UML modeling tool
  • There is no use of composite aggregation anywhere in the model
  • All associations own both property ends and none are navigable from the end classes.

Issues

The following issues were discovered while implementing the SBVR CMOF serialization metamodel.

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 the {subsets} reference is not included in the CMOF model. Without the subsets reference, the designation subclass will require 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 of issues by OMG SBVR revision task force committee.