Demo: turning "orders must never be lost" into testable requirements
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
work the vague sentence into scenarios, constraints, and a conflict list; prepares SRC-001-LAB1.
Draft outline details
Step by step
- Start from the sentence and ask the interview questions: lost where, by whom, for how long?
- Split it: "accepted orders are durable" (RPO) versus "orders are visible within 2 s" (latency) versus "no duplicate charge".
- Write three scenarios with measures; define "lost" as accepted-but-not-recoverable.
- Record assumptions (single-region failure is the worst case) and constraints (PostgreSQL stays).
- Planned mistake: accept "zero loss" as written. Fix: show that it implies synchronous multi-site writes and price it; negotiate "no loss of acknowledged orders after a single-AZ failure".
- List the conflict (zero loss vs latency budget) with owners.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.