Generate Database Model from Class Model

[fabiane]

Hi!!!!

  We defined the domain classes (classes diagram) and now we need to create a database model for our project.

   If we change each stereotype from the classes to table, we loose the logical view of the system.

  How we can create the database model without loosing the domain classes???

  Other question.... The EA create automatically the FK from an association between tables. For example, We have a table person and a table address with an association (1..*), so the PK from table person must go automatically to the address table as a FK. (Like power Designer tool or ER-Win).

thank's!!!!!

   

[CJ]

G'day,

To address the first question, until somebody gives a better answer ...  I'd say copy all your logical classes and paste them all as new in your database model.  (You'll have to go to each element and set stereotype to table, and set other database properties).


I'd trace each element in your database view back to the logical elements with some relationship (maybe a realization link?)  A lot of work, but makes for good documentation.

[fabiane]

We just try it... but when we paste the classes as new, EA doesn't bring the relationships (associations).  

[sargasso]

Since you are moving from analysis to design, why not copy the entire model to a new model (ie EAP database) and statrt there?

[JohnH]

Hi!!!!

  
   How we can create the database model without loosing the domain classes???

  
    

Look at Rational Rose for an example of support for this. A domain (conceptual) model is mapped to (or from - with roundtrip feature) a separate database (logical) model, and then generates the physical (schema) model. This has advantages over using other data design approaches (such as ORM in MS Visio Enterprise Architect edition) because it follows an object-oriented approach compatible with UML models.

With the increased emphasis on business process and domain modeling, having these features in EA would be a strong benefit.