Scribd
Upload
225 views

Software Maintenance Models

The document discusses five models of software maintenance: the quick-fix model, iterative enhancement model, re-use oriented model, Boehm's model, and Taute maintenance model. It describes the key aspects of each model, including their approaches, steps, and phases. The quick-fix model takes an ad-hoc firefighting approach, while the iterative enhancement and re-use oriented models incorporate reusing existing components. Boehm's model represents maintenance in an approval-execution cycle, and Taute's model consists of eight phases from change request to operation. The importance of each model depends on the project size, with quick-fix only suitable for small projects and iterative enhancement for small-medium projects.

Uploaded by

Jai Chaudhry
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
225 views

Software Maintenance Models

The document discusses five models of software maintenance: the quick-fix model, iterative enhancement model, re-use oriented model, Boehm's model, and Taute maintenance model. It describes the key aspects of each model, including their approaches, steps, and phases. The quick-fix model takes an ad-hoc firefighting approach, while the iterative enhancement and re-use oriented models incorporate reusing existing components. Boehm's model represents maintenance in an approval-execution cycle, and Taute's model consists of eight phases from change request to operation. The importance of each model depends on the project size, with quick-fix only suitable for small projects and iterative enhancement for small-medium projects.

Uploaded by

Jai Chaudhry
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

There are a

number of models of maintenance that serve to


organize the five main tasks of the phase:
isolating and analyzing the problem, designing a
fix, implementing this fix, testing the resulting
system, and updating documentation to reflect
the changes made.

The purpose of software maintenance is to preserve the value of software over time,
which can accomplished by:

1) Expanding the customer base.


2) Enhancing software’s capabilities.
3) Omitting obsolete capabilities.
4) Employing newer technology.

Maintenance Models

1) Quick-fix Model :
This is basically an adhoc approach to maintaining software. It is a fire
fighting approach, waiting for the problem to occur and then trying to fix it
as quickly as possible.

2) Iterative Enhancement Model :


It considers that the changes made to the software system are iterative in nature.
The iterative enhancement model comprises three stages, namely, analysis of
software system, classification of requested modifications, and implementation of
requested modifications.

3) The Re-use Oriented Model:

This model is based on the principle that maintenance could be viewed as an


activity involving the reuse of existing program components.
Steps in this model:
1) Identification of parts of the old system that are candidates for reuse
2) Understanding these system parts
3) Modification of the old system parts appropriate to the new requirements.
4) Integration of the modified parts into the new system

4) Boehm's Model:
Boehm’s Model performs maintenance process based on the economic models and
principles. It represents the maintenance process in a closed loop cycle, wherein
changes are suggested and approved first and then are executed.

5) Taute Maintenance Model:


Named after the person who proposed the model, Taute’s model is a typical
maintenance model that consists of eight phases in cycle fashion. The process of
maintenance begins by requesting the change and ends with its operation

Phases in this model:


1) Change request phase
2) Estimate phase
3) Schedule Phase
4) Programming Phase
5) Test Phase
6) Documentation Phase
7) Release Phase
8) Operation phase

Importance of each of the models :

1) Quick and easy for small projects but useless in big projects.
2) Easy to implement/follow for when size of project is between small to medium.
3) Previous things made are integrated into modified parts into the new system, so
saves a lot of time and money.
4) Continuous evolving maintenance
5) Easy to understand and implement.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy