program change monitoring procedure

Program Change Monitoring Procedures

Number:Page Number:Date of Issue:

Revision:Prepared By:

Revised By:Approved By:

ITP of 528 March 071Hong Chan Chuen

Lim Hock Chee

1. PURPOSE

The purpose of the Program Change Monitoring Procedure is to describe the management processes required to ensure that any authorized changes to the applications are coordinated and documented properly. All changes to the applications are subjected to the various test processes before the tested changes can be released to the production environment.

2. SCOPE

This procedure applies to all the applications registered and managed by IT Team.

3. DEFINITIONS

IT Change Request Form: Form used for recording the change request and used for seeking proper approval for the change request.

Unit Test and System Integration Test Script: User Acceptance Test (UAT) Script: Scripts used to record details of test

results conducted by the authorized application users. Application Release Form: Form used for recording the release and used for

seeking proper approval prior to the actual release deployment.

4. RESPONSIBILITIES

Responsibilities are detailed in the flow chart and notes below. <If there are responsibilities which are not defined in the process flow, please define them here>

When printed, this document is uncontrolled unless properly identified as controlled.






Lim Hock Chee

Role

Task

Application Owner / Client Sponsor

Authorized User Lead

IT Management

CMM IT Representative

Application Developer

Change Request Form

A R A/C C R/C

Developer / Vendor Test Scripts

I C I C A/R

User Acceptance Test

A R C C S/C

R – ResponsibleA – AccountableS – SupportI – InformC – Consult







Lim Hock Chee

5. PROCESS DESCRIPTION

A. Process Flow

Process Workflow (High Level)







Lim Hock Chee

B. Activity Description

Change Request

1. Whenever there is any change request to the application system, the user lead will need to submit the change request to the corresponding Change Committee for approval.

The Change Committee consists of the Key Business Owner, IT Management.

Upon approval of the change request, the change request will be passed to the IT team to follow-up.

2. If the change request is rejected, it will be feedback to the user.

3. Certain application issues rectification will require modification to the programs.

4. All approved change request will go through the Application System Development Life Cycle.

5. The Developer/Vendor needs to complete their respective unit test and system integration test based on the test scenarios defined in the test scripts.

6. When the system integration test has completed successfully, the new applications/patches/upgrades will be deployed into the testing/staging server for user to conduct the User Acceptance Test.

Staging/Testing Environment

7. The authorized user will proceed to perform the UAT on the new applications/patches/upgrades. Only when the UAT is successful, the authorized UAT user lead will signed off the UAT scripts. The UAT will also need to be approved by the Application Owner/Project Owner.

8. CMM IT Representative/IT Project Manager will plan the outage (If required) together with the Application Owner/Project Owner.







Lim Hock Chee

9. The Application Release Form must be sign-off and approved by the various parties.Authorized By: Application Owner/Project OwnerReleased By: CMM IT Representative / IT Project ManagerVerified By: User Lead

** The CMM IT Representative/IT Project Manager is not a developer.

10. A backup of the affected programs and database (If required) will be performed by the IT Administrator.

11. CMM IT Representative will proceed to deploy the new applications/patches/upgrades into the production environment.

Production Environment

12. The User Lead will perform a verification of the new release in the production environment

13. If there is no problem with the new release, the CMM IT Representative will announce the availability of the application to the rest of the authorized users.

14. All the control documents will be updated accordingly. Example: Issue Log, Change Request Log, Application Release Log.

6. REFERENCES/SOURCE MATERIALS

Short Name Description File NameUAT Script Test Script For User Acceptance TestApplication Release Form Form for authorizing

applications/patches/upgrades release into the production environment

7. REVISION RECORD

Reason for Revision Effective Date Person Responsible


program change monitoring procedure

Documents