SOFTWARE MAINTENANCE

Dr.G.Jose Moses
B.Tech(CSE).,M.Tech(CSE).,Ph.D(CSE).,LMCSI.,MBA(F&M).,Ph.D(MBA).

Professor of CSE
Recognised Research Supervisor of JNTUK & GIETU
Raghu Engineering College(Autonomous)
Visakhapatnam
Mobile:+91-9701329977.
Software Maintenance: Software maintenance, Maintenance Process
Models, Maintenance Cost, Reengineering, Reengineering activities,
Software Reuse.
Software Maintenance is a process of modifying a software system after
the delivery to correct faults, improve or other attributes.

Software Product vs Software Maintenance

Software Product It is the result of the software development.

Software Maintenance it results in a service being delivered to the

customer.
Software Maintenance:
Software maintenance is a part of Software Development Life Cycle.
Its main purpose is to modify and update software application after delivery
to correct faults and to improve performance.
Software maintenance is a vast activity which includes optimization, error
correction, and deletion of discarded features and enhancement of existing
features.
Since these changes are necessary, a mechanism must be created for
estimation, controlling and making modifications.
The essential part of software maintenance requires preparation of an
accurate plan during the development cycle.
Typically, maintenance takes up about 40-80% of the project cost.
It stands for all the modifications and updations done after the delivery of
software product.
Types of Software Maintenance Activities:
Corrective: Taking existing code and correcting a fault that deviates from
its document requirement.
Adaptive: Adding new features to the existing code.
Perfective: Typically made to improve the maintainability of code
Inspection: These are usually made as a result of code inspection to
reduce the likelihood of a failure.
Corrective Maintenance - This includes modifications and updations done in order to correct or fix
problems, which are either discovered by user or concluded by user error reports.
Adaptive Maintenance - This includes modifications and updations applied to keep the software
product up-to date and tuned to the ever changing world of technology and business environment.
Adaptive maintenance is the implementation of changes in a part of the system, which has been
affected by a change that occurred in some other part of the system. Adaptive maintenance consists
of adapting software to changes in the environment such as the hardware or the operating system.
Perfective Maintenance - This includes modifications and updates done in order to keep the
software usable over long period of time. It includes new features, new user requirements for
refining the software and improve its reliability and performance. Perfective maintenance mainly
deals with implementing new or changed user requirements. This includes enhancing both the
function and efficiency of the code and changing the functionalities of the system as per the users'
changing needs.
Preventive Maintenance - This includes modifications and updations to prevent future problems of
the software. It aims to attend problems, which are not significant at this moment but may cause
serious issues in future. Preventive maintenance involves performing activities to prevent the
occurrence of errors. It tends to reduce the software complexity thereby improving program
understandability and increasing software maintainability. It comprises documentation updating,
code optimization, and code restructuring. Documentation updating involves modifying the
documents affected by the changes in order to correspond to the present state of the system. Code
optimization involves modifying the programs for faster execution or efficient use of storage space.
Software Maintenance Process

Maintenance Process vary considerably depending on the type of

software being maintained.

The most expensive part of software life cycle is software maintenance

Software Maintenance Process Models

Maintenance Process Models:

Studies suggest that the software maintenance process begins without proper
knowledge of the software system. This occurs because the software maintenance
team is unaware of the requirements and design documentation. Also, traditional
models fail to capture the evolutionary nature of the software.
To overcome these problems, software maintenance models have been proposed,
which include
quick fix model
iterative enhancement model
reuse-oriented model
Quick fix model
The quick-fix model is an ad hoc approach used for maintaining the software system.
The objective of this model is to identify the problem and then fix it as quickly as
possible.
The advantage is that it performs its work quickly and at a low cost.
This model is an approach to modify the software code with little consideration for its
impact on the overall structure of the software system.

Sometimes, users do not wait for long time. Rather, they require the modified software
system to be delivered to them in the least possible time. As a result, the software
maintenance team needs to use a quick-fix model to avoid the time consuming process
of SMLC.
This model is beneficial when a single user is using the software system. As the user has
proper knowledge of the software system, it becomes easier to maintain the software
system without having need to manage the detailed documentation.
This model is also advantageous in situations when the software system is to be
maintained with certain deadlines and limited resources. However, this model is not
suitable to fix errors for a longer period.
The iterative enhancement model:
The iterative enhancement model can be easily adapted for maintaining a
software system.
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.
In the analysis stage, the requirements are analyzed to begin the software
maintenance process. After analysis, the requested modifications are
classified according to the complexity, technical issues, and identification of
modules that will be affected. At the end, the software is modified to
implement the modification request. At each stage, the documentation is
updated to accommodate changes of requirements analysis, design, coding,
and testing phases.
Note: It is essential to have a complete documentation before the
implementation of iterative enhancement model begins.
The Reuse-oriented Model
The reuse-oriented model assumes that the existing program components
can be reused to perform maintenance.
It consists of the following steps.
Identifying the components of the old system which can be reused
Understanding these components
Modifying the old system components so that they can be used in the new
system
Integrating the modified components into the new system.
Define Re Engineering.
When we need to update the software to keep it to the current market,
without impacting its functionality, it is called software re-engineering. It is
a thorough process where the design of software is changed and programs
are re-written.
Reengineering Activities:
Reverse Engineering
It is a process to achieve system specification by thoroughly analyzing,
understanding the existing system. This process can be seen as reverse SDLC
model, i.e. we try to get higher abstraction level by analyzing lower
abstraction levels.
An existing system is previously implemented design, about which we know
nothing. Designers then do reverse engineering by looking at the code and
try to get the design. With design in hand, they try to conclude the
specifications. Thus, going in reverse from code to system specification.
Program Restructuring
It is a process to re-structure and re-construct the existing software. It is all
about re-arranging the source code, either in same programming language or
from one programming language to a different one. Restructuring can have
either source code-restructuring and data-restructuring or both.
Re-structuring does not impact the functionality of the software but enhance
reliability and maintainability. Program components, which cause errors very
frequently can be changed, or updated with re-structuring.
The dependability of software on obsolete hardware platform can be
removed via re-structuring.
Forward Engineering
Forward engineering is a process of obtaining desired software from the
specifications which were brought down by means of reverse engineering. It
assumes that there was some software engineering already done in the past.
Forward engineering is same as software engineering process with only one
difference – it is carried out always after reverse engineering.
Component reusability
A component is a part of software program code, which executes an
independent task in the system. It can be a small module or sub-system
itself.
Software Reuse
A definition of software reuse is the process of creating software systems from predefined software
components.
The advantage of software reuse:
The systematic development of reusable components.
The systematic reuse of these components as building blocks to create new systems.
A reusable component may be code, but the bigger benefits of reuse come from a broader and higher-
level view of what can be reused. Software specifications, designs, tests cases, data, prototypes, plans,
documentation, frameworks, and templates are all candidates for reuse.

Software reuse can cut software development time and costs.

The major advantages for software reuse are to:
Increase software productivity.
Shorten software development time.
Improve software system interoperability.
Develop software with fewer people.
Move personnel more easily from project to project.
Reduce software development and maintenance costs.
Produce more standardized software.
Produce better quality software and provide a powerful competitive advantage.
 THANK YOU
STAY HOME STAY SAFE