The document discusses the importance of IT change control processes and proposes establishing a change control process at UDD. Key points: 1) IT change control processes formalize how IT systems are changed to maintain validated states and provide proof of a coordinated process between IT and business units. 2) Change control boards review and approve change requests, provide guidelines for requests, and manage approved changes to involve stakeholders. 3) Establishing a change control board and formal process at UDD would provide governance over IT changes and prioritize issues for the IT department.

1. IT Change Control Process 18 August 2005 [email_address]

2. Why Does UD Require IT Change Controls To maintain the IT systems in a Validated State. To provide proof to our customers/suppliers/auditors that UD and IT --WORK TOGETHER-- to a formal process. To allow UD management to review and be informed of interdepartmental workflow and requests for change. To minimise cost of change by clearly specifying requirements prior to implementation and installation (cost of ownership).

3. Cost/Effort Of A Change Request (from Boehm, Barry W. Software Engineering Economics . Englewood Cliffs, NJ: Prentice-Hall, 1981) 0 10 20 30 40 50 60 70 Requirements Design Code Development Testing Acceptance Testing Operation Development Phase Cost/Effort to Correct a Problem

8. The Change Control Process Loop