Experimentation in software engineering
IEEE Transactions on Software Engineering
N-Fold inspection: a requirements analysis technique
Communications of the ACM
An experimental study of fault detection in user requirements documents
ACM Transactions on Software Engineering and Methodology (TOSEM)
An improved inspection technique
Communications of the ACM
Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Assessing Software Review Meetings: Results of a Comparative Analysis of Two Experimental Studies
IEEE Transactions on Software Engineering
ICSE '97 Proceedings of the 19th international conference on Software engineering
A case study of distributed, asynchronous software inspection
ICSE '97 Proceedings of the 19th international conference on Software engineering
Assessing software review meetings: a controlled experimental study using CSRS
ICSE '97 Proceedings of the 19th international conference on Software engineering
An empirical methodology for introducing software processes
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
A Discipline for Software Engineering
A Discipline for Software Engineering
Software Inspection: An Industry Best Practice for Defect Detection and Removal
Software Inspection: An Industry Best Practice for Defect Detection and Removal
Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products
Software Inspection
Empirical Software Engineering
Perspective-based Usability Inspection: An Empirical Validationof Efficacy
Empirical Software Engineering
Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment
IEEE Transactions on Software Engineering
An Empirical Evaluation of Three Defect-Detection Techniques
Proceedings of the 5th European Software Engineering Conference
An experiment to assess cost-benefits of inspection meetings and their alternatives: a pilot study
METRICS '96 Proceedings of the 3rd International Symposium on Software Metrics: From Measurement to Empirical Results
Developing techniques for using software documents: a series of empirical studies
Developing techniques for using software documents: a series of empirical studies
Shared defect detection: the effects of annotations in asynchronous software inspection
Shared defect detection: the effects of annotations in asynchronous software inspection
Knowledge-Sharing Issues in Experimental Software Engineering
Empirical Software Engineering
Cognitive factors in perspective-based reading (PBR): A protocol analysis study
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
An empirically-based process to improve the practice of requirement review
ICSP'08 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story
Hi-index | 0.00 |
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.