Detecting defects in object-oriented designs: using reading techniques to increase software quality

ABSTRACT

Inspections can be used to identify defects in software artifacts. In this way, inspection methods help to improve software quality, especially when used early in software development. Inspections of software design may be especially crucial since design defects (problems of correctness and completeness with respect to the requirements, internal consistency, or other quality attributes) can directly affect the quality of, and effort required for, the implementation.We have created a set of “reading techniques” (so called because they help a reviewer to “read” a design artifact for the purpose of finding relevant information) that gives specific and practical guidance for identifying defects in Object-Oriented designs. Each reading technique in the family focuses the reviewer on some aspect of the design, with the goal that an inspection team applying the entire family should achieve a high degree of coverage of the design defects.In this paper, we present an overview of this new set of reading techniques. We discuss how some elements of these techniques are based on empirical results concerning an analogous set of reading techniques that supports defect detection in requirements documents. We present an initial empirical study that was run to assess the feasibility of these new techniques, and discuss the changes made to the latest version of the techniques based on the results of this study.

REFERENCES

• 1: Basili, V. R., Green S., Laitenberger, O., Lanubile, F., Shull, F., Sorumgard, S., Zelkowitz, M. V.. The Empirical Investigation of Perspective-Based Reading, Empirical Software Engineering Journal, I, 133-164, 1996
• 2: Basili, V., Caldiera, G., Lanubile, F., and Shull, F.. Studies on reading techniques. In Proc. of the Twenty- First Annual Software Engineering Workshop, SEL- 96-002, pages 59-65, Greenbelt, MD, December 1996.
• 3: Peter Coad , Edward Yourdon, Object-oriented analysis (2nd ed.), Yourdon Press, Upper Saddle River, NJ, 1991
• 4: Fagan, M., 1976. Design and code inspections to reduce errors in program development. IBM Systems Journal, 15(3):182-211
• 5: M E Eagan, Advances in software inspections, IEEE Transactions on Software Engineering, v.12 n.7, p.744-751, July 1986
• 6: Martin Fowler , Kendall Scott, UML distilled: applying the standard object modeling language, Addison-Wesley Longman Ltd., Essex, UK, 1997
• 7: Pierfrancesco Fusaro , Filippo Lanubile , Giuseppe Visaggio, A Replicated Experiment to Assess Requirements InspectionTechniques, Empirical Software Engineering, v.2 n.1, p.39-57, 1997 [doi>10.1023/A:1009742216007]
• 8: Tom Gilb , Dorothy Graham , Susannah Finzi, Software Inspection, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1993
• 9: Ivar Jacobson, Object-oriented software engineering, ACM Press, New York, NY, 1991
• 10: John C. Knight , E. Ann Myers, An improved inspection technique, Communications of the ACM, v.36 n.11, p.51-61, Nov. 1993 [doi>10.1145/163359.163366]
• 11: Filippo Lanubile , Forrest Shull , Victor R. Basili, Experimenting with Error Abstraction in Requirements Documents, Proceedings of the 5th International Symposium on Software Metrics, p.114, March 20-21, 1998
• 12: Bertrand Meyer, Object-oriented software construction (2nd ed.), Prentice-Hall, Inc., Upper Saddle River, NJ, 1997
• 13: Shari Lawrence Pfleeger, Software engineering: theory and practice, Prentice-Hall, Inc., Upper Saddle River, NJ, 1998
• 14: Adam A. Porter , Lawrence G. Votta, Jr. , Victor R. Basili, Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment, IEEE Transactions on Software Engineering, v.21 n.6, p.563-575, June 1995 [doi>10.1109/32.391380]
• 15: Forrest Joseph Shull , Victor R. Basili, Developing techniques for using software documents: a series of empirical studies, 1998
• 16: Marlon Erthal Righi Vieira , Guilherme Horta Travassos, An Approach to Perform Behavior Testing in Object-Oriented Systems, Proceedings of the Technology of Object-Oriented Languages and Systems, p.318, September 22-25, 1998
• 17: Lawrence G. Votta, Jr., Does every inspection need a meeting?, ACM SIGSOFT Software Engineering Notes, v.18 n.5, p.107-114, Dec. 1993
• 18: Zhang, Z., Basili, V., and Shr~eiderman, B., An empirical study of perspective-based usability inspection. Human Factors and Ergonomics Society Annual Meeting, Chicago, Oct. 1998.

INDEX TERMS

Primary Classification:
  D. Software
  D.1 PROGRAMMING TECHNIQUES

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Software quality assurance (SQA)

General Terms:
Design, Measurement, Performance, Reliability, Theory, Verification

Keywords:
object oriented software quality, object testing and metrics, software engineering practices, software inspection