On this page
architecture
Architecture & Design
Architecture documents, decision records, API specs and data models.
Last updated
Design documents are written for the engineer who joins in eighteen months, not for the approval meeting next Tuesday. These templates favour recording the why — constraints, options rejected, trade-offs accepted — over redrawing boxes that the code already shows.
Related categories
- Requirements & Analysis — the requirements a design exists to satisfy, and traces back to.
- Development & Release — the standards, reviews and runbooks that carry a design into production.
- Security & Compliance — the controls a design has to carry, and the evidence it has to produce.
Linked from
- API Specification — The contract between two teams: resources, errors, versioning and what happens when it breaks.
- Architecture Decision Record — One decision, its context, the options rejected, and what it costs — in under a page.
- Data Model Document — Entities, relationships, classification and retention — the parts of the schema that outlive the code.
- Development & Release — Coding standards, review checklists, PR templates, release notes and deployment runbooks.
- Overview — Copy-paste document templates for IT work, each with a worked example and the mistakes that usually spoil it.
- Requirements & Analysis — BRDs, SRSs, user stories, use cases and traceability matrices.
- Security & Compliance — Security policies, risk registers, access reviews, vendor assessments and DPIAs.
- Solution Architecture Document — The structure of a system, the constraints that shaped it, and the trade-offs accepted.
- Technical Design Document — How one component will actually be built — enough detail to review the idea before the code exists.