UML2 Profile Mechanisms

Omondo Corporation, Eclipse Foundation Member
February 2005

Tutorials:

1. UML2 Profile Diagram Guide

2. Omondo Profile Extension Guide

OMONDO's philosophy is not to ask our users to migrate from a code-centric to model-centric development. We consider that you should be free to use the methodology you need and work the way you want.  In order to help our users develop higher quality software more efficiently, we launched a powerful profiles creation mechanism built inside the EclipseUML2 Studio class diagram, on top of the EclipseUML2 metamodel and natively integrated with Eclipse 3.0.1. For Omondo, therefore, the Java code is as important as the UML models !!

The only way to improve productivity at any time of the life cycle is not to change the way you work but by understanding and adding modeling value to your daily job. Many vendors are just using UML 1.x or 2.0 annotation and MDA. Is this enough ?

A modern modeling solution should:

  1. Include a powerful UML2 graphical presentation (GEF) , customizable java code generator (Jet, Velocity and EMF) and use the XMI 2.0 metamodel.
  2. Interact between these elements inside a native Eclipse integration.
  3. Reverse a full project including all the information needed (not just pieces of information as other UML tools vendors do):  http://www.tutorial-omondo.com/reverse/ 
  4. Use a MDA approach. Omondo is looking for technological partners to work together in building professional MDA solutions onto the EclipseUML2 metamodel: http://www.eclipse.org/uml2/

UML Profiles were first introduced in Unified Modeling Language 1.3. It was a way to extend the standard modeling language. Architects/developers tried to integrate specific business needs. Unfortunately this was not possible at the time because of technological limitations and UML 1.x use. In UML 2.0, we have a mechanism to extend the UML based on stereotypes.

EclipseUML2 Studio now allows architects/developers to work together in a rational way and to add specific business needs. The Eclipse Platform allows each plugin to interact with other plugins. Both UML2 extension mechanisms and EclipseUML allow architects/developers to meet any specific business modeling need and add their "touch" to the UML inside the Eclipse platform.

Omondo decided to launch the UML2 profiles research project 18 months ago. The goal was to respect the UML2 profile requirements, use both UML2 graphical presentation and XMI 2.0 and allow our corporate customers to add their own framework inside EclipseUML. The decision was to rebuild all our existing core and migrate from NSUML to the EclipseUML2 metamodel: http://www.eclipse.org/uml2/

Several profiles can be applied to the same model using a stable and standardized core. It is possible to add J2ee, database, JSF (coming soon) etc.. profiles to a project in order to work inside a predefined UML configuration. Omondo's current technological projects related to profiles are:

  • Hibernate profile - adding Persistence inside the class diagram which is being connected live to the UML2 metamodel and generating java code.
  • JavaServer profile - model and use the profile mechanism inside the activity (or class) diagram to model and deploy.

Dynamic changes during the development life cycle using use case/class diagram and profile mechanisms, will be covered at the end of the year 2005. We are currently working on a new project whose goal is to dynamically integrate any third party methodology. Having a tight integration between UML and Methods is important, as much as selecting the right methods. This is why we consider that we should not provide an out of the box bundled solution. We prefer to allow each company to add its own methods corresponding to its own business requirements onto Eclipse using EclipseUML2 Studio extensions.


 
 
Last update Mon Feb 07 14:44:22 CEST 2005 Valid XHTML 1.0 Valid CSS All text, graphics © 2002-2005 by Omondo