Study guide
Verifying and Validating Requirements
IIBA ECBA Entry Certificate in Business Analysis
Track your progress as you read
Finished sections get a check mark.
1 Introduction & ECBA Exam Overview
ECBA Exam Facts: Format, Eligibility, Cost, and Scoring How the ECBA Is Built: Source Documents, Blueprint Domains, and Study Plan
2 Understanding Business Analysis
What Is Business Analysis? The BACCM: Business Analysis Core Concept Model How Business Analysis Creates Value Defining Value and Assessing Value Realization
3 Mindset for Effective Business Analysis
The Business Analysis Mindset and How It Drives Effectiveness Shared Values and Core Business Analysis Principles Foundational Competencies Overview
4 Implementing Business Analysis
Business Analysis Roles and Organizational Context Choosing a BA Approach and the Requirements Classification Schema
5 Change
Contextual Factors Influencing the Work Impact Analysis Tracking Progress and Implementing Improvements
6 Need
Elicitation Methods and Stakeholder Rapport Documenting and Modeling Requirements Verifying and Validating Requirements Prioritizing Needs with MoSCoW
7 Solution
Solution Validation Criteria Evaluating Solution Options Scope Definition and Design Artifacts
8 Stakeholder
Communicating with Stakeholders Stakeholder Roles, Analysis, and RACI Facilitating Collaboration and Feedback
9 Value
Confirming Desired Outcomes and Value Opportunities Measuring Value Delivered
10 Context
Validating Information and Adapting Plans Technology Trends and Industry Standards
11 BABOK Techniques for ECBA
Elicitation and Collaboration Techniques Modeling and Analysis Techniques Strategy, Risk, and Investigation Techniques Requirements and Value Techniques
12 Underlying Competencies
Analytical Thinking, Behavioural Characteristics, and Business Knowledge Communication Skills, Interaction Skills, and Tools and Technology
13 Exam Readiness
Final Review & Exam-Day Strategy
Verifying and Validating Requirements
Key Takeaways Explain This Topic AI
BABOK v3 defines requirements verification as ensuring a requirement or design is well-formed, at the right level of abstraction, and meets quality standards.
BABOK v3 defines requirements validation as ensuring a requirement or design delivers business value and aligns to the business goals and objectives.
Verification asks whether the requirement was written correctly; validation asks whether the correct requirement was identified.
A requirement can pass verification (be well-written) yet fail validation (not deliver value) if it no longer supports a business objective.
Conflicts between stakeholder requirements should be documented and traced back to the underlying need so they can be resolved against business objectives.
Last updated: July 2026
Two Different Questions About the Same Requirement
The Need domain requires a business analyst to check requirements from two distinct angles, and the ECBA exam frequently tests whether a candidate can tell them apart. Verification asks: is this requirement well-written? Validation asks: is this the right requirement? BABOK v3 defines requirements verification as the process of checking that a requirement or design has been documented correctly - that it is at the right level of detail, uses proper structure and terminology, and satisfies the applicable quality standards, including the nine characteristics of good requirements covered in the previous section. BABOK v3 defines requirements validation as the process of confirming that a requirement or design delivers business value and aligns to the business goals, objectives, and needs that justified the change in the first place. A requirement can pass one check and fail the other, and understanding which failure mode applies is a core Need-domain skill.
Verification: Is It Correct?
Verification is a quality-control activity performed against the requirement itself, independent of whether the requirement is still needed. Typical verification checks include:
Does the requirement follow the organization's approved template and terminology?
Is it atomic, unambiguous, and testable, as covered in the previous section?
Is it free of internal contradictions and consistent with related requirements?
Is it traceable to its source, so its origin can be confirmed later?
Verification is usually performed by peers, quality reviewers, or the BA themselves through a structured review, and can happen before a stakeholder ever sees the final version.
Traceability Supports Both Checks
Both verification and validation lean on traceability - the documented link between a requirement and its source, and between a requirement and the higher-level need it satisfies. Without traceability, verification cannot confirm a requirement's origin, and validation cannot confirm which business objective a requirement is meant to support. When a requirement is traced back to a specific elicitation session, a specific stakeholder, and a specific business objective, both checks become mechanical: a reviewer can trace forward to confirm the requirement still connects to something the organization currently funds, and can trace backward to confirm nothing was lost or altered from the original elicitation. Weak or missing traceability is why validation failures often surface late, well after a requirement has already been implemented, because no one could quickly confirm which objective it was supposed to serve.
Validation: Is It the Right Thing?
Validation looks outward, from the requirement to the business case that justified it. A requirement can be perfectly written and still fail validation if:
The business objective it supported was cancelled or changed.
It duplicates value already delivered by another initiative.
It reflects an individual stakeholder's preference rather than a genuine organizational need.
The cost of delivering it exceeds the value it would return.
Validation typically involves confirming with the accountable business sponsor or stakeholder that the requirement still supports a current, funded objective, not simply confirming that the words on the page are clear.
Verification vs. Validation at a Glance
Question Verification Validation
Core question Is the requirement well-formed? Does the requirement deliver value?
- Focus The requirement document or model itself The requirement's alignment to business goals
- Typical checkers BA, peer reviewer, quality process Business sponsor, accountable stakeholder
Failure looks like Ambiguous, incomplete, inconsistent wording Correctly written requirement with no supporting business need
- When performed Throughout drafting, before finalizing Before requirements are approved for implementation
- Checking Alignment and Flagging Conflicts
Because multiple stakeholders elicit requirements independently, conflicts surface regularly - one department may need a field mandatory while another needs it optional. Part of the Need domain's validation responsibility is actively looking for these conflicts rather than assuming consistency. When a BA finds two requirements that cannot both be true, the correct response is not to silently pick one; it is to document the conflict, trace both requirements back to their underlying business need, and escalate the conflict to the accountable stakeholders for resolution against the organization's actual priorities. This keeps the decision with the people who own the business objective, rather than embedding an undocumented judgment call inside the requirements documentation where it will surface later as a dispute.
Why the Distinction Matters on Exam Day
A situation-based question that describes a requirement passing every quality check yet still not supporting any current business objective is testing a validation failure, not a verification failure - a common wrong-answer trap is to say the requirement needs to be rewritten more clearly when the actual problem is that it doesn't need to exist at all. Conversely, a question describing a requirement that is clearly connected to an active, valuable initiative but is stated ambiguously is testing a verification failure. Keeping the two questions - is it well-written versus is it the right thing - separate is the fastest way to eliminate distractors on Need-domain exam items. When in doubt about which failure a scenario describes, check whether the complaint is about the requirement's wording or about its connection to a funded business objective.