Constraints and assumptions
On This Lesson 4 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
record what is fixed and what is merely believed.
Planned topics
- Constraint: a limit we cannot choose (budget, PostgreSQL as the system of record, regulation).
- Assumption: something we believe but have not verified (peak is 3× average).
- Requirement: something the solution must satisfy, owned by a stakeholder.
- Every assumption gets an owner, a way to verify it, and a date.
Draft outline details
Demonstration
three-column register for the order subsystem with one row each, e.g. assumption "Black Friday peak is 6× daily peak", owner Finance, verify with last year's data.
Check your understanding
Which of the three can later turn out false and silently invalidate the design?
Show answer
Assumptions, if not recorded and verified.
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.