N-Fold inspection: a requirements analysis technique
Communications of the ACM
A Two-Person Inspection Method to Improve Programming Productivity
IEEE Transactions on Software Engineering
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
Software inspection process
An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development
IEEE Transactions on Software Engineering
Using simulation to build inspection efficiency benchmarks for development projects
Proceedings of the 20th international conference on Software engineering
Design and code inspections to reduce errors in program development
IBM Systems Journal
Active design reviews: principles and practices
ICSE '85 Proceedings of the 8th international conference on Software engineering
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
Software Inspection: An Industry Best Practice for Defect Detection and Removal
Software Inspection: An Industry Best Practice for Defect Detection and Removal
Software Inspection
Does Every Inspection Really Need a Meeting?
Empirical Software Engineering
Empirical Software Engineering
Empirical Software Engineering
Computer
Lessons from Three Years of Inspection Data
IEEE Software
SEL's Software Process Improvement Program
IEEE Software
Benchmarking Software-Development Productivity
IEEE Software
Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment
IEEE Transactions on Software Engineering
Applying Benchmarking to Learn from Best Practices
PROFES '00 Proceedings of the Second International Conference on Product Focused Software Process Improvement
Can Results from Software Engineering Experiments be Safely Combined?
METRICS '99 Proceedings of the 6th International Symposium on Software Metrics
Research Synthesis in Software Engineering: A Case for Meta-Analysis
METRICS '99 Proceedings of the 6th International Symposium on Software Metrics
Influence Of Team Size And Defect Detection Technique On Inspection Effectiveness
METRICS '01 Proceedings of the 7th International Symposium on Software Metrics
Accumulation and presentation of empirical evidence: problems and challenges
REBSE '05 Proceedings of the 2005 workshop on Realising evidence-based software engineering
Evaluating guidelines for empirical software engineering studies
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Replicating software engineering experiments: a poisoned chalice or the Holy Grail
Information and Software Technology
Hi-index | 0.00 |
Software inspections have been around for 25 years, and most software engineering researchers and professionals know that they are mostly a cost-effective means for removing software defects. However, this does not mean that there is consensus about how they should be conducted in terms of reading techniques, number of reviewers or the effectiveness of reviewers. Still, software inspections are probably the most extensively empirically studied technique in software engineering. Thus, a large body of knowledge is available in literature. This paper uses 30 data sets from software inspections found in the literature to study different aspects of software inspections. As a feasibility study, the data are amalgamated to increase our understanding and illustrate what could be achieved if we manage to conduct studies where a combination of data can be collected. It is shown how the combinated data may help to evaluate the influence of several different aspects, including reading techniques, team sizes and professionals vs. students. The objective is primarily to illustrate how more general knowledge may be gained by combining data from several studies. It is concluded that combining data is possible, although there are potential validity threats. Research results are examined with reference to software inspections on three levels: organization, project and individual.