Skip to main content

Abstract

This paper presents new studies and experiences that enhance the use of the inspection process and improve its contribution to development of defect-free software on time and at lower costs. Examples of benefits are cited followed by descriptions of the process and some methods of obtaining the enhanced results.

Software inspection is a method of static testing to verify that software meets its requirements. It engages the developers and others in a formal process of investigation that usually detects more defects in the product—and at lower cost—than does machine testing. Users of the method report very significant improvements in quality that are accompanied by lower development costs and greatly reduced maintenance efforts. Excellent results have been obtained by small and large organizations in all aspects of new development as well as in maintenance. There is some evidence that developers who participate in the inspection of their own product actually create fewer defects in future work. Because inspections formalize the development process, productivity and quality enhancing tools can be adopted more easily and rapidly.

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. L. H. Fenton, “Response to the SHARE software service task force report,” IBM Corp., Kingston, NY, Mar. 6, 1984.

    Google Scholar 

  2. M. E. Fagan, “Design and code inspections to reduce errors in program devclopment,” IBM Syst. J., vol. 15, no. 3, 1979.

    Google Scholar 

  3. IBM Technical Newsletter GN20-3814, Base Publication GC20-2000-0, Aug. 15, 1978.

    Google Scholar 

  4. T. D. Crossman, “Inspection teams, are they worth it?” in Proc. 2nd Nat. Symp. EDP Quality Assurance, Chicago, IL, Mar. 24-26, 1982.

    Google Scholar 

  5. R. R, Larson, “Test plan and test case inspection specification,” IBM Corp., Tech. Rep. TR21.585, Apr. 4, 1975.

    Google Scholar 

  6. T. D. Crossman, “Some experiences in the use of inspection teams in application development,” in Proc. Applicat. Develop. Symp., Monterey, CA, 1979.

    Google Scholar 

  7. G. D. Brown and D. H. Sefton, “The micro vs. the applications logjam,” Datamation, Jan, 1984.

    Google Scholar 

  8. J. H. Morrissey and L. S.-Y. Wu, “Software engineering: An economical perspective,” in Proc. IEEE Conf. Software Eng., Munich, West Germany, Sept. 14-19, 1979.

    Google Scholar 

  9. B. Bochm et al., Characteristics of Software Quality. New York: American Elsevier, 1978.

    Google Scholar 

  10. F. O. Buck, “Indicators of quality inspections,” IBM Corp., Tech. Rep. IBM TR21. 802, Sept. 1981.

    Google Scholar 

  11. K. Ishikawa, Guide to Quality Control. Tokyo, Japan: Asian Productivity Organization, 1982.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2001 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Fagan, M.E. (2001). Advances in Software Inspections. In: Broy, M., Denert, E. (eds) Pioneers and Their Contributions to Software Engineering. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-48354-7_14

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-48354-7_14

  • Publisher Name: Springer, Berlin, Heidelberg

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

  • Online ISBN: 978-3-642-48354-7

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics