1 Introduction 1.1 Purpose This document describes the roles of the data warehouse team and the IPS development team pertaining to future database change requests.
1.2 Roles and Responsibilities The data conversion/data warehouse team will assume primary responsibility for overseeing any changes to the IPS/SIPS logical model. These changes will include the recommended database changes from the first iteration; as well as, any future change requests. The team will approve future database change requests and apply changes to the IPS/SIPS logical model. The team will also apply changes to the SIPS physical model. Any changes to the IPS physical database will be made and coordinated among IPS developers and team leads.
1.3 Database Change Request Polices and Procedures The following sections list instructions for proper implementation of the Database Change Request Policies and Procedures. In addition, a copy of the Database Change Control Form is provided. 1.1.1
Recommended Changes Requests Pertaining to Iteration One: The following rules apply for ongoing database change requests: 1. The data conversion team will identify when the remaining “recommended database changes” will occur. They will coordinate these changes with their data conversion tasks, targeting the changes to occur at times when they are converting data in those subject areas. 2. The data conversion team will co-ordinate with the IPS developers, and team leads, any changes to the logical model. The impacts on the amount of coding, design rationale, etc can be discussed at this time. The IPS team and developers will operate with the understanding that the data conversion team will make the appropriate changes and that the developer’s code must be modified to conform. 3. The data conversion team will then make changes to the logical data models and apply changes to the physical SIPS model. 4. The data conversion team will then give the logical model to a IPS team lead, the primary developer, and the designated IPS database developer. 5. The developers and team lead will determine the date on which the physical IPS model and code changes will be applied. 6. The developers will then conform their code to the new physical model, update test plans as needed and unit test the code. 7. Once the SIPS and IPS physical models are updated and the MIS code has been modified, the Change Control Form will be noted and signed, indicating that the change has occurred.
Last Saved: 09/05/2005 9:42 PM
Confidential
4
Inventory and Project Sales (IPS)
ABC Corporation
Database Change Request Procedures
1.1.2
Ongoing Database Change Requests: The following rules apply for ongoing database change requests: 1. The data conversion team and IPS developers can submit database change requests twice a week. 2. Database change requests will be accepted up until 10:00 a.m. on Monday and 10:00 a.m. on Thursday. 3. The requestor will then complete the standard Change Control Form with a detailed description of why the change must occur. 4. The Change Control Form will be reviewed by a representative from the data conversion team, the primary developer, and a IPS team lead at an 11:00 a.m. meeting on Monday and Thursday. 5. If approved and no impacts are identified, then the data conversion team will update the logical model immediately. 6. The data conversion team will determine a time and apply the changes to the SIPS physical model. 7. Once the logical model is updated, it is passed to the IPS team lead, the primary developer, and the designated IPS database developer. These IPS representative will determine impacts to the IPS system and decide when the IPS database can be updated. 8. Once the SIPS and IPS physical models are updated, the Change Control Form should be noted and signed indicating that the change has occurred.
Last Saved: 09/05/2005 9:42 PM
Confidential
5
Inventory and Project Sales (IPS)
ABC Corporation
Database Change Request Procedures
Database Change Control Form Change Request Details: Requestor:
