Checkout
technical requirements
- TS-004Prices from the catalogue APImeets FS-010
- TS-005Totals on the server · ADR-007meets FS-010
- TS-006Card payment via the providermeets FS-012
Read more · slide 03 / 07 · specified · technical
The technical spec says how each requirement will be met. The decision record says why a significant choice was made. Together they are the memory a project usually loses.
technical requirements
the decision, and why
from slide 03each technical line points back to the requirement it serves
Where the data comes from, where the logic runs, what it talks to. Each line has its own id and points back to the functional line it serves, so nothing technical exists without a reason a user would recognise.
| Id | How | Meets |
|---|---|---|
| TS-004 | Prices from the catalogue API | FS-010 |
| TS-005 | Totals computed on the server · see ADR-007 | FS-010 |
| TS-006 | Card payment via the provider | FS-012 |
A short record for each decision that someone might later want to undo. It keeps the reason next to the choice, so a future change can see what it would break.
An agent starting a new session remembers nothing. The technical spec and the decision records are its memory. Without them it decides again, often differently, and the code drifts from session to session.
Written down, the context travels: to the next session, to a second agent, to the person who maintains it next year.
Carries forward: your answer on slide 02, now ADR-007. FS-010 and FS-012 sit beside it on slide 03. ADR-007 comes back on slide 06, where the decision still holds after the change.