Overview
Defect density, a metric that quantifies the number of defects per unit of code, has been a cornerstone of software quality assurance since the 1970s, when IBM first introduced it as a key performance indicator. With a vibe score of 8, defect density is widely reported to be a strong predictor of software reliability, with studies showing that a lower defect density is associated with higher customer satisfaction and reduced maintenance costs. However, skeptics argue that defect density can be gamed, with developers artificially reducing defect counts by reclassifying or ignoring defects. As the software industry continues to evolve, with the rise of agile development and DevOps, the relevance of defect density as a metric is being reevaluated, with some arguing that it is no longer a relevant indicator of software quality. Despite this, defect density remains a widely used metric, with companies like Microsoft and Google using it to measure the quality of their codebases. With the average defect density of commercial software ranging from 0.1 to 10 defects per thousand lines of code, the stakes are high for companies to get it right, with the cost of fixing a defect increasing by a factor of 10 for each stage of the development process, from design to deployment.
Key Facts
- Year
- 1970
- Origin
- IBM
- Category
- Software Engineering
- Type
- Software Metric