Using fault slippage measurement for monitoring software process quality during development

In a competitive environment where time-to-market is crucial for success, software development companies initiate process improvement programs that can shorten the development time. They especially seek improvements in the verification activities since rework commonly constitutes a significant part of the development cost. However, the success of process improvement initiatives is dependent on early and observable results since a lack of feedback on the effect of improvements is a common cause of failure. This paper investigates how to monitor the verification process as input to decisions such as improvement actions. The suggested approach was applied on three industrial software products at Ericsson and the results determined that the approach can be used for quantitative monitoring of process quality and as decision support to do rapid improvement actions.

[1]  Lars Lundberg,et al.  Results from introducing component-level test automation and Test-Driven Development , 2006, J. Syst. Softw..

[2]  Ram Chillarege,et al.  Test and development process retrospective - a case study using ODC triggers , 2002, Proceedings International Conference on Dependable Systems and Networks.

[3]  Alan R. Hevner,et al.  Phase containment metrics for software quality improvement , 1999, Inf. Softw. Technol..

[4]  Mayuram S. Krishnan,et al.  Measurement Programs in Software Development: Determinants of Success , 2002, IEEE Trans. Software Eng..

[5]  Jan Pries-Heje,et al.  Improving Software Organizations: From Principles to Practice , 2001 .

[6]  van E.P.W.M. Veenendaal,et al.  The Testing Practitioner , 2007 .

[7]  Richard E. Biehl.  Six Sigma for Software , 2004, IEEE Softw..

[8]  Peter Axel Nielsen,et al.  Competing values in software process improvement: an assumption analysis of CMM from an organizational culture perspective , 2003, IEEE Trans. Engineering Management.

[9]  Raymond A. DeCarlo,et al.  Monitoring the software test process using statistical process control: a logarithmic approach , 2003, ESEC/FSE-11.

[10]  V. Basili.  Software modeling and measurement: the Goal/Question/Metric paradigm , 1992 .

[11]  Mark C. Paulk,et al.  The Capability Maturity Model: Guidelines for Improving the Software Process , 1994 .

[12]  Khaled El Emam,et al.  Spice: The Theory and Practice of Software Process Improvement and Capability Determination , 1997 .

[13]  Gerard O’Regan,et al.  The Capability Maturity Model , 2002 .

[14]  E. Ziegel,et al.  The Balanced Scorecard , 1998 .

[15]  Claes Wohlin,et al.  Faults-slip-through - a concept for measuring the efficiency of the test process , 2006, Softw. Process. Improv. Pract..

[16]  W. L. Smith,et al.  On the limitations of software process assessment and the recognition of a required re-orientation for global process improvement , 1998, Software Quality Journal.

[17]  Robert B. Grady,et al.  Practical Software Metrics for Project Management and Process Improvement , 1992 .

[18]  E. Ziegel,et al.  Balanced Scorecard , 2019, Encyclopedia of Public Administration and Public Policy, Third Edition.

[19]  Per Runeson,et al.  Are found defects an indicator of software correctness? An investigation in a controlled case study , 2004, 15th International Symposium on Software Reliability Engineering.

[20]  Didar Zowghi,et al.  A Maturity Model for the Implementation of Software Process Improvement: an Empirical Study , 2022 .

[21]  Austen Rainer,et al.  Key success factors for implementing software process improvement: a maturity-based analysis , 2002, J. Syst. Softw..

[22]  Norman E. Fenton,et al.  A Critique of Software Defect Prediction Models , 1999, IEEE Trans. Software Eng..

[23]  Barry W. Boehm,et al.  What we have learned about fighting defects , 2002, Proceedings Eighth IEEE Symposium on Software Metrics.