Software Process Improvement and Practice · 2006 · 61 citations · 20 references
ComputingComputer ScienceProject ManagementCost ManagementPerformance MeasurementSoftware EngineeringProject Performance MeasurementSoftware Development Life Cycle ManagementSoftware MetricsSoftware Project ManagementSoftware Quality AssuranceSoftware TestingReworkRework RateSoftware Process MeasurementSoftware Testing Process
Abstract In market‐driven development where time‐to‐market is of crucial importance, software development companies seek improvements that can decrease the lead‐time and improve the delivery precision. One way to achieve this is by analyzing the test process since rework commonly accounts for more than half of the development time. A large reason for high rework costs is fault slippages from earlier phases where they are cheaper to find and remove. As an input to improvements, this article introduces a measure that can quantify this relationship. That is, a measure called faults‐slip‐through , which determines the faults that would have been more cost‐effective to find in an earlier phase. The method presented in this article also determines the excessive costs of the faults that slipped through phases, i.e. the improvement potential. The method was validated through practical application in two software development projects at the telecom company Ericsson AB. The results of the case study determined that the implementation phase had the largest improvement potential in the two studied projects since it caused a large faults‐slip‐through to later phases, i.e. 85 and 86% of the total improvement potential of each project. Copyright © 2006 John Wiley & Sons, Ltd.
20
Eric R. Ziegel, Robert S. Kaplan, D. P. Norton · Technometrics · 1998 · 2.2K citations
What we have learned about fighting defects
Forrest Shull, Victor R. Basili, Barry Boehm et al. · 2002 · 244 citations
A case study in root cause defect analysis
Marek Leszak, Dewayne E. Perry, Dieter Stoll · 2000 · 180 citations · Full text