Edge cases and non-functional requirements
Production incidents often come from a case no one wrote down or a performance requirement that stayed implicit. This lesson helps you find the situations at the edges of a feature methodically and express its non-functional requirements in a testable way, so neither the team nor a coding agent has to guess them.
Lesson objective
By the end of this lesson, you will be able to find a feature's edge cases methodically with a grid of questions, and write its non-functional requirements (performance, reliability, security, accessibility, personal data) in a quantified, testable form.
Topics covered
- edge cases
- non-functional requirements
- NFR
- accessibility requirements
- performance and reliability
In the glossary
Where it fits
Criteria, edge cases and requirements
How do you write criteria you can verify, and not forget what happens when things do not go as planned?
Lessons in this module
- Write verifiable Given / When / Then criteria
- Edge cases and non-functional requirements (this lesson)
What you will learn in this module
This lesson is part of the course Write specs that developers and AI agents understand
- Write verifiable, declarative and unambiguous Given/When/Then acceptance criteria, including as tables of examples.
- Identify edge cases and non-functional requirements (performance, security, accessibility, personal data) and make them testable.
Related courses
- Product ManagementJuniorSome basics are useful: introductory knowledge of the topic.
Design and validate a product experience with AI
2 hr 30 min
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Instrument a product and use data to make decisions
3 hr 30 min
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Prioritize and build an outcome-based roadmap
2 hr 30 min