Loading content
Quality Assurance (QA) is a comprehensive approach for systematically ensuring product and process quality. It combines organizational responsibility, defined testing and improvement processes, and metrics for transparency. QA aims to reduce defect sources and embed continuous improvement across development and operations.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Quality assurance (QA) designs and evaluates ways of working so that defects are prevented or found early and outcomes reliably meet their requirements.
The term grew out of quality practice in industrial production and was adapted to software development and IT operations. QA denotes planned, systematic assurance of product and process quality.
QA starts before the finished product: teams make requirements testable, assess risks, add quality gates to workflows, and review results through tests, inspections, or audits. Findings feed product and process improvement. QA is broader than executing tests; testing is one instrument within its quality framework.
Requirements, standards, and reviews reduce defect sources before they enter a product.
Tests, inspections, and audits provide traceable evidence that quality requirements are met.
Detected deviations lead to corrective action and improvement of the underlying process.
QA helps teams treat quality as a planned responsibility across the lifecycle and expose risk early. It becomes meaningful when requirements, verification methods, and ownership are explicit.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.