With DB2® Change Management Expert, you create models of the database that you want to change, and use those models to define what the database should look like before and after the changes and to generate the DDL to implement the changes. Before deploying the changes to the actual database, you also create commands to define how the data should be preserved in or migrated from the database when there are structural changes and to rebind the packages that might be affected by the changes.
As you change a model to define the set of changes that you want to make, you might want to compare the model to another model and move differences, validate the model definition, determine the impact that the changes might have on other objects in the database, and verify your changes by comparing the model of the database after changes to a model of the database before changes.
Each approach to change specification provides some functionality that is not provided by the other. Therefore, although the Deployment Script Editor is the primary approach, you will often use both approaches together to plan, analyze, and deploy your changes.