Model Transformation

Overview

Transformations are a huge productivity boost, and reduce the necessity of manually implementing stock Classes and elements for a particular implementation domain; for example, database tables generated from persistent PIM Classes

Enterprise Architect includes a number of basic built-in Transformations (see Included Transformations, below); Sparx Systems intend to make further Transformations available over time, either as built in Transformations or as downloadable modules from the Sparx Systems website

For a further productivity boost, Enterprise Architect can automatically generate code for your transformed Classes that target code languages; see the Generate Code on result option on the Model Transformation dialog

A Transformation is defined using Enterprise Architect's simple code generation template language, and involves no more than writing a template to create a simple intermediary source file; Enterprise Architect reads the source file and binds that to the new PSM

Transform Elements

Transformation Dependencies

Enterprise Architect also creates internal bindings (Transformation Dependencies) between each PSM created and the original PIM

This is essential, as it enables you to forward synchronize from the PIM to the PSM many times, adding or deleting features as you go; for example, adding a new attribute to a PIM Class can be forward synchronized to a new column in the Data Model

You can observe the Transformation Dependencies for a package using the Traceability window; this enables you to check the impact of changes to a PIM element on the corresponding elements in each generated PSM, or to verify where a change required in a PSM should be initiated in the PIM (and also to reflect back in other PSMs)

The Transformation Dependencies are a valuable tool in managing the traceability of your models

Enterprise Architect does not delete or overwrite any element features that were not originally generated by the transform; therefore, you can add new methods to your elements, and Enterprise Architect does not act on them during the forward generation process

Traceability

Included Transformations

Transformations that are currently built-in include:

• C# - Converts a PIM to a standard C# implementation set
• Data Model to ERD - Transforms a Data Model to an Entity Relationship Diagram (ERD)
• DDL - Transforms platform-independent Class elements to platform-specific table elements
• EJB Entity - Transforms platform-independent Class elements to packages containing the Class and Interface elements that comprise an EJB Entity Bean
• EJB Session - Transforms platform-independent Class elements to packages containing the Class and Interface elements that comprise an EJB Session Bean
• ERD to Data Model - Transforms an Entity Relationship Diagram into a Data Model
• Java - Transforms platform-independent elements to Java language elements
• JUnit - Converts a Java model to a model where test methods are created for each public method of any original Class
• NUnit - Converts a .Net language specific model to a model where test methods are created for each public method of any original Class
• WSDL - Converts a simple representation of a WSDL interface into the elements required to generate that interface
• XSD - Transforms platform-independent elements to XSD elements