Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SBVR Exchange Metamodel"
| Line 4: | Line 4: | ||
* The revised model is available as SBVR.uml in CVS org.eclpse.sbvr/models | * The revised model is available as SBVR.uml in CVS org.eclpse.sbvr/models | ||
| − | Class | + | = Issues = |
| + | === Issue 1: designation::signifier === | ||
| + | Class diagram 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_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. | |
| + | |||
| + | 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}. | ||
| + | |||
| + | === Issue 2: === | ||
| + | |||
| + | === Issue 3: === | ||
| + | = Resolutions = | ||
| + | Track the resolution by OMG SBVR revision task force committee. | ||
[[Category:Modeling]] | [[Category:Modeling]] | ||
[[Category:MDT]] | [[Category:MDT]] | ||
[[Category:SBVR]] | [[Category:SBVR]] | ||
Revision as of 13:59, 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
Issues
Issue 1: designation::signifier
Class diagram created from the original SBVR 1.0 metamodel specification:
- 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.
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}.
Issue 2:
Issue 3:
Resolutions
Track the resolution by OMG SBVR revision task force committee.