Learn about UML-to-Java transformations, how to merge changes
when you develop in both Java and
UML, the UML-to-Java transformation profile, and when to use mapping
models.
UML-to-Java transformations The UML-to-Java transformation
transforms UML model elements into Java code,
and generates code that is compatible with the Java 2 Platform, Standard Edition 1.4 (J2SE
1.4) and the Java 2 Platform,
Standard Edition 5.0 (J2SE 5.0).
Reverse transformations: Java to UML When
you create a UML-to-Java transformation
configuration and enable the Reconciled
Modeling design contract management protocol (DCMP), the Java-to-UML transformation
is automatically enabled. Reverse transformations enable you to reconcile
changes in an iterative development process.
Workflow for using transformations to merge changes when you develop in both Java and UML This content applies to version 7.5.4 or later. Starting
in version 7.5.4, you can instruct the UML-to-Java transformation
to automatically link all generated target Java elements to corresponding UML elements
and enable the UML-to-Java transformation to synchronize the model
with the source.
About mapping models You
can specify alternate file names for any of the files and folders that a transformation
generates by creating a mapping model. You can specify alternate names if
you want to include code-specific details such as naming restrictions in platform-specific
models, or if the logical organization of the source model is not appropriate
as target packaging.
Java transformation profile The UML-to-Java transformation profile
contains several stereotypes that you can apply to validate elements
in the source model, and stereotypes that control how the transformation
generates Java code.