Skip to main content

Software Maintenance

  • Chapter
  • 439 Accesses

Part of the book series: Applications of Modern Technology in Business ((AMTB))

Abstract

Software maintenance consumes 60–80% of most companies’ software budgets (Freedman and Weinberg; 1982; Parikh 1982), the largest single item contribut-ing to high software costs (Yau and Tsai, 1986). U.S. corporations now spend $30 billion annually on software maintenance and, by 1995, the process of fixing and upgrading aging applications software programs will employ 90% of all software resources (Moad, 1990). New code is added faster than old code is discarded, increasing the maintainable systems base. Moreover, growth in system size averages 10% per year (Swanson and Beath, 1990) and maintenance expenditures generally increase as systems age. Large multinational corpora-tions require a 15% increase in programming staff every year just to meet growing maintenance needs (Jones, 1986). And the introduction of fourth-generation languages has not curbed the growth in maintenance requirements (Chapin, 1984; Lehner, 1990; Parikh, 1986).

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  • Adams, E. N., “Optiniizing Preventive Service of Software Products,” IBM J. Systems Develop. 28(1), (January 1984), 2–14.

    Article  Google Scholar 

  • Baker, C. T., “Effects of Field Service on Software Reliability,” IEEE Trans. Software Engrg. SE-14(2), (February 1988), 254–258.

    Article  Google Scholar 

  • Brooks, F., “No Silver Bullet: Essence and Accidents of Software Engineering,” IEEE Computer, April, 1987, pp. 10–19.

    Google Scholar 

  • Chapin, N., “Software Maintenance with Fourth-Generation Languages,” Software Engrg. Notes 9(1), (January 1984), 41–42.

    Article  Google Scholar 

  • Elmer-Dewitt, P., “Ghost in the Machine,” Time, January 29, 1990, pp. 58–59.

    Google Scholar 

  • Freedman, D. P. and G. M. Weinberg, “Maintenance Reviews,” in Techniques of Program and System Maintenance, (G. Parikh, ed.), Cambridge, MA: Winthrop, 1982, pp. 53–55.

    Google Scholar 

  • Jones, C., Programming Productivity, New York: McGraw-Hill, 1986.

    Google Scholar 

  • Lehner, F., “Cost Comparison for the Development and Maintenance of Application Systems in 3rd and 4th Generation Languages,” Information and Management, 1990, pp. 131–141.

    Google Scholar 

  • Lientz, B. P, “Issues in Software Maintenance,” Computing Surveys 15(3), (September 1983), 271–278.

    Article  Google Scholar 

  • Lientz, B. E and E. B. Swanson, Software Maintenance Management, Reading, MA: Addison-Wesley, 1980.

    Google Scholar 

  • Lindhorst, W. M., “Scheduled Program Maintenance,” in Techniques of Program and System Maintenance (G. Parikh, ed.) Cambridge, MA: Winthrop, 1982, pp. 129–132.

    Google Scholar 

  • Moad, J., “Maintaining the Competitive Edge,” Datamation February 15, 1990, pp. 61–66.

    Google Scholar 

  • Musa, J. D., A. Iannino, and K. Okumoto, Software Reliability: Measurement, Prediction, New York: McGraw-Hill, 1987.

    Google Scholar 

  • Parikh, G., The Guide to Software Maintenance, Cambridge, MA: Winthrop, 1982.

    Google Scholar 

  • Parikh, G., Handbook of Software Maintenance, New York: Wiley, 1986.

    Google Scholar 

  • Schneidewind, N. F., “The State of Software Maintenance,” IEEE Trans. Software Engrg. SE-13(3), (March 1987), 303–310.

    Article  Google Scholar 

  • Swanson, E. B. and C. M. Beath, “Departmentalization in Software Development and Maintenance,” Comm.ACM 33(6), (June, 1990), 658–667.

    Article  Google Scholar 

  • Vallabhaneni, S. R., Auditing the Maintenance of Software, Englewood Cliffs, NJ: Prentice-Hall, 1987.

    Google Scholar 

  • Weinberg, G. M., “Worst-First Maintenance,” in Techniques of Program and System Maintenance (G. Parikh, ed.), Cambridge, MA: Winthrop, 1982.

    Google Scholar 

  • Yau, S.S. and T. J. Tsai, “A Survey of Software Design Techniques,” IEEE Trans. Software Engrg. SE-12(6), (June 1986), 713–721.

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 1992 Springer Science+Business Media New York

About this chapter

Cite this chapter

Sherer, S.A. (1992). Software Maintenance. In: Software Failure Risk. Applications of Modern Technology in Business. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-3020-6_10

Download citation

  • DOI: https://doi.org/10.1007/978-1-4615-3020-6_10

  • Publisher Name: Springer, Boston, MA

  • Print ISBN: 978-1-4613-6316-3

  • Online ISBN: 978-1-4615-3020-6

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics