Evaluating the cost of software quality
Communications of the ACM
Art of Software Testing
Gauging Software Readiness with Defect Tracking
IEEE Software
Critical Testing Process: Plan, Prepare, Perform, Perfect
Critical Testing Process: Plan, Prepare, Perform, Perfect
Validation of a Methodology for Assessing Software Reliability
ISSRE '04 Proceedings of the 15th International Symposium on Software Reliability Engineering
Testing a Datawarehouse - An Industrial Challenge
TAIC-PART '06 Proceedings of the Testing: Academic & Industrial Conference on Practice And Research Techniques
A literature survey of the quality economics of defect-detection techniques
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Software Testing Foundations: A Study Guide for the Certified Tester Exam
Software Testing Foundations: A Study Guide for the Certified Tester Exam
Software Estimation: Demystifying the Black Art
Software Estimation: Demystifying the Black Art
Seven Principles of Software Testing
Computer
Hi-index | 0.00 |
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.