You can generate conceptual and physical data models and XML models from an OOM.
The following table details how OOM objects are generated to other models:
OOM |
CDM |
PDM |
XSM |
---|---|---|---|
Domain |
Domain |
Domain |
Simple Type |
Class (Persistent and Generate check boxes selected). |
Entity |
Table (The cardinality of a class becomes the number of records of a table.) |
Element |
Abstract class |
Entity |
Table |
Complex type |
Attribute (Persistent check box selected) |
Attribute |
Column |
Attribute or element (see generation options) |
Identifier |
Identifier |
Identifier |
Key |
Composition |
- |
- |
New level in the element hierarchy |
Operation with <<storedProcedure>> stereotype (parent class generated as a table) |
- |
Stored procedure attached to the table, with the operation body as a body in the procedure definition. |
- |
Operation with <<storedFunction>> stereotype (parent class generated as a table) |
- |
Stored function attached to the table, with the operation body as a body in the function definition. |
- |
Association |
Relationship or association |
Table (if many-to-many multiplicity) or reference. Role names become migrated foreign keys. |
KeyRef constraints |
Association class |
Entity/relationship notation: entity with two associations. Merise notation: association, and two association links |
A table and two associations between the end points of the association class |
- |
Dependency |
- |
- |
- |
Realization |
- |
- |
- |
Generalization |
Inheritance |
Reference |
Complex type derivation (XSD) or attribute migration to child element (DTD) |