Which technique is used by business analysts (BAs) to measure the quality of requirements?

Acceptance and Evaluation Criteria are used to define the conditions that must be met for a solution or requirement to be considered acceptable. This technique is fundamental to measuring requirement quality because it ensures that requirements are testable and unambiguous. By setting clear, agreed-upon criteria, business analysts can verify and validate that the requirements are complete, correct, and meet stakeholder needs. These criteria form the basis for tests that confirm the solution delivers the intended value, directly reflecting the quality of the underlying requirements.

B. Key Performance Indicators: KPIs measure the performance or success of an implemented solution against business objectives, not the intrinsic quality of the requirements themselves during the analysis phase.
C. Risk Analysis and Management: This technique identifies and mitigates potential problems that could negatively impact a project, rather than directly measuring the quality attributes of individual requirements.
D. Entity Relationship Modelling: This is a data modeling technique used to define and analyze data requirements and their relationships, not a method for assessing the overall quality of all types of requirements.

1. International Institute of Business Analysis. (2015). A Guide to the Business Analysis Body of Knowledge (BABOK Guide) (Version 3). IIBA.

Section 10.1.1

Acceptance and Evaluation Criteria - Purpose: "Acceptance and evaluation criteria are used to define the requirements

outcomes

or conditions that must be met in order for a solution to be considered acceptable by key stakeholders."

Section 10.1.2

Acceptance and Evaluation Criteria - Description: States that criteria must be "testable" and are used for "defining acceptance." This directly relates to verifying requirement quality.

Section 10.27

Metrics and Key Performance Indicators: Describes KPIs as measures of organizational performance and solution effectiveness

distinct from requirement quality.

Section 10.39

Risk Analysis and Management: Defines this technique's purpose as identifying and managing uncertainties

not evaluating requirement attributes.

Section 10.18

Data Modelling: Explains this technique is for describing entities and relationships within a domain

a specific type of requirement definition

not a general quality measure.