A self-study course in solution architecture, built from public standards and literature: ISO/IEC/IEEE 42010, ISO/IEC 25010, the SEI's architecture body of work, TOGAF, and the pattern literature. Every framework here is traceable to a citable primary source, listed in References and further reading at the end.
Read it front to back once, then use the module sections as reference. Every module ends with a Task against one fictional case — Lumen Diagnostics — so the practice compounds instead of restarting each time. The case is the next unit; read it before starting Module 2. The capstone uses a different customer, Halcyon Standards Council — reuse the method, not the Lumen artefacts.
Who it is for. Developers, tech leads and consultants moving into solution architecture. It assumes you have built and shipped web systems and know basic cloud concepts; no prior architecture training is needed.
How each module works. It opens with what you will be able to do, and closes with Check yourself questions (answers included), a Task with a self-assessment table, and — where there is one — a worked Lumen answer. Attempt the Task before you read the worked answer; comparing the two is where most of the learning happens.
How to use this course
| Phase | Unit | What you produce | Rough time |
|---|---|---|---|
| Orientation | Module 1 | — | 1 h |
| Understand the business | Module 2 | Drivers, goals and SMART objectives, stakeholder register, power/interest grid, RACI, capability map, value stream, RAID log | 5–6 h |
| Nail the requirements | Module 3 (part 2 is the reference for it) | ASR list, utility tree, six-part scenarios, tactics for the top three quality attributes, an availability target derived from outage cost | 6–8 h |
| Choose the shape | Module 4 | Style and pattern decisions for three Lumen sub-problems, one Attribute-Driven Design iteration | 5–6 h |
| Draw it | Module 5 | Context and container diagrams | 2–3 h |
| Write it down | Module 6 | Software Architecture Document with 3+ views, interface descriptions, ADRs | 6–8 h |
| Sell and plan it | Module 7 | WBS, estimate, resource plan, contingency, discovery plan, five-year cost view | 5–6 h |
| Review and govern | Module 8 | A mini-ATAM review of your own design, a governance model | 4–5 h |
| Pick the technology | Module 9, parts 1 and 2 | Deployment view, availability calculation, five-year run cost, unit cost per referral; data and integration decisions | 11–13 h |
| Secure it | Module 10 | Threat model with trust boundaries, data classification, controls matrix, key and residency design | 6–7 h |
| Add AI where it pays | Module 11 | An AI architecture note for one Lumen use case: evaluation plan, guardrails, cost, fallback | 6–7 h |
| Capstone | All | Full technical RFP response for Halcyon, not Lumen | 15–20 h |
Times include reading and the Task, and vary widely with experience — treat them as a planning aid, not a target.
The case you will use. The module Tasks (Modules 2–11) are set on Lumen Diagnostics. The capstone is a separate RFP for Halcyon Standards Council. Do not copy Lumen stakeholders, ASRs or estimates into the Halcyon response.