Applying Software Quality Procedures
Mark A. Levin, Ted T. Kalal, Jonathan Rodin · 2019
For organizations just starting out with defect run charts, it is sufficient to just create a simple burn up chart that plots the total number of defects expected and progress toward finding them on defect run charts. All defects found during the software development must be counted. This should include defects found during reviews, inspections, and developer testing in addition to those found during the traditional software quality assurance type testing. Having accurate defect discovery and closure counts is critical to determining if the software is meeting its quality goals and is ready to release. Before any process improvement processes are undertaken, it must be determined where to start improving. Pareto charts are a particularly useful means of identifying targets for improvement. With continuous integration and test, the build and test environments are automated such that each time there is a code delivery, the software is automatically built and the tests are automatically run.