Phase 3 · Requirements Analysis & Documentation
TopicsWriting Clear, Testable Requirements
Part of the Business Analyst Roadmap.
Summary
A requirement should be specific, unambiguous, and verifiable — 'the system should be fast' is untestable; 'the system should load search results within 2 seconds' is testable.
How to Learn This
- 1Rewrite 5 vague requirements into specific, testable ones.
- 2Learn the SMART-adjacent checklist many BAs use: specific, measurable, achievable, relevant, testable.
- 3Practice this on a real ambiguous requirement you've encountered or can imagine.
More topics in Requirements Analysis & Documentation
Functional vs Non-Functional RequirementsBusiness Requirements Document (BRD)Functional Requirements Document (FRD)User Stories & Acceptance CriteriaUse Cases & Use Case DiagramsRequirements Traceability Matrix (RTM)Requirements Prioritization (MoSCoW)Requirements Validation & Sign-OffManaging Requirement Changes
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — free on the InsideEdge app.