|
1
|
|
|
2
|
- Overview
- Goals
- Challenges
- Status
- Milestones
- Work Items
- How Can You Help?
|
|
3
|
- An Eclipse Modeling Development Tools subcomponent at http://www.eclipse.org/modeling/mdt/?project=uml2#uml2
- An EMF-based implementation of the UML™ 2.0 metamodel for the Eclipse
platform
- Project lead is Kenn Hussey (khussey@ca.ibm.com)
- Partners include Borland, Ericsson, and Unisys
- Users include IBM, Metanology, Omondo, and Ontogenics
|
|
4
|
- Provide a useable implementation of the metamodel to support the
development of modeling tools
- Provide a common XMI schema to facilitate interchange of semantic models
- Provide test cases as a means of validating the specification and
implementation
- Provide validation rules as means of defining and enforcing levels of compliance
|
|
5
|
- Since the specification isn’t finalized, the API is a moving target
- The current structure of the standard metamodel (w.r.t. package merge,
redefinitions, subsets/supersets) makes the mapping to Java difficult
- An XMI schema based on the current specification could not be used for
interchange without transformations
- There are a number of errors in the specification which, until fixed,
make the API and XMI schema difficult to use
- Compliance points for UML™ 2.0 are a subject of much debate within the
modeling community
|
|
6
|
- EMF-generated API based on a collapsed version of the metamodel in which
package merges and a majority of the redefinitions have been factored
out
- Includes mechanisms to support derived union, redefines, and subsets
constraints
- Generated using a customized Rose2Ecore builder and JET templates
|
|
7
|
- Default XMI schema generated using EMF
- Defines one namespace (http://org.eclipse/uml2.ecore) for all elements,
thus supporting interchange
- Elements identified using Universally Unique Identifiers (UUIDs)
|
|
8
|
- Errors discovered while using the API and/or XMI schema are being fixed
and submitted as issues to the UML™ 2.0 Superstructure Finalization Task
Force (FTF)
- UML™ 2.0 Superstructure FTF currently has a large number of unresolved
issues, available at
http://www.omg.org/issues/uml2-superstructure-ftf.open.html
- Tentative finalization date for UML™ 2.0 Specification is April 2004
|
|
9
|
- Validation rules to be evaluated using EMF Switch-based validator
mechanism
- Validators are being implemented based on sets of OCL constraints
- May correspond to compliance levels when defined
|
|
10
|
- Release 1.0 of UML2 to coincide with Eclipse 3.0
- Will be based on EMF 2.0
- Depends on successful finalization of UML™ 2.0 specification
|
|
11
|
- Validation rules
- Resource migration mechanism
- Import/export from/to Rose (Unisys XMI)
- Unit tests
- Javadoc
- Bug fixes
|
|
12
|
- Develop tools based on UML2
- Report bugs
- Participate in newsgroup discussions
- Write articles
- Become a UML2 contributor
|