Software engineers have traditionally considered any work after initial
delivery as simply software maintenance. Some researchers have divided
this work into various tasks, including making changes to functionality
(perfective), changing the environment (adaptive), correcting errors
(corrective), and making improvements to avoid future problems (preventive).
However, many have considered maintenance basically uniform over
time. Because software development has changed considerably since
its early days, the authors believe this approach no longer suffices.
They describe a new view of the software life cycle in which maintenance
is actually a series of distinct stages, each with different activities,
tools, and business consequences. While the industry still considers
postdelivery work as simply software maintenance, the authors claim
that the process actually falls into stages. They think both business
and engineering can benefit from understanding these stages and
their transitions
%0 Journal Article
%1 rajlich00
%A Rajlich, V. T.
%A Bennett, K. H.
%D 2000
%J IEEE Computer
%K maintenance evolution software taxonomy
%N 7
%P 66--71
%T A staged model for the software life cycle
%U http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=869374
%V 33
%X Software engineers have traditionally considered any work after initial
delivery as simply software maintenance. Some researchers have divided
this work into various tasks, including making changes to functionality
(perfective), changing the environment (adaptive), correcting errors
(corrective), and making improvements to avoid future problems (preventive).
However, many have considered maintenance basically uniform over
time. Because software development has changed considerably since
its early days, the authors believe this approach no longer suffices.
They describe a new view of the software life cycle in which maintenance
is actually a series of distinct stages, each with different activities,
tools, and business consequences. While the industry still considers
postdelivery work as simply software maintenance, the authors claim
that the process actually falls into stages. They think both business
and engineering can benefit from understanding these stages and
their transitions
@article{rajlich00,
abstract = {Software engineers have traditionally considered any work after initial
delivery as simply software maintenance. Some researchers have divided
this work into various tasks, including making changes to functionality
(perfective), changing the environment (adaptive), correcting errors
(corrective), and making improvements to avoid future problems (preventive).
However, many have considered maintenance basically uniform over
time. Because software development has changed considerably since
its early days, the authors believe this approach no longer suffices.
They describe a new view of the software life cycle in which maintenance
is actually a series of distinct stages, each with different activities,
tools, and business consequences. While the industry still considers
postdelivery work as simply software maintenance, the authors claim
that the process actually falls into stages. They think both business
and engineering can benefit from understanding these stages and
their transitions},
added-at = {2006-09-18T06:26:07.000+0200},
author = {Rajlich, V. T. and Bennett, K. H.},
biburl = {https://www.bibsonomy.org/bibtex/25c7d7ef7914f4bdebab41b996de83d19/neilernst},
citeulike-article-id = {765119},
description = {Not previously uploaded},
interhash = {7d717c566bd0490759dd4d03a7b9a80c},
intrahash = {5c7d7ef7914f4bdebab41b996de83d19},
journal = {IEEE Computer},
keywords = {maintenance evolution software taxonomy},
number = 7,
pages = {66--71},
priority = {0},
timestamp = {2006-09-18T06:26:07.000+0200},
title = {A staged model for the software life cycle},
url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=869374},
volume = 33,
year = 2000
}