Qualitative observations from software code inspection experiments
CASCON '02 Proceedings of the 2002 conference of the Centre for Advanced Studies on Collaborative research
Using multiple adaptive regression splines to support decision making in code inspections
Journal of Systems and Software - Special issue: Applications of statistics in software engineering
Task-directed software inspection
Journal of Systems and Software - Special issue: Applications of statistics in software engineering
Peer Reviews in Real Life - Motivators and Demotivators
QSIC '05 Proceedings of the Fifth International Conference on Quality Software
Requirements engineering: In search of the dependent variables
Information and Software Technology
Are good code reviewers also good at design review?
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Hi-index | 0.00 |
Software inspection is one of the key enablers for qualityimprovement and defect cost reduction. Although itsbenefits are shown in many studies, a major obstacle toimplement and use inspection technologies in softwareprojects is the costs associated with it. Companiestherefore constantly ask for the most cost-effectiveinspection implementation. Answering this questionrequires a discussion about the design of the inspectionprocess as well as the question of how the selected processactivities are to be performed. As a consequence, thetailored process and activities often result in an inspectionimplementation that perfectly fits into a project orenvironment but is different to the traditional onespresented in the existing inspection literature.In this paper, we present and examine a non-traditionalinspection implementation at DaimlerChrysler AG. Thedesign of this inspection approach evolved over time aspart of a continuous improvement effort and thereforeintegrates specific issues of the project environment as wellas recent research findings. In addition to the descriptionof the inspection approach, the paper presents quantitativeresults to characterize the suggested inspectionimplementation and investigates some of the essentialhypotheses in the inspection area. Both, the technicaldescription as well as its quantitative underpinning servesas an example for other companies that pursueimprovement or adaptation efforts in the softwareinspection area.