Confirming you understood.
WHAT VALIDATION ESTABLISHES
That the requirements describe what is actually needed.
WHAT VERIFICATION ESTABLISHES
That the system meets the requirements.
WHY THAT DISTINCTION MATTERS
A system can meet its requirements perfectly and still be wrong.
WHAT TO DO
Review requirements with the people who stated them Walk through scenarios end to end Build something small and show it
WHAT SHOWING SOMETHING REVEALS
Misunderstandings that reviewing documents does not.
WHY
People recognise what is wrong far more reliably than they specify what is right.
WHAT TO USE
Prototypes, mockups, or a working slice.
WHAT TO ASK
Is this what you meant? What is missing? What would you do differently?
WHAT TO LOOK FOR
Hesitation, which usually indicates something unstated.
WHAT TO CHECK FOR
Requirements that conflict Requirements with no source Requirements nobody can test Gaps between requirements
WHAT TO RECORD
Agreement, and any changes arising.
