Library Structure Considerations

You must consider any or all of these suggestions when building a library structure:

Practical library names

Use practical and functional library names that help all users understand the purpose and type of models contained in the library. For example, you can use the format: Short System Name+Version+Stage (for example, Ora_8_Production).

Model naming and data type standards

Enforce naming and data type standards, which are vital to efficient workgroup modeling.

For more information, see the erwin� Data Modeler Online Help.

Rules for promoting models

Define a rigid and documented model approval and promotion process using different libraries for each development phase.

Rules for versioning models

Define versioning rules using different libraries for each development version (for example, Development Beta 1).

User rights and security

Apply stricter rights to libraries that contain mature models nearing the latter stages of development. You can also apply strict rights to individual models.

Publication

Generate reports to communicate milestones in the model development process.

Schema generation rules

Set up a library where you generate the model schema. Usually, you generate the model schema of promoted models only in the latter stages of development.