| Summary: | [Plan Item] UML 2.1 Conformance | ||
|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Kenn Hussey <Kenn.Hussey> |
| Component: | Core | Assignee: | Kenn Hussey <Kenn.Hussey> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P2 | CC: | cdtdoug, crivet |
| Version: | 1.1.0 | Keywords: | plan |
| Target Milestone: | 2.0 M2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Kenn Hussey
So I take this to mean you're quite a ways from complying with the 04-10-02 spec. In particular, I've been looking at the Actions where there seems to have been pretty significant clean up in the new spec. Any comments on when we can expect any of this? The draft plan for UML2 2.0 can be found at http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E/uml2- home/docs/plans/uml2_project_plan_2_0.html. In it you will see the proposed dates for the milestone builds, the first of which is August 18. Does that mean you'll have conformance by M1? Or is it too early to say? The goal for the first milestone is to have generated the final API, so with any luck, "yes". I don't expect that all of the resource-related work will be done by M1, however. Ensure that the multiplicities of all properties match the specification. For example, the multiplicities of DurationObservationAction::duration and TimeObservationAction::now should be 1..1, not 0..*. Ensure that the defaults of all properties match the intended defaults in the specification. For example, the defaults of Operation::isUnique, Operation::isOrdered, Operation::lower, and Operation::upper (all redefinitions) are unspecified in the source model... should this mean that they inherit the redefined defaults? The main one I'm interested in at the moment is OpaqueAction. I haven't yet gone into much more depth to see if there are other actions that are missing. UML2 2.0 migration is now being tracked under bug 105191. A new API conformant to the forthcoming UML 2.1 specification has been made available (see org.eclipse.uml2.uml.*). Resources and examples have been updated/added to make use of the new API. Detailed differences between the old and new APIs will be described in a migration document to be posted in the near future. The code generator will be updated to use the new API as part of the migration feature (see bug 105191). The changes are available in build 2.0 M2. Move to verified as per bug 206558. |