Quality describes the degree to which a system, product, service, or work product fulfils defined requirements and stakeholder needs.
It depends on the intended purpose and operating context. Therefore, teams must define relevant expectations instead of relying on general ideas of excellence.
Quality requirements may address performance, security, reliability, availability, usability, or maintainability. Moreover, teams should express these expectations through measurable criteria.
Acceptance criteria define the conditions for accepting a specific requirement or backlog item. In contrast, broader requirements describe desired system characteristics. However, both need clear verification methods.
Teams can also evaluate requirements models. Syntactic evaluation checks compliance with modelling rules. Semantic evaluation checks correctness and completeness. Meanwhile, pragmatic evaluation checks whether stakeholders can understand and use the model.
Clear targets, acceptance tests, and review criteria provide objective evidence. As a result, teams can identify weaknesses and improve the solution before release.
Measurable expectations support reliable validation, informed decisions, and stakeholder acceptance.
« Back to Glossary Index