Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mdt-sbvr.dev] Draft of UML model for tooling metamodel 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=226010

The bug attachment contains a draft of UML models for the SBVR tools
metamodel.
See content of the 'model' folder.  After review and agreement to approach,
this
plugin will be committed to CVS.  These models are *NOT* complete and I am
not
soliciting detailed comment on design.  This review is only to gain
agreement
on the approach to modularizing the metamodel design, and generation into
five
separate model plugins.

If we want five plugins with dependencies, then we cannot use UML package
merge,
because merge aggregates all dependent model content in each client model.
This
would prevent creation or use of reusable tooling code (unless someone can
recommend an approach where this would work).  So please review if there are
any issues to NOT using package merge in the metamodel design.

The five model files are saved in *.uml format and should be usable in any
current
tool based on Eclipse UML2.  To allow us to edit and reveiw the models in an
open source environment, I used the Papyrus UML tool to create the model and
diagrams.  Download Papyrus (www.papyrusuml.org, I used version 1.9.1) to
open
the *.di2 diagrams files.

We agreed on a requirement to support the compliance levels in the SBVR
specification:

      Meaning and Representation Vocabulary (MRV)
      Logical Formulation of Semantics Vocabulary (LFSV)
      Vocabulary for Describing Business Vocabularies (VDBV)
      Vocabulary for describing Business Rules (VDBR)
      SBVR Vocabulary (SBVR)

The 5 UML models correspond to each of these vocabularies and there is a
.genmodel for each.  I have configured these to generate into, e.g.
org.eclipse.sbvr.mrv and org.eclipse.sbvr.lfsv

The current three plugins in CVS will be deleted and renamed to:
  org.eclipse.sbvr.xmi
  org.eclipse.sbvr.xmi.edit
  org.eclipse.sbvr.xmi.ui.editor

These plugins, generated from the specification CMOF model, should load and
save compliant XMI.

Regards,
  Dave Carlson

Back to the top