Scribd
Upload
53 views17 pages

12-DPSI-Software Evolution

The document discusses software evolution and program evolution dynamics. It covers topics like change processes for software systems, understanding software evolution, and Lehman's laws of software evolution. Some key points are that software change is inevitable due to new requirements and environment changes. The majority of software budgets are spent on evolving existing software rather than new development. Lehman's laws state that software evolution is continuous and complexity increases over time as systems adapt to their environment.

Uploaded by

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

12-DPSI-Software Evolution

The document discusses software evolution and program evolution dynamics. It covers topics like change processes for software systems, understanding software evolution, and Lehman's laws of software evolution. Some key points are that software change is inevitable due to new requirements and environment changes. The majority of software budgets are spent on evolving existing software rather than new development. Lehman's laws state that software evolution is continuous and complexity increases over time as systems adapt to their environment.

Uploaded by

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

Software Evolution

Dasar Pengembangan Sistem Informasi


Fajar Pradana S.ST., M.Eng
Topics covered
• Evolution processes
 Change processes for software systems
• Program evolution dynamics
 Understanding software evolution
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.
Importance of evolution
• Organisations 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.
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.
Change identification and evolution processes
The software evolution process
Change implementation
Change implementation
• Iteration of the development process where the revisions to the
system are designed, implemented and tested.
• A critical difference is that the first stage of change implementation
may involve program understanding, especially if the original
system developers are not responsible for the change
implementation.
• During the program understanding phase, you have to understand
how the program is structured, how it delivers functionality and
how the proposed change might affect the program.
Urgent change requests
• Urgent changes may have to be implemented without going
through all stages of the software engineering process
 If a serious system fault has to be repaired to allow normal operation
to continue;
 If changes to the system’s environment (e.g. an OS upgrade) have
unexpected effects;
 If there are business changes that require a very rapid response
(e.g. the release of a competing product).
The emergency repair process
Program evolution dynamics
• Program evolution dynamics is the study of the processes of
system change.
• After several major empirical studies, Lehman and Belady
proposed that there were a number of ‘laws’ which applied to all
systems as they evolved.
• There are sensible observations rather than laws. They are
applicable to large systems developed by large organisations.
 It is not clear if these are applicable to other types of software
system.
Change is inevitable
• The system requirements are likely to change while the system is
being developed because the environment is changing. Therefore
a delivered system won't meet its requirements!
• Systems are tightly coupled with their environment. When a
system is installed in an environment it changes that environment
and therefore changes the system requirements.
• Systems MUST be changed if they are to remain useful in an
environment.
Lehman’s laws
Law Description
Continuing A program that is used in a real-world environment must
change necessarily change, or else become progressively less useful in
that environment.

Increasing As an evolving program changes, its structure tends to become


complexity more complex. Extra resources must be devoted to preserving
and simplifying the structure.

Large program Program evolution is a self-regulating process. System


evolution attributes such as size, time between releases, and the number
of reported errors is approximately invariant for each system
release.
Organizational Over a program’s lifetime, its rate of development is
stability approximately constant and independent of the resources
devoted to system development.
Lehman’s laws
Law Description

Conservation of Over the lifetime of a system, the incremental


familiarity change in each release is approximately constant.

Continuing growth The functionality offered by systems has to


continually increase to maintain user satisfaction.

Declining quality The quality of systems will decline unless they are
modified to reflect changes in their operational
environment.
Feedback system Evolution processes incorporate multiagent,
multiloop feedback systems and you have to treat
them as feedback systems to achieve significant
product improvement.
Key Points
• Software development and evolution can be thought of as an
integrated, iterative process that can be represented using a spiral
model.
• For custom systems, the costs of software maintenance usually
exceed the software development costs.
• The process of software evolution is driven by requests for
changes and includes change impact analysis, release planning
and change implementation.
• Lehman’s laws, such as the notion that change is continuous,
describe a number of insights derived from long-term studies of
system evolution.
17

Terima Kasih
Ada Pertanyaan

You might also like