Managing an Environment for Subsetting › Implement Change Control › Scenario: Preparing for a Data Model Change Session

Scenario: Preparing for a Data Model Change Session

1. The data administrator informs the team of the date and time to check in their subset and when they can check it out again.
2. The data administrator runs the Delete report to verify that developers have removed references to objects that is deleted.
3. The data administrator changes the data model using the data maintenance subset. As each change request is implemented, it is signed and dated.
4. The data administrator runs consistency check against the data model to ensure that all changes were done correctly.
5. The DBA runs retransformation so that the data model changes are reflected in the Data Structure List.

   Note: Not all changes to the data model are reflected in the Data Structure List. For example, adding and deleting permitted values cause no change to the Data Structure List because they are not implemented directly into the database.

6. The DBA prints all reports resulting from retransformation to create a record of the changes made.
7. The DBA modify the Data Structure List and the Data Store List to meet project, corporate standards, or both.
8. The model manager works with the developers, data administrator, and DBA to define the aggregate sets or rekeying required to migrate shared objects from other models.