CPD
Software architecture artefact templates and rubrics
These templates are designed to be quick, defensible, and easy to explain. Use the rubric to check quality. Keep the output as CPD evidence.
How to use this
Practical, not perfection- Pick the tier you are studying and copy the template into your notes.
- Complete it for one real example (work, a side project, or a safe fictional scenario).
- Use the rubric to tighten it until it is defensible.
- Paste a short reflection into your CPD record: what you assumed, what evidence you would keep, and what you would do next.
Foundations. Architecture canvas
Template + rubric + exampleTemplate
Rubric (what “good enough” looks like)
- Scope and boundaries are clear (what is in/out).
- Boundaries and ownership are explicit.
- Evidence is identified (what you would log/measure/keep).
Worked example (short)
Example (short): Quality priority: availability 99.9%, latency p95 < 300ms.
Applied. ADR pack
Template + rubric + exampleTemplate
Rubric (what “good enough” looks like)
- Trade-offs are stated, not implied.
- Assumptions are explicit and testable.
- Next actions are concrete and realistic.
Worked example (short)
Example (short): Decision: adopt event-driven integration for X. Review trigger: tracing cost exceeds budget.
Advanced. Governance and evolution plan
Template + rubric + exampleTemplate
Rubric (what “good enough” looks like)
- Governance enables delivery and avoids theatre.
- Evidence is identified (what you would log/measure/keep).
- Next actions are concrete and realistic.
Worked example (short)
Example (short): Signals: rising change failure rate, repeated exceptions, unclear ownership.