Skip to main content

Analyzing software Reuse at the project and module design levels

  • VII — Re-Use
  • Conference paper
  • First Online:
ESEC '87 (ESEC 1987)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 289))

Included in the following conference series:

Abstract

Reusing software may be the catalyst that helps the software community achieve large improvements in software productivity and quality. The purpose of this study is to characterize software reuse empirically by investigating one development environment that actively reuses software. Twenty-five software systems ranging from 3000 to 112,000 source lines have been selected for analysis from a NASA production environment. The amount of software either reused or modified from previous systems averages 32% per project in this environment. Analysis of variance models are applied to examine 46 dependent variables across the 7188 software modules in the systems. The analysis focuses on the characterization of software reuse at the project and module design levels.

This work was supported in part by National Science Foundation grant DCR-8521398.

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

Access this chapter

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Ted Biggerstaff, editor. Proceedings of the Workshop on Reusability in Programming. ITT, Shelton, Conn., 1983.

    Google Scholar 

  2. B. W. Boehm. Software Engineering Economics. Prentice-Hall, Englewood Cliffs, NJ, 1981.

    Google Scholar 

  3. Grady Booch. Object-oriented development. IEEE Transactions on Software Engineering, SE-12(2):211–221, February 1986.

    Google Scholar 

  4. Ted Biggerstaff and Alan Perlis, editors. IEEE Transactions on Software Engineering. SE-10(5), Special Issue on Software Reusability, September 1984.

    Google Scholar 

  5. Ted Biggerstaff and Charles Richter. Reusability framework, assessment, and directions. IEEE Software, 4(2):41–49, March 1987.

    Google Scholar 

  6. V. R. Basili, R. W. Selby, and T. Y. Phillips. Metric analysis and data validation across fortran projects. IEEE Trans. Software Engr., SE-9(6):652–663, Nov. 1983.

    Google Scholar 

  7. V. R. Basili and D. M. Weiss. A methodology for collecting valid software engineering data. Trans. Software Engr., SE-10(6):728–738, Nov. 1984.

    Google Scholar 

  8. V. R. Basili, M. V. Zelkowitz, F. E. McGarry, Jr. R. W. Reiter, W. F. Truszkowski, and D. L. Weiss. The Software Engineering Laboratory. Technical Report SEL-77-001, Software Eng. Lab., NASA/Goddard Space Flight Center, Greenbelt, MD, May 1977.

    Google Scholar 

  9. W. G. Cochran and G. M. Cox. Experimental Designs. John Wiley & Sons, New York, 1950.

    Google Scholar 

  10. D. N. Card, F. E. McGarry, J. Page, S. Eslinger, and V. R. Basili. The Software Engineering Laboratory. Technical Report SEL-81-104, Software Eng. Lab., NASA/Goddard Space Flight Center, Greenbelt, MD, Feb. 1982.

    Google Scholar 

  11. R. Conn. An overview of the dod ada software repository. Dr. Dobbs Journal, 60–61,86–91, February 1986.

    Google Scholar 

  12. W. J Decker and W. A. Taylor. FORTRAN Static Source Code Analyzer Program (SAP) User's Guide (Revision 1). Technical Report SEL-78-102, Software Eng. Lab., NASA/Goddard Space Flight Center, Greenbelt, MD, May 1982.

    Google Scholar 

  13. A. N. Habermann and D. Notkin. Gandalf: software development environments. IEEE Transactions on Software Engineering, SE-12(12), December 1986.

    Google Scholar 

  14. Gail E. Kaiser and David Garlan. Melding software systems from reusable building blocks. IEEE Software, 4(4):17–24, July 1987.

    Google Scholar 

  15. Bertrand Meyer. Reusability: the case for object-oriented design. IEEE Software, 4(2):50–64, March 1987.

    Google Scholar 

  16. James Neighbors. The Draco approach to constructing software from reusable components. IEEE Transactions on Software Engineering, SE-10(5):564–573, September 1984.

    Google Scholar 

  17. L. J. Osterweil. Software processes are software too. In Proc. Ninth Int. Conf. Software Engr., pages 2–13, Monterey, CA, March 30–April 2, 1987.

    Google Scholar 

  18. T. Reps. Generating Language-Based Environments. M.I.T. Press, Cambridge, Mass., 1983.

    Google Scholar 

  19. H. Scheffe. The Analysis of Variance. John Wiley & Sons, New York, 1959.

    Google Scholar 

  20. SEL. Annotated Bibliography of Software Engineering Laboratory (SEL)Literature. Technical Report SEL-82-006, Software Eng. Lab., NASA/Goddard Space Flight Center, Greenbelt, MD, Nov. 1982.

    Google Scholar 

  21. Will Tracz. Ada reusability efforts: a survey of the state of the practice. In Proceedings of the Fifth National Conference on Ada Technology, Arlington, VA, March 1987.

    Google Scholar 

  22. Will Tracz, editor. IEEE Software. 4(4), Special Issue on Software Reusability, July 1987.

    Google Scholar 

  23. C. E. Walston and C. P. Felix. A method of programming measurement and estimation. IBM Systems J., 16(1):54–73, 1977.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Howard Nichols Dan Simpson

Rights and permissions

Reprints and permissions

Copyright information

© 1987 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Selby, R.W. (1987). Analyzing software Reuse at the project and module design levels. In: Nichols, H., Simpson, D. (eds) ESEC '87. ESEC 1987. Lecture Notes in Computer Science, vol 289. Springer, Berlin, Heidelberg. https://doi.org/10.1007/BFb0022114

Download citation

  • DOI: https://doi.org/10.1007/BFb0022114

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-18712-7

  • Online ISBN: 978-3-540-48117-1

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics