Big4Guy

Welcome to Big4Guy.com. Big4Guy is an online resource where I will share with you the latest news, insights, knowledge and some experiences as a Big 4 consultant. We will discuss some of the important issues which organisations are facing today in the areas of information security, security and controls in SAP R/3, Oracle Applications, J.D.Edwards, Peoplesoft and various other ERP's. You will also find information on latest complaince regulations like Sarbanes Oxley, Basel II and so on. Big4guy will also attempt to provide valuable resources for individuals interested in examinations the CISA, CISM, CISSP, PMP and various other security certifications considered essential for entry in any Big 4 accounting, auditing and consulting firms. You are invited to post your comments and viewpoints to posts here. I sincerely hope this online journal will be useful to everyone from a budding student to a professional in the accounting, auditing, management and consultancy professions.

Post details: Change Control Procedures - 7 Simple Steps to Manage Application Change Control

02/24/06

Permalink 10:44:37 pm, Categories: Information Security, 234 words   English (US)

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

Comments:

No Comments for this post yet...

Official Websites

Search

Google

Web Big4Guy.com

January 2009
Mon Tue Wed Thu Fri Sat Sun
<<  <   >  >>
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

Misc

Syndicate this blog XML

What is RSS?