In the transformation configuration, you can select a single Java project as the source of the transformation.
If you specify a project or folder in the workspace as the transformation target, the transformation creates a new UML model in the container that you specify. The name of the model is JavaUMLModel, and a time stamp is appended to the name to ensure that the model and file name are unique. The time stamp is the system time specified in seconds; for example, JavaUMLModel1164050609968.emx.
If you specify a UML model as the transformation target, the transformation creates a temporary UML model, and compares the temporary model to the target model that you specify.
The Java-to-UML transformation uses the comparing and merging functionality to determine the differences between the target model and the temporary model that the transformation generates. When you run the Java-to-UML transformation, the merge editor displays the differences between the two models. In the merge editor dialog box, you can select the changes that the transformation merges into the target model.
The filters available in the merge editor enable you to show or hide the different types of deltas that occur when you run the Java-to-UML transformation. In the merge editor, click the Filters icon on the toolbar, and select the filters to apply to simplify the view.
For example, the transformation does not set upper and lower bounds when it transforms multiplicity elements such as attributes and parameters. In the temporary model, upper and lower bounds are set to null if no collection type is generated. If the upper and lower bounds are explicitly specified in the target UML model, even if these boundary values specify a default multiplicity of 0..1, this is considered a delta between the temporary model and the target model. For large models, these trivial deltas might be numerous, and make other deltas more difficult to see in the merge editor. To hide this type of delta, select the Filter out Trivial Lower and Upper Bound Changes filter.
The transformation provides integration functionality with CVS, Rational® ClearCase®, and Rational ClearCase LT version control systems, which enables you to automatically check out files or add new files. You must enable team capabilities to work with configuration management systems.