Deliverables and their readers
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
match each architecture deliverable to the person who must act on it.
Planned topics
- HLD: read by sponsors, reviewers, and security; they need to approve direction and risk.
- LLD: read by delivery teams; they need to build and estimate without guessing.
- ADRs: read by future maintainers; they need to know why, not only what.
- Interface contracts and deployment diagrams: read by partner teams and operations.
- A deliverable with no named reader and no decision it supports should not be written.
Draft outline details
Demonstration
a table with columns deliverable, reader, decision it enables, and length target, filled for the Larkspur pack.
Check your understanding
Who is the primary reader of an LLD?
Show answer
The delivery team that builds and estimates from it.
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.