• Corpus ID: 18117844

Lifetime and its Evolution Process over Generations

  title={Lifetime and its Evolution Process over Generations},
  author={Tetsuo Tamai and Yohsuke Torimitsu},
Software evolution process does not end at the death of an individual software system but usually continues its evolution over generations through being replaced by newly built software. To explore this research topic, we conducted a survey collecting data of software lifetimes, replacement practices and factors of replacement. In this paper, we report the results of the survey and discuss some possible long range strategies for software life cycle planning and control based on our findings. 
2 Citations

Figures and Tables from this paper

Reverse engineering is reverse forward engineering

  • I. BaxterM. Mehlich
  • Computer Science
    Proceedings of the Fourth Working Conference on Reverse Engineering
  • 1997
A by-product of the transformational reverse engineering process is a design database for the program that can be maintained to minimize the need for further reverse engineering during the remaining lifetime of the system.

Survive Another Day: Using Changes in the Composition of Investments to Measure the Cost of Credit Constraints

Abstract We introduce a novel empirical strategy to measure the size of credit shocks. Theoretically, we show that credit shocks reduce the value of long-term relative to short-term investments.



Insights on improving the maintenance process through software measurement

It is suggested that early identification of change-prone modules through the use of change measures across release cycles can be an effective technique in allocating maintenance resources.

On understanding laws, evolution, and conservation in the large-program life cycle

  • M. Lehman
  • Environmental Science
    J. Syst. Softw.
  • 1980

A cost analysis of the software dilemma: to maintain or to replace

  • A. BaruaT. Mukhopadhyay
  • Business
    [1989] Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences. Volume III: Decision Support and Knowledge Based Systems Track
  • 1989
An analytical model is developed for determining the optimal rewriting time for two rewriting strategies involving two different technologies and several interesting propositions with managerial implications emerge.

Program lifetime: a vital statistic for maintenance

  • J. Foster
  • Law
    Proceedings. Conference on Software Maintenance 1991
  • 1991
It is concluded that measurement of average program lifetime is likely to be a better indicator of maintenance improvements than overall maintenance costs.

Viewing maintenance as reuse-oriented software development

An improvement paradigm that helps organizations evaluate, learn, and enhance their software processes and products; a reuse-oriented evolution environment that encourages and supports reuse; and automated support for the paradigm and environment as well as for measurement and evaluation are discussed.

A Model of Large Program Development

Observations made on the development of OS/360 and its subsequent enhancements and releases are discussed and some modeling approaches to organizing these observations are presented.

Software maintenance management

Findings and Recommendations from a Software Reengineering Case Study

  • Proc. the Second Annual Systems Reengineering Workshop
  • 1991

Why does Software Die?

  • Proc. 67th Infotech State of the Art Conference
  • 1979