Notes
Slide Show
Outline
1
UML2 1.1 Release Review
  • Kenn Hussey
  • UML2 Project Lead
2
Agenda
  • Features
  • Non-Code Aspects
  • APIs
  • Architectural Issues
  • End-of-Life
  • Bugzilla
  • Standards
  • Schedule
  • Process
  • Community
  • IP Issues
  • Project Plan
3
Features
  • 1.1 Plan available at http://www.eclipse.org/modeling/mdt/uml2/docs/plans/uml2_project_plan_1_1.html.


  • Major features
    • Migration Framework. Provide a mechanism (using the Ecore2Ecore mapping framework and extended metadata) for migrating resources based on different (older) versions of the UML2 schema.
    • Resource Localization. Provide a mechanism for arbitrary (named) elements to be localized via properties bundles either co-located with the resource or distributed in a fragment; enhance the existing stereotype keyword mechanism to support properties bundles distributed in fragments.
4
Features (Continued)
  • Major features (continued)
    • EMF Generator Extensions. Refactor the custom Ecore “builder” and JET templates that were used to generate the UML2 metamodel and deliver them to the open source community, pending the availability of EMF generator extensibility enhancements; provide an extension that builds Ecore models from UML2 models.
    • More Examples. Deliver resource generation utilities to the open source community as examples. Introduce robust actions for converting models between Ecore and UML2 (and deprecate the existing import wizards).

  • 1.1 release notes available at http://download.eclipse.org/tools/uml2/scripts/news-release-notes.php?ver=1.1.0.
5
Non-Code Aspects
  • Documentation available at http://www.eclipse.org/modeling/mdt/docs.php?project=uml2
    • FAQ (updated)
    • Javadoc (for 1.0, 1.0.1, 1.0.2, 1.0.3, 1.1)
    • Link to OMG’s UML™ Resource Page (new)

  • Localization/externalization
    • Now optional (see bugs 77406, 85982).
    • NL packs for 1.0.x available at http://www.eclipse.org/modeling/mdt/downloads/?project=uml2#uml2.
    • NL packs for 1.1 to be available by September.
6
Non-Code Aspects (Continued)
  • Examples available as part of org.eclipse.uml2.examples feature
    • Actions to convert models to metamodels, model libraries (new)
    • Actions to generate metamodels, libraries, profiles (new)
    • Actions to externalize labels, keywords (new)
    • EMOF2Ecore mapping resource (new)

  • Articles
    • Getting Started with UML2 (needs to be updated)
    • Introduction to UML2 Profiles (needs to be updated)
    • Others (TBD) – see bug 77413
7
APIs
  • The APIs in this release are Eclipse Quality.


  • Internal APIs marked as such using new Eclipse 3.1 capability.


  • Support for instance creation – see bug 78296.


  • More convenience operations.


  • Improved factory methods.


  • New utilities class available.
8
Architectural Issues
  • Improved architectural quality
    • Less redundancy
    • Refactored code generator
    • Smaller, cleaner metadata
    • More efficient support for derived unions
    • New common plug-ins

  • Generic features contributed to EMF
    • Generation of unit tests
    • Support for Boolean flags
    • Migration framework (Ecore2XML)
9
End-of-Life
  • User features
    • Ecore2UML2, UML22Ecore import wizards retired in favor of new editor actions (in Ecore, UML2 editors).

  • APIs
    • Factory methods with unnecessary EClass argument deprecated.
    • Profile/stereotype methods with Ecore arguments deprecated.
    • Item property descriptor, property descriptor, property source, adapter factory content provider deprecated (moved to UML2Editor, made internal).
    • Subset/superset lists, cache adapter, qualified text provider interface, change command deprecated (refactored into common plug-ins).
10
Bugzilla
  • 44 bugs opened


  • 38 bugs resolved/closed


  • 0 bugs deferred


  • 5 new bugs


  • 1 P1 bug outstanding (77405)


  • 1 P2 bug outstanding (77413)


  • 3 P3 bugs outstanding (NLS)
11
Standards
  • 1.1 release (still) based on interim draft of UML 2.0 specification (U2P-UML-Super-v2-PDF-040502).


  • OMG to finalize specification (for real) very soon.


  • 2.0 release to be based on released specification (ptc-04-10-02).
12
Schedule
  • Project team met all milestones despite challenges
    • unplanned EMF contributions
    • limited resources
13
Process
  • This release has been developed using open, transparent, and inclusive processes.


  • This release has followed its charter principles.


  • The UML2 project makes appropriate use of Bugzilla, mailing lists (mdt-uml2.dev@eclipse.org), newsgroups (eclipse.tools.uml2), and conference calls.


  • There were no committer elections/removals during the 1.1 release cycle.
14
Community
  • Increased interaction in Bugzilla and on newsgroup.


  • UML2 represented at EclipseCon 2005 (project sprint) and OMG MDA, SOA and Web Services Workshop (workshop session).


  • Increased coordination with EMF tools project.


  • Coordination with new GMF technology project.


  • UML2 is the 6th most popular download at Eclipse.org.
15
IP Issues
  • The UML2 project verifies that:
    • the about files and use licenses are in place
    • all contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement; in either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy
    • all significant contributions have been reviewed by the Foundation's legal staff
    • that all non-committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff
    • all contribution questionnaires have been completed
16
Project Plan
  • Draft 2.0 plan available at http://www.eclipse.org/modeling/mdt/uml2/docs/plans/uml2_project_plan_2_0.html.


  • Committed features
    • UML™ 2.0 Conformance. Implement the revised package merge algorithm and regenerate the code using a source model based on the finalized UML™ 2.0 Superstructure specification (compliance level L3). Update UML2 resources (libraries, metamodels, profiles), examples, and EMF generator extensions as necessary. Enhance the generator extensions (developed in UML2 1.1) to facilitate code generation for an arbitrary compliance level. Provide a resource migration extension to migrate resources based on the UML2 1.x schema to 2.0.
17
Project Plan (Continued)
  • Committed features (continued)
    • Reduced Memory Footprint. Reduce the memory footprint of UML models by, for example, providing alternative implementations and/or lightweight alternatives to heavyweight representations of certain concepts (e.g. lower and upper bounds).

  • Planned features (planned)
    • UML™ 2.0 Interchange. Provide support for importing/exporting resources based on the official OMG XMI representation of UML™ 2.0.
    • Validation Rules. Complete the generation and implementation of validation rules from the UML™ 2.0 source model.
    • Javadoc. Complete the generation of model documentation from the UML™ 2.0 source model.
18
Project Plan (Continued)
  • Planned features (continued)
    • Enhanced Icons. Provide meaningful icons for most, if not all, of the types in UML.
    • Resource Fragments. Provide support for segregation of UML2 resources into ‘fragments’ with packages as root elements.
    • Tools. Engage partners and tool developers to contribute tools based on UML2, e.g. a mechanism for import/exporting resources based on Unisys XMI for UML 1.x.
19
Thank you!
  • Q&A