Managing the software process
Computation for the analysis of designed experiments
Computation for the analysis of designed experiments
An experimental study of fault detection in user requirements documents
ACM Transactions on Software Engineering and Methodology (TOSEM)
Estimating software fault content before coding
ICSE '92 Proceedings of the 14th international conference on Software engineering
Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Experience with Formal Methods in Critical Systems
IEEE Software
Lessons from using basic LOTOS
ICSE '94 Proceedings of the 16th international conference on Software engineering
Active design reviews: principles and practices
ICSE '85 Proceedings of the 8th international conference on Software engineering
Software Engineering Economics
Software Engineering Economics
Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment
IEEE Transactions on Software Engineering
Evaluation of a software requirements document by analysis of change data
ICSE '81 Proceedings of the 5th international conference on Software engineering
Building Knowledge through Families of Experiments
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
Studies of the work practices of software engineers
Advances in software engineering
Using a Reliability Growth Model to Control Software Inspection
Empirical Software Engineering
Empirical Software Engineering
Empirical Software Engineering
Evaluating defect estimation models with major defects
Journal of Systems and Software
Tailoring a COTS Group Support System for Software Requirements Inspection
Proceedings of the 16th IEEE international conference on Automated software engineering
(Quasi-)experimental studies in industrial settings
Lecture notes on empirical software engineering
An Experimental Comparison of Usage-Based and Checklist-Based Reading
IEEE Transactions on Software Engineering
Quality assurance under the open source development model
Journal of Systems and Software
On the Effectiveness of the Test-First Approach to Programming
IEEE Transactions on Software Engineering
Improvement of Design Specifications with Inspection and Testing
EUROMICRO '05 Proceedings of the 31st EUROMICRO Conference on Software Engineering and Advanced Applications
Perspective-Based Reading: A Replicated Experiment Focused on Individual Reviewer Effectiveness
Empirical Software Engineering
Analyzing individual performance of source code review using reviewers' eye movement
Proceedings of the 2006 symposium on Eye tracking research & applications
PBR vs. checklist: a replication in the n-fold inspection context
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Using portfolio theory for better and more consistent quality
Proceedings of the 2007 international symposium on Software testing and analysis
Empirical investigation towards the effectiveness of Test First programming
Information and Software Technology
A defect prediction method for software versioning
Software Quality Control
Exploiting Eye Movements for Evaluating Reviewer's Performance in Software Review
IEICE Transactions on Fundamentals of Electronics, Communications and Computer Sciences
Experiences from using ICMM in inspection process assessment
Software Quality Control
Replicating software engineering experiments: a poisoned chalice or the Holy Grail
Information and Software Technology
Testing the theory of relative defect proneness for closed-source software
Empirical Software Engineering
A test-driven approach to code search and its application to the reuse of auxiliary functionality
Information and Software Technology
Impact of test-driven development on productivity, code and tests: A controlled experiment
Information and Software Technology
Issues in software inspection practices
PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
Investigating the impact of active guidance on design inspection
PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
Is external code quality correlated with programming experience or feelgood factor?
XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in Software Engineering
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
Replication of software engineering experiments
Empirical Software Engineering and Verification
Fully employing software inspections data
Innovations in Systems and Software Engineering
Proceedings of the 2013 International Conference on Software and System Process
Empirical Software Engineering
Hi-index | 0.00 |
Software requirementsspecifications (SRS) are often validated manually. One such processis inspection, in which several reviewers independently analyzeall or part of the specification and search for faults. Thesefaults are then collected at a meeting of the reviewers and author(s). Usually, reviewers use Ad Hoc or Checklistmethods to uncover faults. These methods force all reviewersto rely on nonsystematic techniques to search for a wide varietyof faults. We hypothesize that a Scenario-based method, in whicheach reviewer uses different, systematic techniques to searchfor different, specific classes of faults, will have a significantlyhigher success rate. In previous work we evaluatedthis hypothesis using 48 graduate students in computer scienceas subjects. We now have replicated this experimentusing 18 professional developers from Lucent Technologies assubjects. Our goals were to (1) extend the external credibilityof our results by studying professional developers, and to (2)compare the performances of professionals with that of the graduatestudents to better understand how generalizable the results ofthe less expensive student experiments were. For each inspection we performed four measurements: (1) individualfault detection rate, (2) team fault detection rate, (3) percentageof faults first identified at the collection meeting (meetinggain rate), and (4) percentage of faults first identified byan individual, but never reported at the collection meeting (meetingloss rate). For both the professionals and thestudents the experimental results are that (1) the Scenario methodhad a higher fault detection rate than either Ad Hoc or Checklistmethods, (2) Checklist reviewers were no more effective thanAd Hoc reviewers, (3) Collection meetings produced no net improvementin the fault, and detection rate—meeting gains were offsetby meeting losses, Finally, although specificmeasures differed between the professional and student populations,the outcomes of almost all statistical tests were identical.This suggests that the graduate students provided an adequatemodel of the professional population and that the much greaterexpense of conducting studies with professionals may not alwaysbe required.