Software Maintenance & Change Control Plan

Essay by casper8106University, Bachelor'sA+, June 2004

download word file, 3 pages 4.0

Downloaded 315 times

Table of Contents

1. Purpose 3

1.1. Maintenance 3

1.2. Change Control 3

2. Scope 4

3. Reference Documentation 4

4. Change Management Process 5

4.1. Software Change Request 5

4.2. Analysis and Prioritization 5

4.3. Development and Testing 5

4.4. Implementation 6

5. Support Policies 6

5.1. Transition Procedure 6

5.2. Support Procedure 7

6. Project Information Location 7

7. Signoffs 7

Software Maintenance & Change Control Plan

1. Purpose

The intention of this document is to provide corporate guidelines for software maintenance and change control processes.

1.1. Maintenance

Maintenance includes routine updates, version upgrades, and enhancements. As defined in Deb Stacey's Software Maintenance document, maintenance can be defined as four activities:

Corrective Maintenance: A process that includes diagnosis and correction of errors.

Adaptive Maintenance: Activity that modifies software to properly interface with a changing environment (hardware and software).

Perfective Maintenance: Activity for adding new capabilities, modifying existing functions and making general enhancements.

This accounts for the majority of all effort expended on maintenance.

Preventive Maintenance: Activity which changes software to improve future maintainability or reliability or to provide a better basis for future enhancements.

1.2. Change Control

Change control activities are defined as the policy, rules, procedures, information, activities, roles, authorization levels, and states relating to creation, updates, approvals, tracking and archiving of items involved with the implementation of a change request.

"Change Control recognizes the need for adaptation to externally imposed change, and looks for opportunities for internally instigated change. It is concerned not only with adaptation of an application's existing functions, but also with its extension to include new functions" (Clarke, 1990).

2. Scope

The scope of this document is intended to cover any software changes which do not involve new software implementation or development within the corporation; only modifications or enhancements to an existing...