Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
MDT-SBVR 0.7 Project Plan
Note: This is a draft of the requirements document and is expected to change.
Last revised: --2008-03-31
Please send your feedback on this draft document to the mdt-sbvr.dev@eclipse.org developer mailing list.
Back to SBVR Main Page
Contents
Overview
Status of a requirement
The current status of a requirement can be one of the following categories.
Proposed
These are requirements that are being considered for this release. These are items that are either being investigated or items that the project would like to explore but are not yet Committed. Most of the requirements should start as proposed items. After a review and some amount of detailed planning, their status will either become committed or deferred.
Committed
These are requirements that the project team is definitely going to address in the release. Resources and some amount of detailed plans have been identified for such items.
Deferred
These are valid requirements that started in a Proposed state but will not be addressed in this release. Each such item will have a brief note explaining the cause for the deferral.
Flags on a requirement
A requirement can have these additional flags.
These are valid requirements in the 'Propsed' or 'Deferred' status that require volunteers to work on them. These are especially good candidates for companies or individuals who want to get involved with SBVR in a large way.
Complete File:Checkmark-10x10.gif
This flag is used to mark items as they are mostly finished. While the items might continue to have bugs fixed etc. until the final release, we expect each milestone will have some items to mark as "complete", such as those going into a New and Noteworthy document for that milestone. This flag is a good indication that something is ready to be fully tested, documented, etc.
Requirements
SBVR Metamodel Implementation
Proposed
- Metamodel enhancements for tool developers. (bug#xxx)
- SBVR 1.1 Compliance. Provide support for interchange (XMI) compliance with SBVR 1.1. (bug#xxx)
Committed
- Generate EMF model, edit, and editor plug-ins for SBVR 1.0 CMOF metamodel. (bug#xxx}
- Load and Save XMI compliant with SBVR 1.0. (bug#xxx)
Deferred
SBVR Example Tools
Proposed
- Example menus for adding new designations. (bug#xxx)
Committed
Deferred