Scribd
Upload
2 views20 pages

Ch9. Evolution Short

Chapter 9 discusses software evolution, emphasizing the inevitability of software change due to new requirements, environmental shifts, and the need for maintenance. It outlines the importance of evolving existing software systems to maintain their value as critical business assets and describes various maintenance types, including fault repairs and functionality modifications. The chapter also covers reengineering and refactoring processes aimed at improving software maintainability and addressing code degradation.

Uploaded by

mabbas20031
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
2 views20 pages

Ch9. Evolution Short

Chapter 9 discusses software evolution, emphasizing the inevitability of software change due to new requirements, environmental shifts, and the need for maintenance. It outlines the importance of evolving existing software systems to maintain their value as critical business assets and describes various maintenance types, including fault repairs and functionality modifications. The chapter also covers reengineering and refactoring processes aimed at improving software maintainability and addressing code degradation.

Uploaded by

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

Chapter 9 – Software Evolution

30/10/2014 Chapter 9 Software Evolution 1


Topics covered

 Evolution processes
 Software maintenance

30/10/2014 Chapter 9 Software Evolution 2


Software change

 Software change is inevitable


 New requirements emerge when the software is used;
 The business environment changes;
 Errors must be repaired;
 New computers and equipment is added to the system;
 The performance or reliability of the system may have to be
improved.
 A key problem for all organizations is implementing and
managing change to their existing software systems.

30/10/2014 Chapter 9 Software Evolution 3


Importance of evolution

 Organizations have huge investments in their software


systems - they are critical business assets.

 To maintain the value of these assets to the business,


they must be changed and updated.

 The majority of the software budget in large companies


is devoted to changing and evolving existing software
rather than developing new software.

30/10/2014 Chapter 9 Software Evolution 4


Evolution and servicing

30/10/2014 Chapter 9 Software Evolution 5


Evolution and servicing

 Evolution
 The stage in a software system’s life cycle where it is in
operational use and is evolving as new requirements are
proposed and implemented in the system.
 Servicing
 At this stage, the software remains useful but the only changes
made are those required to keep it operational i.e. bug fixes and
changes to reflect changes in the software’s environment. No
new functionality is added.
 Phase-out
 The software may still be used but no further changes are made
to it.

30/10/2014 Chapter 9 Software Evolution 6


Evolution processes

30/10/2014 Chapter 9 Software Evolution 7


Evolution processes

 Software evolution processes depend on


 The type of software being maintained;
 The development processes used;
 The skills and experience of the people involved.
 Proposals for change are the driver for system evolution.
 Should be linked with components that are affected by the
change, thus allowing the cost and impact of the change to be
estimated.
 Change identification and evolution continues throughout
the system lifetime.

30/10/2014 Chapter 9 Software Evolution 8


The software evolution process

30/10/2014 Chapter 9 Software Evolution 9


Change implementation

30/10/2014 Chapter 9 Software Evolution 10


Software maintenance

30/10/2014 Chapter 9 Software Evolution 11


Software maintenance

 Modifying a program after it has been put into use.


 The term is mostly used for changing custom software.
Generic software products are said to evolve to create
new versions.
 Maintenance does not normally involve major changes to
the system’s architecture.
 Changes are implemented by modifying existing
components and adding new components to the system.

30/10/2014 Chapter 9 Software Evolution 12


Types of maintenance

 Fault repairs
 Changing a system to fix bugs/vulnerabilities and correct
deficiencies in the way meets its requirements.
 Environmental adaptation
 Maintenance to adapt software to a different operating
environment
 Changing a system so that it operates in a different environment
(computer, OS, etc.) from its initial implementation.
 Functionality addition and modification
 Modifying the system to satisfy new requirements.

30/10/2014 Chapter 9 Software Evolution 13


Maintenance effort distribution

30/10/2014 Chapter 9 Software Evolution 14


Software reengineering

 Restructuring or rewriting part or all of a legacy system


without changing its functionality.

 Applicable where some but not all sub-systems of a


larger system require frequent maintenance.

 Reengineering involves adding effort to make


them easier to maintain. The system may be re-
structured and re-documented.

30/10/2014 Chapter 9 Software Evolution 15


The reengineering process

30/10/2014 Chapter 9 Software Evolution 16


Reengineering process activities

 Source code translation


 Convert code to a new language.
 Reverse engineering
 Analyse the program to understand it;
 Program structure improvement
 Restructure automatically for understandability;
 Program modularisation
 Reorganise the program structure;
 Data reengineering
 Clean-up and restructure system data.

30/10/2014 Chapter 9 Software Evolution 17


Refactoring

 Refactoring is the process of making improvements to a


program to slow down degradation through change.
 You can think of refactoring as ‘preventive maintenance’
that reduces the problems of future change.
 Refactoring involves modifying a program to improve its
structure, reduce its complexity or make it easier to
understand.
 When you refactor a program, you should not add
functionality but rather concentrate on program
improvement.

30/10/2014 Chapter 9 Software Evolution 18


Refactoring and reengineering

 Re-engineering takes place after a system has been


maintained for some time and maintenance costs are
increasing. You use automated tools to process and re-
engineer a legacy system to create a new system that is
more maintainable.
 Refactoring is a continuous process of improvement
throughout the development and evolution process. It is
intended to avoid the structure and code degradation
that increases the costs and difficulties of maintaining a
system.

30/10/2014 Chapter 9 Software Evolution 19


‘Bad smells’ in program code

 Duplicate code
 The same or very similar code may be included at different
places in a program. This can be removed and implemented as
a single method or function that is called as required.
 Long methods
 If a method is too long, it should be redesigned as a number of
shorter methods.
 Data clumping
 Data clumps occur when the same group of data items (fields in
classes, parameters in methods) re-occur in several places in a
program. These can often be replaced with an object that
encapsulates all of the data.

30/10/2014 Chapter 9 Software Evolution 20

You might also like