scispace - formally typeset
Proceedings ArticleDOI

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

A. Barua, +1 more
- Vol. 3, pp 89-98
Reads0
Chats0
TLDR
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.
Abstract
The authors develop an analytical model for determining the optimal rewriting time. They consider two rewriting strategies involving two different technologies. Several interesting propositions with managerial implications emerge from the analysis. These include the impacts of increasing maintenance requirements and unstructuredness of the technology on the optimal rewriting time, the differences in replacement times for the two technologies, and the effects of system integration requirements on replacement decisions. >

read more

Citations
More filters
Journal ArticleDOI

System life expectancy and the maintenance effort: exploring their equilibration

TL;DR: Support is found for an exploratory structural equation model in which the relationship between maintenance effort and remaining life expectancy is newly explained, and it is suggested that better documented and monitored portfolios, together with regular, periodic performance assessments, can lead to better management of systems' life cycles.
Proceedings ArticleDOI

Software lifetime and its evolution process over generations

TL;DR: Some possible long-range strategies for software life cycle planning and control based on the findings of the survey are discussed; management by lifetime characteristics, monotonicity of size growth, and reuse.
Journal ArticleDOI

Comparing uniform and flexible policies for software maintenance and replacement

TL;DR: Results from the model show that the traditional practice of maintaining or replacing a software system at uniform time intervals may not be optimal, and that an increase in software reuse leads to more frequent replacement, but the number of maintenance activities is not significantly impacted.
Journal ArticleDOI

What is your software worth

TL;DR: In this article, a method is presented for valuing software based on the income that use of the software is expected to generate in the future, by applying well-known principles of intellectual property valuation, sales expectations, growth of maintained software, discounting to present value, and the like.
Posted Content

What is Your Software Worth

TL;DR: By applying well-known principles of intellectual property valuation, sales expectations, growth of maintained software, discounting to present value, and the like, a method is presented for valuing software based on the income that use of the software is expected to generate in the future.
References
More filters
Journal ArticleDOI

Structured design

TL;DR: Considerations and techniques are proposed that reduce the complexity of programs by dividing them into functional modules, which can make it possible to create complex systems from simple, independent, reusable modules.
Journal ArticleDOI

Programs, life cycles, and laws of software evolution

TL;DR: By classifying programs according to their relationship to the environment in which they are executed, the paper identifies the sources of evolutionary pressure on computer applications and programs and shows why this results in a process of never ending maintenance activity.
Proceedings ArticleDOI

The dimensions of maintenance

TL;DR: Some measures are suggested for coming to grips with the “dimensionality” of the maintenance problem, and problems of utilization associated with these measures are explored.
Book

Information systems management in practice

TL;DR: In this article, the authors give readers conceptual and practical guidelines for dealing with the management of today's information systems function and present a framework that provides guidance for readers, using profiles of actual work as a key element of the overall learning process.
Related Papers (5)