Explain software maintenance ? explain its various types of models ?

Software maintenance process starts without proper information of the software system. This happens in light of the fact that the product support group is unconscious of the necessities and outline documentation. Likewise, traditional models neglect to catch the transformative idea of the product. To beat these issues, software maintenance models have been proposed.

These are:-

1. Quick fix model
2. Iterative enhancement model
3. Reuse-oriented model.

Quick fix model

The Quick fix model is a specially appointed approach utilized for keeping up the product framework. The target of this model is to recognize the issue and afterward settle it as fast as could be allowed.

The advantage is that it plays out its work rapidly and with ease. This model is a way to deal with adjusting the product code with little thought for its effect on the general structure of the product framework.

Now and again, clients don’t sit tight for a long time. Or maybe, they require the adjusted programming framework to be conveyed to them at all conceivable time. Thus, the product support group needs to utilize a handy solution model to dodge the tedious procedure of SMLC.

This model is advantageous when a solitary client is utilizing the product framework. As the client has appropriate learning of the product framework, it ends up noticeably less demanding to keep up the product framework without having a need to deal with the point by point documentation.

This model is likewise invaluable in circumstances when the product framework is to be kept up with specific due dates and constrained assets. In any case, this model is not reasonable to settle mistakes for a more extended period.

This model is likewise invaluable in circumstances when the product framework is to be kept up with specific due dates and constrained assets. In any case, this model is not reasonable to settle mistakes for a more extended period.

 

Iterative enhancement model:-

The Iterative enhancement model, which was initially proposed as a procedure show, can be effortlessly adjusted for keeping up a product framework. It considers that the progressions made to the product framework are iterative in nature.

The Iterative enhancement model includes three phases:-

1. Investigation of programming framework
2. Order of asked for changes
3. Usage of asked for alterations.

In the investigation organize, the prerequisites are broke down to start the product support process. After examination, the asked for changes are ordered by the unpredictability, specialized issues, and ID of modules that will be influenced. Toward the end, the product is altered to execute the alteration ask. At each stage, the documentation is refreshed to oblige changes of necessities examination, plan, coding, and testing stages.

Note: It is fundamental to have an entire documentation before the execution of iterative upgrade show starts.

Reuse-oriented model

The reuse-arranged model accepts that the current program segments can be reused to perform upkeep.

It consists of the following steps.

1. Identifying the segments of the old framework which can be reused
2. Understanding these segments
3. Modifying the old framework segments with the goal that they can be utilized as a part of the new framework
4. Integrating the altered parts into the new framework.