Learn to tell functional requirements — what a system does — apart from non-functional requirements — how well it does it — and why the second kind is the one teams forget. You will work through the categories that get omitted, build a reusable checklist, and diagnose a real system that passed every test and still fell over.
Watch the free preview
Why systems that "work" still fail — free to watch, no account needed.
What you'll learn
- Distinguish functional requirements from non-functional requirements with confidence
- Name the non-functional categories most often omitted, including performance, security, usability and scalability
- Write non-functional requirements that are measurable and testable rather than vague aspirations
- Diagnose a system that passes functional tests yet fails a quality attribute under real conditions
- Produce a reusable Non-Functional Requirements Checklist to run against any feature
Syllabus
The Requirement You Forgot to Ask For
Why systems that "work" still failFree preview
Defining functional and non-functional requirements
The Categories Teams Forget
The non-functional categories that get omitted
Making non-functional requirements measurable
Capturing Both Kinds in Real Work
Eliciting non-functional requirements in practice
Case study — the system that collapsed under load
Making It Stick
Building your Non-Functional Requirements Checklist
Common traps and anti-patterns to avoid