Change Control Procedures - 7 Simple Steps to Manage Application Change Control
Change Control Procedures - 7 Simple Steps to Manage Application Change Control
Applications and softwares are a critical component of any organization. Changes in information technology, requires constant changes and upgradations of the applications in use. Organizations face the risk that such changes to applications might not be properly controlled. Change control becomes an important part of a application SDLC project. A Change Control System is thus a set of formally documented procedures which
helps in streamlining the entire application change process. Below, I have listed down 7 simple steps which form part of the change control process.
1. A change request is submitted to project management based on the user requirements.
2. The change request is reviewed by the project management. If approved, such change requests are then forwarded to the application development team.
3. The change request submitted is analyzed by the development team. A feasibility report is made considering factors such as cost, time involved, resource requirement etc.
4. Development management submits such feasibility report to user management who decides whether to go ahead with the changes or not.
5. Application developers are assigned the development work according to the change request.
6. Application changes are tested first by application developers and later on by user called as user acceptance testing.
7. The new functionality is then rolled out in the production environment or as part of the new application.
Related Posts
Deploying an Intrusion Detection System
COBIT - IT Control Framework
ROSI - Return on Security Investment
Information Technology Tips - Database Replication
Feedback awaiting moderation
This post has 14 feedbacks awaiting moderation...