In short
- Definition: The overall degree to which a system is free of defects and meets its requirements, measured through faults found, faults delivered and fault-removal efficacy.
- Goal: Deliver a system that works as expected, with few defects reaching users.
- Example S.M.A.R.T. requirement: Fewer than 0.5 defects per thousand lines of code in production, and more than 90% of defects found before release.
1. Definition
As a non-functional requirement, quality describes the overall degree to which a system is free of defects and meets its requirements [1], [2].
Quality is not tested in at the end. It is built in, and measured all along.Key takeaway
It is commonly measured through faults: how many are found before release, how many reach production (defect density), and what share of defects are caught before users see them (defect removal efficiency).
Quality in a broad sense covers all characteristics of ISO/IEC 25010, such as reliability, security or usability [3]. This page focuses on the defect-based view, which applies to every system.
2. Goal
The goal is a system that works as expected, with few defects reaching users.
Low quality shows up as incidents, rework, support costs and loss of trust, and each defect found in production costs much more to fix than one found early.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Production defect density | Defects per thousand lines of code or per feature | < 0.5 per KLOC | Defect tracker and code metrics |
| Defect removal efficiency | % of defects found before release | > 90% | Defects found before versus after release |
| Critical defects at release | Count | 0 open | Release checklist |
| Escaped defects per release | Count | Decreasing trend | Production defect reports |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Release gate: “No release shall go to production with an open critical or high-severity defect.”
- Efficiency: “More than 90% of defects shall be found before release, measured over each quarter.”
- Density: “Production defect density shall stay below 0.5 defects per thousand lines of changed code.”
5. Questions to Ask Stakeholders
- How is a defect defined and classified by severity?
- Which defects block a release?
- What quality level does the business expect in the first months?
- How will defects be tracked before and after release?
- Which testing levels are required (unit, integration, end-to-end, acceptance)?
- Who signs off on quality?
6. Common Pitfalls
- Counting only tests run. Many tests do not mean good quality. Measure defects and their escape rate.
- Inconsistent severity. Without shared definitions, metrics cannot be compared.
- Quality as the testers’ job only. Developers, analysts and product owners all shape quality.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Testability — makes it easier to find defects early.
- Reliability — fewer defects mean fewer failures.
- Maintainability — clean code reduces new defects.
- Certification — many certifications require a quality process.
8. FAQ
The share of defects found before release, compared with all defects found before and after release.
The number of defects relative to the size of the software, such as per thousand lines of code.
Yes, when expressed as measurable targets such as defect density or escape rate.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [4] |
| KLOC | Thousand (kilo) lines of code | Unit used to express the size of a code base, for example “0.5 defects per KLOC”. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [8] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [2] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Incident | Unplanned interruption or degradation of a service. | [9] |
| Production environment | The live system that real users use, as opposed to test environments. | [10] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [11] |
10. Sources and Further Reading
- [1] “Software quality.” Wikipedia. https://en.wikipedia.org/wiki/Software_quality (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [4] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [5] “Source lines of code.” Wikipedia. https://en.wikipedia.org/wiki/Source_lines_of_code (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [9] “Incident management.” Wikipedia. https://en.wikipedia.org/wiki/Incident_management (accessed Nov. 19, 2026).
- [10] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [11] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @truckrun_ebike_systems; inline photo by @sasun1990, both on Unsplash.








