Access control is the collection of mechanisms that permits managers of a system to exercise a directing or restraining influence over the behavior, use, and content of a system. It permits management to specify what users can do, which resources they can access, and what operations they can perform on a system.
Change management deals with how changes to the system are managed so they don't degrade system performance and availability. Change management is especially critical in today's highly decentralized, network-based environment where users themselves may be applying many changes. A key cause of high cost of ownership is the application of changes by those who don't fully understand their implications across the operating environment.
In effective change management, all changes should be identified and planned for prior to implementation. Back-out procedures should be established in case changes create problems. Then, after changes are applied, they are thoroughly tested and evaluated. This article describes the process steps for change management and factors critical to its success.
Step 1: Define change management process and practices
As you would with other systems management disciplines, you must first craft a plan for handling changes that covers: Procedures for handling changes—how changes are requested, how they are processed and scheduled for implementation, how they are applied, and what the criteria are for backing out changes that cause problems Roles and responsibilities of the IT support staff—who receives the change request, who tracks all change requests, who schedules change implementations, and what each entity is supposed to do Measurements for change management—what will be tracked to monitor the efficiency of the change management discipline Tools to be used
Type of changes to be handled and how to assign priorities—priority assignment methodology and escalation guidelines Back-out procedures—Actions to take if applied...
Please join StudyMode to read the full document