All I really need to know about pair programming I learned in kindergarten
Communications of the ACM
The costs and benefits of pair programming
Extreme programming examined
Agile software development
Software Inspection
Strengthening the Case for Pair Programming
IEEE Software
The cost of errors in software development: evidence from industry
Journal of Systems and Software
Investigating the Defect Detection Effectiveness and Cost Benefit of Nominal Inspection Teams
IEEE Transactions on Software Engineering
Influence Of Team Size And Defect Detection Technique On Inspection Effectiveness
METRICS '01 Proceedings of the 7th International Symposium on Software Metrics
An Experimental Comparison of Usage-Based and Checklist-Based Reading
IEEE Transactions on Software Engineering
Building Pair Programming Knowledge through a Family of Experiments
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
Analyzing the Cost and Benefit of Pair Programming
METRICS '03 Proceedings of the 9th International Symposium on Software Metrics
A Replicated Experiment of Usage-Based and Checklist-Based Reading
METRICS '04 Proceedings of the Software Metrics, 10th International Symposium
Improvement of Design Specifications with Inspection and Testing
EUROMICRO '05 Proceedings of the 31st EUROMICRO Conference on Software Engineering and Advanced Applications
Value-Based Software Engineering
Value-Based Software Engineering
Design and code inspections to reduce errors in program development
IBM Systems Journal
Investigating the impact of active guidance on design inspection
PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
Hi-index | 0.00 |
The quality of the software design often has a major impact on the quality of the final product and the effort for development and evolution. A number of quality assurance (QA) approaches for inspection of early-life-cycle documents have been empirically evaluated. An implicit assumption of these studies was: an investment into early defect detection and removal saves higher rework cost. The concept of pair programming combines software construction with implicit QA in the development team. For planning QA activities, an important research question is how effective inspectors can be expected to be at detecting defects in software (design and code) documents compared to programmers who find defects as by-product of their usual construction activities. In this paper we present an initial empirical study that compares the defect detection effectiveness of a best-practice inspection technique with defect detection as by-product of constructive software evolution tasks during pair programming. Surprisingly, in the study context pair programmers were more effective to find defects in design documents than inspectors. However, when building a larger team for defect detection, a mix of inspection and pair programming can be expected to work better than any single technique.