Advances in software inspections
IEEE Transactions on Software Engineering
Designing documentation to compensate for delocalized plans
Communications of the ACM
A Statistical Approach to the Inspection Checklist Formal Synthesis and Improvement
IEEE Transactions on Software Engineering
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Object-oriented inspection in the face of delocalisation
Proceedings of the 22nd international conference on Software engineering
Systematic object-oriented inspection — an empirical study
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
A Discipline for Software Engineering
A Discipline for Software Engineering
Practical Object-Oriented Design
Practical Object-Oriented Design
Using Uml: Software Engineering with Objects and Components
Using Uml: Software Engineering with Objects and Components
Software Inspection
Lessons from Three Years of Inspection Data
IEEE Software
Evaluation of Usage-Based Reading—Conclusions after Three Experiments
Empirical Software Engineering
An experimental evaluation of continuous testing during development
ISSTA '04 Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis
Software testing research and practice
ASM'03 Proceedings of the abstract state machines 10th international conference on Advances in theory and practice
Hi-index | 0.00 |
This paper describes the development and experimental evaluation of a rigorous approach for effective object-oriented (OO) code inspection. Since their development, inspections have been shown to be powerful defect detection strategies but little research has been done to investigate their application to OO systems, which have very different structural and execution models compared to procedural systems. Previous investigations have demonstrated that the delocalised nature of OO software - the resolution of frequent non-local references, and the incongruous relationship between its static and dynamic representations, are primary inhibitors to its effective inspection. The experiment investigates a set of three complementary code reading techniques devised specifically to address these problems: one based on a checklist adapted to address the identified problems of OO inspections, one focused on the systematic construction of abstract specifications, and the last centered on the dynamic slice that a use-case takes through a system. The analysis shows that there is a significant difference in the number of defects found between the three reading techniques. The checklist-based technique emerges as the most effective approach but the other techniques also have noticeable strengths and so for the best results in a practical situation a combination of techniques is recommended.