ON THE ECONOMICS OF THE-SOFTWARE REPLACEMENT PROBLEM

Proceedings of the 11th International Conference on Information Systems, ICIS 1990

Volumn , Issue , 1990, Pages 159-170

  Gode, Dhananjay K ^a   Barua, Anitesh ^a   Mukhopadhyay, Tridas ^a  

^a CARNEGIE MELLON UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

BUDGET CONTROL; COMPUTER SOFTWARE MAINTENANCE; ECONOMICS; LIFE CYCLE;

ECONOMIC MODELS; ECONOMIC SENSE; MAINTENANCE COST; MAINTENANCE STRATEGIES; REWRITING STRATEGIES; SHARP INCREASE; SOFTWARE REPLACEMENT; SYSTEM SIZE; SYSTEMS COMPLEXITY; TECHNICAL ASPECTS;

COSTS;

EID: 33747358067     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (25)

1. Banker, R. D.; Datar, S. M.; and Kemerer, C. F. "A Model to Evaluate Factors Impacting the Productivity of Software Maintenance Projects." Working paper #2093- 88, Massachusetts Institute of Technology Sloan School of Management, 1988.
2. Banker, R. D.; Datar, S. M.; and Zweig, D. "Software Complexity and Maintainability." In J. I. DeGross, J. C. Henderson, and B. R. Konsynski (eds.), Proceedings of the Tenth International Conference on Information Systems, Boston, December 1989, pp. 247-255.
3. Barua, A., and Mukhopadhyay, T. "A Cost Analysis of the Software Dilemma: To Maintain or to Replace." Proceedings of the Twenty-Second Hawaii International Conference on Systems Sciences, January 1989.
4. Bcrgland, G. D. "A Guided Tour of Program Design Methodologies." IEEE Computer, October 1981, pp. 13-37.
5. Boehm, B. Software Engineering Economics. Englewood Cliffs, New Jersey: Prentice Hall, 1981.
6. Boehm, B. "Improving Software Productivity.” IEEE Computer, September 1987, pp. 43-57.
7. Curtis, B.; Sheppard, S. B.; Milliman, P.; Borst, M. A.; and Love, T. "Measuring the Psychological Complexity of Software Maintenance Tasks with the Halstead and Mc­Cabe Metrics.” IEEE Transactions on Software Engineering, Volume SE-5, Number 2, March 1979, pp. 96-104.
8. Gurbaxani, V., and Mendelson, H. "Software and Hard­ware in Data Processing Budgets." IEEE Transactions on Software Engineering, Volume SE-J3, Number 3, March 1987, pp. 1010-1017.
9. Kafura, D., and Reddy, G. "The Use of Software Com­plexity Metrics in Software Maintenance." IEEE Trans­actions on Software Engineering, Volume SE-13, Number 3, March 1987, pp. 335-343.
10. Kemerer, C. F. Measurement of Software Development Productivity. Unpublished Ph.D. Dissertation, Graduate School of Industrial Administration, Carnegie Mellon University, Pittsburgh, Pennsylvania, April 1987.
11. Lehman, M. "Programs, Life Cycles, and Laws of Software Evolution." In G. Parikh and N. Zvegintzov (eds.), Tutorial on Software Maintenance, Los Angeles: IEEE Computer Society, 1982, pp. 199-215.
12. Lientz, B. P.; Swanson, E. B.; and Tompkins, G. E. "Characteristics of Application Software Maintenance." Communications of ACM, Volume 21, Number 6, June 1978, pp. 466-471.
13. Martin, J. Fourth Generation Languages Volume I, Principles. Englewood Cliffs, New Jersey: Prentice Hall, Inc., 1985.
14. Rudolph, E. E. "Productivity in Computer Application Development." University of Auckland, New Zealand, 1984.
15. Schneidewind, N. "The State of Software Maintenance." IEEE Transactions on Software Engineering, Volume SE- 13, Number 3, March 1987, pp. 303-310.
16. Sprague, R. H., and McNurlin, B. C. (Editors) Information Systems Management in Practice. Englewood Cliffs, New Jersey: Prentice Hall, 1986.
17. Swanson, E. B. "The Dimensions of Maintenance." Proceedings of the Second International Conference on Software Engineering, 1976, pp. 492-497.
18. Swanson, E. B., and Beath, C. M. Maintaining Information Systems in Organizations. New York: John Wiley and Sons, 1979.
19. Yao, S. S., and Collofello, J. "Some Stability Measures for Software Maintainers." IEEE Transactions on Software Engineering, Volume SE-6, Number 6, November 1980.
20. Advanced technologies such as 4GLs have been found to make programming less time consuming (Martin 1985; Rudolph 1984), although the economic issues such as initial acquisition and learning costs have not been investigated.
21. Without assuming a restrictive functional form, we only utilize the signs of the first and second deriva­tives.
22. It is assumed that both of the systems are developed in a structured manner within the limits of techno­logies A and B.
23. For example, the number of function points or source lines of code modified or added.
24. In this paper, we consider a complete rewrite of the software. On the other hand, a partial rewrite will be affected more directly by the state of the system. An analysis of partial rewriting is suggested as an extension in Section 4.
25. It will be equal if maintenance involves only modifi­cations. Enhancements to the system increase the functionality.