The architecture pack
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
assemble documentation as a pack structured by audience, not one big document.
Planned topics
- Four main readers: executives (decision and value), reviewers (compliance and risk), delivery (build detail), operations (run detail).
- A pack has an index, a one-page summary, and sections per audience that link to each other.
- Each document has a purpose, owner, status, version, and date.
- Reuse sources instead of copying them: link to the ADR rather than retyping it.
- Smaller and current beats complete and stale.
Draft outline details
Demonstration
a pack contents page for Larkspur: executive summary, options and decision, HLD, LLD for order fulfilment, interface contracts, deployment diagram, ADR log, risk register, operations handover; each with reader and owner.
Check your understanding
Why not write one document for everyone?
Show answer
Different readers need different depth; one document serves none of them well.
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.