Change Management Process for the Oracle Data Warehouse
Departmental users of the Oracle Data Warehouse may request that columns or tables be changed or added to the existing warehouse of current, future, historical or frozen data. The process for doing so is as follows:
- The Requestor lists what is required and contacts the Office of Data Administration (ODA) at email@example.com.
- Office of Data Administration (ODA) works with the Requestor to detail the requirements.
- The ODA coordinates a meeting with the following groups.
- Business Analysts.
- IT Architect and Modeler.
- Data Manager and/or Steward.
- IT Software Engineers (ESEs).
- IT Database Administrators (DBAs).
- The Architect, ESEs, and DBAs review the request to determine impact analysis and feasibility.
- The Data Manager approves the data set if possible; Data Stewards and DPAC involvement may be needed.
- A go/no go decision is made by the group or by DPAC, and a preliminary schedule is developed.
- ESEs and DBAs develop work product in the DEV environment.
- When the product is developed, it is moved to the QA environment.
- ODA tests in the QA environment, then hands off to the Requestor.
- The Requestor performs User Acceptance Testing in the QA environment, then hands back to ODA.
- Security access and user roles are reviewed and developed, if necessary.
- ODA requests a move to Production; DBAs determine the schedule.
- The ODA will communicate to the requestor, ESE, DBA, DW and WOW users, Data Managers, Data Stewards, and DPAC the release of the new data set or change to the warehouse.
- The Requestor and Data Manager coordinate training for the data set, metadata for Data Docs, and reports for WOW and reports.umd.edu.
- After release into Production and resolution of any issues, ODA calls a meeting to debrief and find lessons learned from the project.
A process flowchart for Change Management of the Oracle Data Warehouse is attached.