Bug 226010

Summary: SBVR metamodel for tool developers
Product: z_Archived Reporter: Dave Carlson <dcarlson>
Component: SBVRAssignee: Dave Carlson <dcarlson>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3 Keywords: plan
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: Compliance
Attachments:
Description Flags
Draft UML models for SBVR tools metamodel none

Description Dave Carlson CLA 2008-04-07 13:52:11 EDT 
The SBVR metamodel has a very "flat" structure without composition/containment or navigable associations. Modify the metamodel structure as necessary to enable improved APIs for tool development.
Comment 1 Dave Carlson CLA 2008-05-01 15:37:44 EDT 
Modify plan item description:

Design an SBVR metamodel that is optimized for tool development and that enforces structural constraints in the specification.
Comment 2 Dave Carlson CLA 2008-05-02 14:59:47 EDT 
Created attachment 98487 [details]
Draft UML models for SBVR tools metamodel

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 independent plugins, then we cannot use UML package merge, because this 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 model files are saved in *.uml format and should be usable in any current tool based on Eclipse UML2.  So that we may 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)
Comment 3 Dave Carlson CLA 2008-06-12 18:31:32 EDT 
A partial SBVR tools metamodel is checked into CVS in project "org.eclipse.sbvr". The metamodel is divided into separate model files for each SBVR compliance point.

The Draft UML models attachement in this bug is now obsolete.

No generated EMF code is committed to CVS, but you can use the supplied .genmodel files to generate all plugins.  I generate "Model" and "Edit" plugins for each genmodel, and generate "Editor" for only the SBVR.genmodel that represents the full compliance point.
Comment 4 Dave Carlson CLA 2008-06-12 18:32:20 EDT 
Comment on attachment 98487 [details]
Draft UML models for SBVR tools metamodel

Replaced by updated model files checked into CVS.
Comment 5 Dave Carlson CLA 2008-09-23 10:43:49 EDT 
Modified metadata for project plan.