I think that there are three different ways to consider:
- The model driven solution is a model that generate code for you after a
transformation stage.
You can use:
1. AndroMDA, BlueAge or other which will generate code from an XMI based
on the UML Superstructure.
2. EMF technology with Obeo, OpenArchitectware etc... which will generate
code from an EMF model.
- The live code and model synchronization is a concept in which if you
change your UML class diagram then you code is automatically updated.
3. You can use commercial tools such as Borland, RSA 7.5, Soyatec or
Omondo. I personnaly think that except Omondo no other tool have a real
perfect integration. The main problem is that other tools had EMF tags in
the java code and don't use the UML Superstructure as the live
synchronization. This is therefore messy and not really usable in a
professional project.
My vision and what is not available as a standard in all tools is that
modern modeling should be a mix of EMF, UML Superstructure, live or none
live synchronization. You should be able to:
- make a clear differentiation between what is a pure UML class or mix
Java+UML class inside the same diagram.
- reuse the same element in as many diagrams as needed. I mean that each
element is displayed depending on the view but all these views keep an
internal mechanism and logic.
- keep the same UML Id for the entire project life in order to keep
traceability and add rules.
The main problem is that today that modeling try to drive Java development
and not be part of an agile methodology in which many other technologies
are involved a