Chapter 12 Generating Other Models from an OOM


Generating PDM objects

PDM generation translates OOM objects into physical objects.

OOM object PDM object after generation
Domain Domain
Class Table (only if the Persistent and Generate check boxes are selected in the class property sheet)
Interface Not translated
Attribute Column (only if the Persistent check box is selected in the attribute property sheet)
Identifier Identifier
Operation with <<storedProcedure>> stereotype If the parent class is generated as a table, the operation is generated as a stored procedure attached to the table.

The operation body is generated as a body in the procedure definition.

The generated procedure has the same name as the operation, however, if a name conflict occurs, a number is added to the name of the procedure
Operation with <<storedFunction>> stereotype If the parent class is generated as a table, the operation is generated as a stored function attached to the table.

The operation body is generated as a body in the function definition.

The generated function has the same name as the operation, however, if a name conflict occurs, a number is added to the name of the function
Association Reference or table
Association class A table and two associations between the end points of the association class
Dependency Not translated
Realization Not translated
Generalization Reference

Generating from classes

For a class to become a table you need to select the Persistent check box and define a type of generation in the Generation list in the Detail tab of the class property sheet.

The cardinality of a class becomes the number of records of a table.

Generating from associations

If the association has a many-to-many multiplicity: both roles of the association have the * sign selected in their multiplicity lists, the association is translated into a table in the generated PDM. If it has any other multiplicity, the association becomes a reference.

A role name becomes a migrated foreign key after PDM generation.

 


Copyright (C) 2005. Sybase Inc. All rights reserved.