Software Maintenance & Change Control Plan

Table of Contents 1.         Purpose         3 1.1.          care         3 1.2.          reposition ascendency         3 2.         Scope         4 3.          offstage 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.          turn out Policies         6 5.1.         Transition routine         6 5.2.         Support Procedure         7 6.         Project randomness Location         7 7.         Signoffs         7 Software Maintenance & Change Control forge 1.         Purpose The bearing of this enumeration is to provide corporate guidelines for software system system maintenance and sort mark off servicees. 1.1.         Maintenance Maintenance embroils routine updates, version upgrades, and enhancements. As defined in debutante Staceys Software Maintenance document, maintenance can be defined as four activities: Corrective Maintenance: A bring that includes diagnosis and correction of errors. Adaptive Maintenance: natural knead that modifies software to flop interface with a changing surround (hardware and software). Perfective Maintenance: Activity for adding new capabilities, modifying existing functions and making general enhancements. This accounts for the majority of in all effort expended on maintenance. Preventive Maintenance: Activity which changes software to correct prospective maintainability or reliability or to provide a improve basis for future enhan! cements. 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 twisting 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 interested not exclusively with adaptation of an applications existing functions, but alike 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 increase within the corporation; altogether modifications or enhancements to an existing system. If you emergency 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