Software Maintenance & Change Control Plan

868 words - 3 pages

Table of Contents1. Purpose 31.1. Maintenance 31.2. Change Control 32. Scope 43. Reference Documentation 44. Change Management Process 54.1. Software Change Request 54.2. Analysis and Prioritization 54.3. Development and Testing 54.4. Implementation 65. Support Policies 65.1. Transition Procedure 65.2. Support Procedure 76. Project Information Location 77. Signoffs 7Software Maintenance & Change Control Plan1. PurposeThe intention of this document is to provide corporate guidelines for software maintenance and change control processes.1.1. MaintenanceMaintenance 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 ControlChange 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. ScopeThe 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 system.3. Reference DocumentationStacey, Deb (July 1995). Software Maintenance. Retrieved May 16, 2004 from http://hebb.cis.uoguelph.ca/~dave/27320/quality/maintain.html.Clarke, Roger (July 1990). Exploiting the Application Software Portfolio Through Change Control and Configuration Management. Retrieved May 16, 2004 http://www.anu.edu.au/people/Roger.Clarke/SOS/ChgeCtl90.html.Francis (not dated). Software Development Process. Retrieved May 16, 2004 from http://www.cms.livjm.ac.uk/library/cd1001-Hulya%20Francis/lecture%209-maintenance.ppt.Francis (not dated). "The Maintenance Process"4. Change Management ProcessThe process for maintenance of software systems and requesting changes to existing systems is defined as follows:4.1. Software Change RequestA Software Change Request (see Figure 1) is submitted to the Systems Development Team (SDT) to request changes in existing software design (new...

Find Another Essay On Software Maintenance & Change Control Plan

Software life cycle Essay

966 words - 4 pages model has its use. We can not deliver waterfall model is not useful although it has some weakness, because it had been used widely last 20 years because of it support structural software design and can control complexity of software. If we focus on the development and maintenance of a diverse range of software products, waterfall model will be not appropriate. We must use more flexible development model to achieve maintenance and diverse range of

Open Source Software vs. Microsoft Empire

3381 words - 14 pages Open Source Software vs. Microsoft Empire Introduction “I think that to try to own knowledge, to try to control whether people are allowed to use it, or to try to stop other people from sharing it, is sabotage. It is an activity that benefits the person that does it at the cost of impoverishing all of society. One person gains one dollars by destroying two dollars’ worth of wealth. I think a person with a conscience wouldn’t do that sort

Maintenance Management Systems

1986 words - 8 pages . Control the issue and documentation of planned and unplanned maintenance work. Organise the maintenance personnel database including shift work schedules Schedule calibration for gauges and instruments Control portable appliance testing (PAT) Provide maintenance costing statistics Tool to analysis tools for maintenance performance. There are four types of CMM software: (A) Single site single user systems. (B) Multiple

Software Methodologies

2088 words - 8 pages off and a bit about what’s currently the standards of companies providing software development like ISO and CMMI. Keywords: Waterfall, Spiral, Agile, Scrum. Software development methodologies, developing software, project phases, initiate, scope, plan, execute, control and monitor, close, transition, maintenance phase. Numerous software methodologies have been presented to the world to foster standards for systems

Evaluating IT Service Management Standards in an Operation.

5772 words - 23 pages configuration items and IT services that are affected by any change. Planning and testing the change is part of change management as well as having a plan if change results in any unexpected state.1.4 Incident Management/Help DeskHelp desk is the first point of contact available to business users in their IT services when problems occur. Incident control and communications are the main focuses of the help desk according to www.bs15000.org.uk. There are many

Configuration Control Process

1875 words - 8 pages ; unmanaged change is very possibly the largest single cause of failure to deliver systems on time and within budget.SCM is the process that has been developed to control and manage change. Change is inevitable during the software development life cycle. Changes to the software come from both external and internal sources. External changes originate from users, from evolution of operational environments, and from improvements in technology. Internal

Software licenseing and piracy act for a business lay class

3694 words - 15 pages . Product delivery for software is made up of a number of different components, which are referred to as 'software licensing'. The following factors are taken into consideration whendetermining a cost for a 'software license'; physical delivery pricing, metric discounts, license periods support and maintenance, license management Tech support, change in use bug fixes and Platform Migration Product enhancements. The most commonly found type of

servic level

829 words - 3 pages Application Release Management 106. Metadata Change Management 117. Known Operational Exceptions 128. Managing and Tracking Project Control Items 139. APMS 14Revision Log 15Appendices 16Approval 1. IntroductionInsert text here.1.1 PurposeInsert text here.1.2 In ScopeInsert text here.1.3 Out of scopeInsert text here.1.4 Intended audienceInsert text here.2. Roles and responsibilities for Maintenance and Support of2.1 Service levelsThe maintenance and support

How To Create A Disaster Recovery Plan

1834 words - 7 pages disaster recovery coordinator should oversee this step. 1. Review changes in the environment, technology, and procedures. 2. Develop maintenance triggers and procedures. 3. Submit changes for systems development procedures. 4. Modify unit change management procedures. 5. Produce plan updates and distribute. 6. Establish period review and update procedures.

Software Localization Systems

1547 words - 7 pages whether to outsource localization of a piece of software is a difficult one to make. This applies to both development and maintenance. Keeping the localization in-house means that experts on the localized software are within the company and more control can be kept over the software. This is expensive and people with the right expertise on localization may not be available within the company. There are advantages to outsourcing such as the lower

my view on social networking

3862 words - 15 pages effectively reflect equipment operating condition of the diaphragm. This system is not only simple and stable, but also can predict pump failure effectively, so that it reduces equipment downtime, plan maintenance time and unplanned maintenance time. FAST FOURIER TRANSFORM (FFT) In the actual industrial pipeline, there are strict requirements on the size of particles and the concentration for the transported material. The pipeline is a closed

Similar Essays

Software Maintenance And Change Control Essay

2362 words - 9 pages Software Maintenance PAGE 1 Running head: SOFTWARE MAINTENANCE AND CHANGE CONTROLSoftware Maintenance and Change Control Plan for McBride Financial ServicesIntroductionMcBride Financial Services, located in the mid-western United States, is a low cost mortgage services provider, specializing in conventional, VA and FHA loans and refinancing. Credit reporting, home inspection and appraisal services are offered at a fixed price along with

Software Maintenance Plan Essay

1259 words - 5 pages PAGE PAGE 4 Software Maintenance Plan Software Maintenance Plan - McBride Financial ServicesUniversity of PhoenixPOS/370AbstractPer Service Request, SR-mf-004, McBride Financial Services has requested a software maintenance and change control plan be developed. This plan is in anticipation of new software developments within the organization. Currently all software support for McBride Financial is outsourced to Smith Systems

Economic Consequences Of Software Crime. Essay

1269 words - 5 pages software development firm, all of these have high administrative costs in regards to software programs. Software licensing policies were originally a result of software developer's need to protect their revenue base in the face of potential piracy.The following factors are taken into consideration when determining a cost for a software license; physical delivery pricing, metric discounts, license periods support and maintenance, license

Understanding The Software Development Process Essay

1285 words - 5 pages the full life cycle of a software product, whether the product is considered as standalone or part of a system. The standard describes the requirements of a software reliability program to define, meet, and demonstrate assurance of software product reliability using a Plan-Case framework and implemented within the context of a system application. Plan-Case: The plan provides the reliability process, activities and performance requirements