All code coverage is not created equal: a case study in prioritized code coverage
CASCON '06 Proceedings of the 2006 conference of the Center for Advanced Studies on Collaborative research
A case study in database reliability: component types, usage profiles, and testing
Proceedings of the 1st international workshop on Testing database systems
| Hi-index | 0.00 |
This tutorial quickly, efficiently teaches you step by step the essentials of how to apply the standard, proven, widespread best practice of Software Reliability Engineering (SRE) to your project. SRE helps you develop and test more reliable software faster and cheaper. SRE is based on two powerful ideas: · Quantitatively characterize expected use and then focus resources on most used and/or most critical functions. This increases development efficiency and hence effective resource pool available to add customer value to product.· Further increase customer value by setting quantitative reliability objectives that precisely balance customer needs for reliability, timely delivery, and cost; engineer project strategies to meet them; and track reliability in test as a release criterion. You can apply SRE to the next release of any system / component that uses software