As per distribution of maintenance effort, which type of maintenance has consumed minimum share

The Four Types Of Software Maintenance & How They Help Your Organization

The life of your software does not begin when coding starts and end with the launch. Instead, it has an ongoing lifecycle that stops and starts whenever necessary. The start of its lifecycle and a good portion of the work begins at launch.

Software is always changing and as long as it is being used, it has to be monitored and maintained properly. This is partly to adjust for the changes within an organization but is even more important because technology keeps changing.

Your software may need maintenance for any number of reasons – to keep it up and running, to enhance features, to rework the system for changes into the future, to move to the Cloud, or any other changes. Whatever the motivation is for software maintenance, it is vital for the success of your business. As such, software maintenance is more than simply finding and fixing bugs. It is keeping the heart of your business up and running.

There are four types of software maintenance:

• Corrective Software Maintenance
• Adaptive Software Maintenance
• Perfective Software Maintenance
• Preventive Software Maintenance

Corrective Software Maintenance

Corrective software maintenance is what one would typically associate with the maintenance of any kind. Correct software maintenance addresses the errors and faults within software applications that could impact various parts of your software, including the design, logic, and code. These corrections usually come from bug reports that were created by users or customers – but corrective software maintenance can help to spot them before your customers do, which can help your brand’s reputation.

Adaptive Software Maintenance

Adaptive software maintenance becomes important when the environment of your software changes. This can be brought on by changes to the operating system, hardware, software dependencies, Cloud storage, or even changes within the operating system. Sometimes, adaptive software maintenance reflects organizational policies or rules as well. Updating services, making modifications to vendors, or changing payment processors can all necessitate adaptive software maintenance.

Perfective Software Maintenance

Perfective software maintenance focuses on the evolution of requirements and features that existing in your system. As users interact with your applications, they may notice things that you did not or suggest new features that they would like as part of the software, which could become future projects or enhancements. Perfective software maintenance takes over some of the work, both adding features that can enhance user experience and removing features that are not effective and functional. This can include features that are not used or those that do not help you to meet your end goals.

Preventive Software Maintenance

Preventative Software Maintenance helps to make changes and adaptations to your software so that it can work for a longer period of time. The focus of the type of maintenance is to prevent the deterioration of your software as it continues to adapt and change. These services can include optimizing code and updating documentation as needed.

Preventative software maintenance helps to reduce the risk associated with operating software for a long time, helping it to become more stable, understandable, and maintainable.

For all businesses and organizations, software maintenance is an essential part of the software development lifecycle. This isn’t something that one can skip or avoid. It is absolutely necessary for the success of your software and any evolution into the future. It is important to know that maintenance needs to go much further than fixing issues or bugs – that is only one steps of the software maintenance process.

Updating software environments, reducing deterioration, and enhancing what is already there to help satisfy the needs of all users are also included in the software maintenance examples.

For more information, see our eBook 20 Software Engineering Goals for the Digital Economy.

Describes how to set up the system, customize it tolocal hardware needs and configure it to particularhardware and other software systems.Provides simple explanations of how to start usingthe system.Provides in depth description of each system facilityand how it can be used.Booklet Contains a summary of new features.Serves as a factual lookup.Provides information on services such as net-working, security and upgrading.

61Software Engineering (3rded.), By K.K Aggarwal & Yogesh Singh, Copyright © New Age International Publishers, 2007Software MaintenanceSoftware MaintenanceSoftware MaintenanceSoftware Maintenancesquare4System DocumentationIt refers to those documentation containing all facets of system, includinganalysis, specification, design, implementation, testing, security, errordiagnosis and recovery.

62Software Engineering (3rded.), By K.K Aggarwal & Yogesh Singh, Copyright © New Age International Publishers, 2007Software MaintenanceSoftware MaintenanceSoftware MaintenanceSoftware Maintenancesquare4System Documentation4.3.2.1.FunctionDocumentS.No.System RationaleSRSSpecification/ DesignImplementationDescribes the objectives of the entire system.Provides information on exact requirements ofsystem as agreed between user and developers.Provides description of:(i)How system requirements are implemented.(ii) How the system is decomposed into a set ofinteracting program units.(iii)The function of each program unit.Provides description of:(i)How the detailed system design is expressed insome formal programming language.(ii) Program actions in the form of intra programcomments.

63Software Engineering (3rded.), By K.K Aggarwal & Yogesh Singh, Copyright © New Age International Publishers, 2007Software MaintenanceSoftware MaintenanceSoftware MaintenanceSoftware Maintenance7.6.5.FunctionDocumentS.No.System Test PlanAcceptance Test PlanData DictionariesProvides description of how program units aretested individually and how the whole system istested after integration.Describes the tests that the system must passbefore users accept it.Contains description of all terms that relate to thesoftware system in question.Table 6:System Documentation

64Software Engineering, By K.K Aggarwal &Yogesh Singh, New Age International Publishers9.1Process of generating analysis and design documents is called(a) Inverse Engineering(b) Software Engineering(c) Reverse Engineering(d) Re-engineering9.2Regression testing is primarily related to(a) Functional testing(b) Data flow testing(c) Development testing(d) Maintenance testing9.3Which one is not a category of maintenance ?(a) Corrective maintenance(b) Effective maintenance(c) Adaptive maintenance(d) Perfective maintenance9.4The maintenance initiated by defects in the software is called(a) Corrective maintenance(b) Adaptive maintenance(c) Perfective maintenance(d) Preventive maintenanceMultiple Choice QuestionsNote: Choose most appropriate answer of the following questions:9.5Patch is known as(a) Emergency fixes(b) Routine fixes(c) Critical fixes(d) None of the above

65Software Engineering, By K.K Aggarwal &Yogesh Singh, New Age International Publishers9.6Adaptive maintenance is related to(a) Modification in software due to failure(b) Modification in software due to demand of new functionalities

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 75 pages?

Upload your study docs or become a

Course Hero member to access this document

Tags

Software engineering, New Age International, Age International Publishers, Yogesh Singh, New Age International Publishers

Which type of maintenance has consumed maximum share?

Which category of maintenance consumes maximum effort and why?

What are the 4 types of system maintenance?

What is perfective maintenance?