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.
How to use this course
| Phase | Modules | What you produce |
|---|---|---|
| Understand the business | 1, 2 | Drivers/goals/objectives, stakeholder registry, RACI, functional decomposition |
| Nail the requirements | 3 | ASR list, utility tree, tactics for top-3 quality attributes |
| Choose the shape | 4, 5 | Style/pattern selection, models and diagrams |
| Write it down | 6 | Software Architecture Document with 3+ views |
| Sell and plan it | 7 | WBS, estimate, resource plan, discovery plan |
| Design, review, govern | 8 | ADD iterations, ATAM review, governance model |
| Pick the technology | 9 | Deployment view, availability calculation, running costs |
| Capstone | GW | Full RFP response for Halcyon, not Lumen |
The case you will use. Module homework (2–9) is 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.