Software Reuse and Productivity: An Empirical View

  • Thomas P. Frazier
Conference paper


Software reuse, by which we mean the reuse of existing software code or design, has gained a great deal of attention because it seems to offer a way to attain substantial increases in software development productivity. Under the reuse paradigm the software developer would select from libraries or repositories of software components and build his program “component-by-component” instead of via the traditional method of writing code “line-by-line.” A component could be an existing standard mathematical or statistical routine, utilities related to operating systems, or even an entire program. Also, there are different levels or degrees of reuse. Some components can be reused verbatim while others must be modified before being incorporated into the new program.


Ordinary Little Square Source Line Ordinary Little Square Model Software Reuse Software Development Project 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    Boehm, B. W., and P.N. Papaccio. “Understanding and Controlling Software Costs,” IEEE Transactions on Software Engineering, vol. 14, no. 10, October 1988.Google Scholar
  2. [2]
    Cruickshank, R. D., and J. E. Gaffhey. “An Economics Model of Software Reuse.” Proceedings, Conference on Analytical Methods in Software Engineering Economics, McLean, VA, April 1991.Google Scholar
  3. [3]
    Kang, K. C., and L. S. Levy. “Software Methodology in the Harsh Light of Economics.” Information and Software Technology, vol. 31, no. 5, June 1989.Google Scholar
  4. [4]
    Boehm, B. W., and W. E. Royce. “Ada, COCOMO and the Ada Process Model.” Proceedings, Fifth International COCOMO User’s Group Meeting, SEI, Pittsburgh, PA, October 1989.Google Scholar
  5. [5]
    Pamas, D. “Design of Program Families,” IEEE Transactions on Software Engineering, vol 2, no. 1, June 1976.Google Scholar
  6. [6]
    Garnett, E. S., and J. A. Mariani. “Software Reclamation,” Software Engineering Journal, vol. 5, no. 3, May 1990.Google Scholar
  7. [7]
    Tracz, W. (ed.). Software Reuse Emerging Technology. IEEE Computer Society Press, 1988.Google Scholar
  8. [8]
    Humphrey, W. S., and N. D. Singpurwalla. “Predicting (Individual) Software Productivity,” IEEE Transactions on Software Engineering, vol. 17, no. 2, February 1991.Google Scholar
  9. [9]
    Banker, R. D., and C. F. Kemerer. “Scale Economies in New Software Development,” IEEE Transactions on Software Engineering, vol. 15, no. 10, October 1989.Google Scholar
  10. [10]
    Selby, R. W. “Empirically Analyzing Software Reuse in a Production Environment” in Tracz, W. (ed), Software Reuse Emerging Technology, IEEE Computer Society Press, 1988.Google Scholar
  11. [11]
    Levitan, K. B., J. Salasin, T. P. Frazier, and B. N. Angier. “Final Report on the Status of Software Obsolescence in the DoD.” Paper P-2136, Institute for Defense Analyses, August 1988.Google Scholar
  12. [12]
    Defense Logistics Agency. “DoD Automated Resources Management System (ARMS) Users Guide.” April 1985.Google Scholar
  13. [13]
    Boehm, B. W., Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.Google Scholar
  14. [14]
    Boehm, B.W., and W. L. Scherlis. “Megaprogramming.” Mimeograph, undatedGoogle Scholar

Copyright information

© Springer-Verlag Berlin · Heidelberg 1994

Authors and Affiliations

  • Thomas P. Frazier
    • 1
  1. 1.Institute for Defense AnalysesAlexandriaUSA

Personalised recommendations