CA ERwin Model Manager Implementation Guide

Model Life Cycle FrameworksModel Life Cycle FrameworksUse one of the following model life cycle frameworks in your organization:Model-Driven DevelopmentChanges to the schema are made to the model first and then forwardengineered.System-Driven ModelsChanges are made directly to the schema and the schema isreverse-engineered into the model to reflect the changes.Informational ModelsContains logical-only models, enterprise-wide models, or standards andsample models.Business Process ModelsContains models generated by CA ERwin Process Modeler.Each type of framework has different considerations that you must think aboutwhen configuring your database and developing its supporting policies. You arenot required to choose a particular framework, however, it helps to know yourdevelopment process before building a library structure.Model-Driven Development FrameworkIn the model-driven framework, the model is always the source of all changes.You create a new database schema by forward engineering the model. The lifecycle of a model in the model-driven Development framework can follow apath like this:■■■■■■■■■Create the library structure (for example, Development, Test, andProduction) and populate them with CA ERwin Data Modeler templates.Create the logical model in a development library.Promote the model to the test library when it is ready.Generate the schema from the test library.Modify the test model as required and synchronize it to the schema.Promote the model to the production library when it is ready.Publish the refreshed production model.Update the enterprise-wide model, if necessary.Incorporate changes into the development model for further changes, andrepeat the process.Chapter 1: Modeling in the Multi-User Environment 11