An addin to transform class models to data models?

[csousa]

I have completed an analysis class model in EA that I would like to use as the starting point for a relational (logical) database design.

Does an add-in or other utility exist to do a basic/initial one-way transformation to give me a starting point?

[David OD]

I haven't tried it myself, but you could look at the built-in DDL transformation.  Information can be found in:

http://www.sparxsystems.com.au/resources/mda/ddl_transformation.html

Hope that helps.

[Makulik]

Hmmm, may be this depends on the modelling technology/concept used, but the more likely way I know it, is exactly vice versa: You're developing a (ER) data model for the persistent parts that appear in your domain model, and then transform it to an appropriate class model for the representation of the persistency layer of your application. This class model is usually based on some framework that provides access to your DB data, by means of specialized classes that contain the "binding" information between the DB tables and related class instances.

That's what I have widely experienced in various domains and projects. Even some sort of such process where no UML or formal model transformation was involved at all, but the principle was the same.

Just my 0.02EUR

Günther

[Dave.B]

You could simply export the package that contains the analysis model and then import that package with the 'strip GUIDs' option set. This will create a clone of the analysis model and provide you with a starting point for your design work.

There won't be an <<trace>> linkages between the two models though. But if you need that a simple script can match up the elements between the two packages and add the <<trace>> associations between them as required.

Regards
Dave B.

[Sunshine]

I create the class model then use the DDL transformation to create the database model. I then create the DDL script and run it on the database to create the schema. I had to modify the default script to add our own custom stuff and it worked fine. The scripting takes a bit of learning but is worth the effort. The one thing that I didn't manage to do was sort out the transformation of relationships with an association class. I had to do a cludge to my class model and replace those types of relationships with simple join classes.  

Once the database has been created I use iron speed to create the rest of the application http://www.ironspeed.com/. Its a same that kind of functionality isn't built into Enterprise Architect.

You can see more on the following link about Model Driven Architecture (MDA)
http://www.sparxsystems.com/uml_tool_guide/mda_transformations/mdastyletransforms.html

Hope that helps