Towards economical software release recommendations

An economic view on software quality is essential for company success. An economic view is also needed for the assessment whether software is ready for release. To give an economical software release recommendation, we must trade off the consequential costs against the removal costs. Simply causing release recommendations on failure-based metrics is not sufficient. We must also regard the test quality if the software release depends on failure statistics. In this work, we survey existing release recommendation approaches. We conclude that existing approaches do not sufficiently regard costs or test quality. Thus, none of the approaches can give an economical release recommendation. We present a release recommendation framework. It focuses on trading off the failure consequential costs against the failure removal costs for each failure at the end of the test process. The test quality is explicitly regarded as a fundamental aspect to ensure a valid release recommendation. We show the applicability of our framework in a hypothetical case study comparing traditional approaches with our framework.

[1]  Bertrand Meyer,et al.  Seven Principles of Software Testing , 2008, Computer.

[2]  Reiner R. Dumke,et al.  Evaluation Approaches in Software Testing , 2008 .

[3]  Mayuram S. Krishnan,et al.  Evaluating the cost of software quality , 1998, CACM.

[4]  Harry M. Sneed Testing a Datawarehouse - An Industrial Challenge , 2006, Testing: Academic & Industrial Conference - Practice And Research Techniques (TAIC PART'06).

[5]  Hong Zhu,et al.  Developing Software Testing Ontology in UML for a Software Growth Environment of Web-Based Applications , 2005 .

[6]  Barry W. Boehm,et al.  How Much Software Quality Investment Is Enough: A Value-Based Approach , 2006, IEEE Software.

[7]  Rex Black,et al.  Critical testing processes : plan, prepare, perform, perfect / Rex Black , 2004 .

[8]  Andreas Spillner,et al.  Management und Optimierung des Testprozesses - ein praktischer Leitfaden für erfolgreiches Software-Testen mit TPI und TMap (2. Aufl.) , 2002 .

[9]  Tom DeMarco Software Engineering: An Idea Whose Time Has Come and Gone? , 2009, IEEE Software.

[10]  Mario Winter,et al.  Qualitätssicherung für objektorientierte Software: Anforderungsermittlung und Test gegen die Anforderungsspezifikation , 2000, Softwaretechnik-Trends.

[11]  Edward G. Schilling,et al.  Juran's Quality Handbook , 1998 .

[12]  Wolfgang Dröschel,et al.  Inkrementelle und objektorientierte Vorgehensweisen mit dem V-Modell 97 , 1998 .

[13]  Antony Black Critical Testing Process: Plan, Prepare, Perform, Perfect , 2003 .

[14]  Harry M. Sneed,et al.  Produkt- und Prozessmetriken für den Softwaretest , 2006, Informatik-Spektrum.

[15]  Stefan Wagner,et al.  A literature survey of the quality economics of defect-detection techniques , 2006, ISESE '06.

[16]  Jochen Ludewig,et al.  Software-Projektmanagement und -Qualitätssicherung , 1988 .

[17]  Charles Radley,et al.  Safeware: System safety and computers. A guide to preventing accidents and losses caused by technology , 1996 .

[18]  Steve McConnell,et al.  Best Practices: Gauging Software Readiness with Defect Tracking , 1997, IEEE Softw..

[19]  Ming Li,et al.  Validation of a methodology for assessing software reliability , 2004, 15th International Symposium on Software Reliability Engineering.

[20]  Steve McConnell Software Estimation: Demystifying the Black Art , 2006 .

[21]  Glenford J. Myers,et al.  Art of Software Testing , 1979 .

[22]  Andreas Spillner,et al.  Praxiswissen Softwaretest, Testmanagement - Aus- und Weiterbildung zum Certified Tester: Advanced Level nach ISTQB-Standard , 2006 .