ACM Home Page
Please provide us with feedback. Feedback
PBR vs. checklist: a replication in the n-fold inspection context
Full text PdfPdf (615 KB)
Source International Symposium on Empirical Software Engineering archive
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering table of contents
Rio de Janeiro, Brazil
SESSION: Comparing defect detection techniques table of contents
Pages: 95 - 104  
Year of Publication: 2006
ISBN:1-59593-218-6
Authors
Lulu He  Mississippi State University, MS
Jeffrey Carver  Mississippi State University, MS
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 12,   Downloads (12 Months): 115,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1159733.1159750
What is a DOI?

ABSTRACT

Inspection is considered a powerful method to check software documents for defects. Many published work shows that inspections in requirements specification phase are particularly effective and efficient. Perspective-Based Reading (PBR) is one of the systematic techniques to support defect detection in requirements documents. In this paper we describe an experiment to validate the effectiveness of PBR in a meeting-based N-fold inspection. Our goals were: (1) re-test the hypothesis of the original experiment that PBR helps to increase individual and team defect detection effectiveness compared to an checklist approach; (2) investigate the different impact of PBR and checklist on the effectiveness of N-fold team meeting; and (3) investigate some interesting characteristics of PBR (e.g. the relationship between background experiences and performance of the subjects). The results of the study showed that PBR was significantly more effective than checklist (supporting the original study). We also found that the team meeting is much more important for checklist teams, based on the number of meeting gains and the number of false defects eliminated. Finally, we found that teams using the PBR techniques have less overlap in their defect detection than those using checklist. The ultimate goal is to provide best practices (guidance) for applying PBR in software inspection and also some advice for PBR (or software inspections) process improvement.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Ballman, K., and Votta, L.G. Organizational congestion in large-scale software development. In Proceeding of the Third International Conference on the Software Process. IEEE CS Press, Los Alamitos, CA, 1994, 123--134.
 
2
Basili, V. R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sørumgård, S., and Zelkowitz, M. V. The Empirical Investigation of Perspective-Based Reading. Empirical Software Engineering: An International Journal, 1, 2 (1996), 133--164.
 
3
 
4
Ciolkowski, M., Differding, C., Laitenberger, O., and Munch, J. Empirical Investigation of Perspective-Based Reading: A Replicated Experiment, Technical Report ISERN-97-13, Fraunhofer Institute for Experimental Software Engineering, Kaiserslautern, Germany, 1997.
 
5
Fagan, M. Design and code inspections to reduce errors in program development. IBM System Journal, 15, 3 (1976), 182--211.
 
6
 
7
 
8
9
 
10
11
 
12
Laitenberger, O., and DeBaud, J. An Encompassing Life-Cycle Centric Survey of Software Inspection. Technical Report ISERN-98-32, Fraunhofer Institute for Experimental Software Engineering, Kaiserslautern, Germany, 1998.
 
13
Lanubile, F. and Visaggio, G. Evaluating Defect Detection Techniques for Software Requirements Inspections, Technical Report ISERN-00-08, International Software Engineering Research Network.
14
 
15
16
 
17
 
18
 
19
 
20
 
21
22
 
23
24
 
25
 
26
27
 
28
Thompsom, C., & Riedl, J. (1995). Collaborative asynchronous inspection of software using Lotus Notes. Technical Report 95-047, Computer Science Department, University of Minnesota.
 
29
Tripp, L., Struck, W., and Pflung, B. The application of multiple team inspections on a safety-critical software standard. Proceeding of 4th Software Engineering Standards Application Workshop. IEEE CS Press, Los Alamitos, CA, 1991, 106--111
30
 
31
Wheeler, D. A., Brykczynski, B, and Meeson, R. N. Software Inspection: An Industry Best Practice. IEEE CS Press, Los Alamitos, CA, 1996.
 
32