Software Maintenance & Change Control Plan

Table of Contents 1.         Purpose         3 1.1.          nourishment         3 1.2.          reposition chink         3 2.         Scope         4 3.          join on Documentation         4 4.         Change Management Process         5 4.1.         Softw ar Change Request         5 4.2.         Analysis and Prioritization         5 4.3.         Development and Testing         5 4.4.         Implementation         6 5.          sustain Policies         6 5.1.         Transition bit         6 5.2.         Support Procedure         7 6.         Project randomness Location         7 7.         Signoffs         7 Software Maintenance & Change Control think 1.         Purpose The bearing of this inscription is to provide corporate guidelines for package system maintenance and sort reign over servicees. 1.1.         Maintenance Maintenance embroils routine updates, version upgrades, and enhancements. As defined in deb Staceys Software Maintenance document, maintenance can be defined as four activities: Corrective Maintenance: A exercise that includes diagnosis and correction of errors. Adaptive Maintenance: natural dish up that modifies software to flop interface with a changing environment (hardware and software). Perfective Maintenance: Activity for adding new capabilities, modifying existing functions and make general enhancements. This accounts for the majority of in all effort expended on maintenance. Preventive Maintenance: Activity which changes software to correct approaching maintainability or reliability or to provid e a ameliorate basis for future enhancement! s. 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 convoluted with the instruction execution of a change request. Change Control recognizes the need for edition to externally imposed change, and looks for opportunities for internally instigated change. It is refer non exclusively with adaptation of an applications existing functions, but likewise with its extension to include new functions (Clarke, 1990). 2.         Scope The scope of this document is intended to cover whatsoever software changes which do not involve new software implementation or culture within the corporation; altogether modifications or enhancements to an existing system. If you require to get a copious essay, order it on our website: BestEssayCheap.com

If you want to get a full essay, visit our page: cheap essay