Reference and Cross-Semester Map
This module is integrative. The "source of record" for most of its concepts is a prior-semester module you have already completed. This page maps each concept to:
- the prior-semester module that teaches it foundationally
- the external URL (curation-validated) that provides calibration, example, or reference
Open entries here only when a specific concept is fuzzy. Do not use this page as a reading list.
Cross-Semester Map by Cluster
Cluster 1: Scoping a Capstone
| Concept | Prior-semester source | External reference |
|---|---|---|
| Problem selection | S7 M01 Architecture Fundamentals (problem vs solution space); S8 M01 System Design (requirements) | What Is an MVP? (Eric Ries, leanstartup.co) |
| Risk register | S7 M05 ADRs & Reviews (risk-driven review); S8 M01 (capacity and risk) | Architecture Frames Requirements (Woods & Rozanski, PDF) |
| MVP definition | S8 M01 System Design (vertical slice) | What Is an MVP? (Eric Ries, leanstartup.co) |
Cluster 2: Domain Discovery
| Concept | Prior-semester source | External reference |
|---|---|---|
| EventStorming | S7 M03 Domain-Driven Design (strategic design) | EventStorming (eventstorming.com) |
| Core / supporting / generic subdomains | S7 M03 DDD (strategic design) | Bounded Context (Martin Fowler) |
| Ubiquitous language | S7 M03 DDD (ubiquitous language) | Ubiquitous Language (Martin Fowler) |
Cluster 3: Architecture Decision
| Concept | Prior-semester source | External reference |
|---|---|---|
| Characteristics selection | S7 M01 Architecture Fundamentals (characteristics catalog) | Architectural Katas (Neal Ford) |
| Style selection (monolith / modular monolith / services) | S7 M01 (styles catalog); S6 M05 Distributed Systems Fundamentals | Patterns of Distributed Systems (Martin Fowler) |
| Fitness functions | S7 M05 ADRs & Reviews (fitness functions) | Fitness function-driven development (Thoughtworks) |
Cluster 4: Design Communication
| Concept | Prior-semester source | External reference |
|---|---|---|
| Capstone design doc | S8 M01 System Design Methodology (design-doc template) | C4 model (c4model.com) |
| C4 diagrams at three levels | S7 M01 Architecture Fundamentals (diagramming) | C4 model (c4model.com) |
| ADRs | S7 M05 ADRs & Reviews (Nygard/MADR/Y-statement) | adr.github.io and joelparkerhenderson/architecture-decision-record |
Cluster 5: Planning for Reality
| Concept | Prior-semester source | External reference |
|---|---|---|
| 6-week schedule & anti-patterns | S8 M01 System Design (iteration cadence) | Continuous Integration (Martin Fowler) |
| Scope-cut rules | S8 M01 (tradeoffs); S7 M05 ADRs (supersede) | What Is an MVP? (Eric Ries, leanstartup.co) |
| Architecture defense | S7 M05 ADRs & Reviews (facilitation / probing) | Architecture Frames Requirements (Woods & Rozanski, PDF) |
External Reference Map
Every external URL used in this module is listed here with its specific role. All have been curation-validated at module authoring time.
Concept-to-Source Map
| Concept page | Best source if stuck | Why this source |
|---|---|---|
| Problem selection | S7 M01 Architecture Fundamentals (problem-vs-solution space concept page) | Foundational framing; the capstone version is the applied specialization. |
| Risk register | Woods & Rozanski PDF | Best practitioner argument that architecture and risk shape each other iteratively. |
| MVP definition | Eric Ries on leanstartup.co | The canonical short definition, which your capstone version extends with "vertical slice of every layer." |
| EventStorming at capstone scale | eventstorming.com (Big-Picture section) | Brandolini's own framing; use the Big-Picture flavor solo. |
| Core / supporting / generic subdomains | S7 M03 DDD (strategic design concept page) | Primary source in the degree's curriculum. |
| Ubiquitous language for a team of one | martinfowler.com/bliki/UbiquitousLanguage.html | One-page reference; re-read before writing the glossary. |
| Characteristics selection | S7 M01 Architecture Fundamentals (characteristics concept page) | Full catalog. Neal Ford katas extend it to drilling practice. |
| Style selection | S7 M01 (styles) + S6 M05 Distributed Systems | Cost of distribution is foundational; do not pick services without re-reading S6 M05. |
| Fitness functions | S7 M05 ADRs & Reviews (fitness functions concept page) | Primary source in the degree. Thoughtworks article shows the range of function types. |
| Capstone design doc | S8 M01 System Design Methodology (design-doc template) | Longer template; the capstone version compresses it. |
| C4 at three levels | c4model.com (Simon Brown's pages) | Canonical notation-independent definition. |
| ADRs for the capstone | S7 M05 ADRs & Reviews + joelparkerhenderson catalog | Primary source + example library. |
| 6-week capstone schedule | S8 M01 System Design (iteration cadence concept page) | Iteration discipline translates directly. |
| Scope-cut rules | S8 M01 (tradeoffs) + S7 M05 (supersede) | The pre-commit idea is native to both. |
| Defense | S7 M05 ADRs & Reviews (facilitation concept page) | The probing habits you learned there are the habits you must now survive. |
Read Only If Stuck
This module does not use "read only if stuck" -- because the source of record is always a prior module you already finished, not a book. If you are stuck, the escalation path is: re-read the concept page -> reread the linked prior-module concept page -> open the external URL for calibration -> talk to someone.
Optional Deep Dive
- Woods & Rozanski's full Software Systems Architecture -- the risk-driven architecture argument in book length.
- Vernon's Implementing Domain-Driven Design -- EventStorming and bounded contexts at team scale.
- Richards & Ford's Fundamentals of Software Architecture -- characteristics and fitness functions at depth.
- Brown's Software Architecture for Developers -- C4 in book length.
None of these are required. All are useful after the capstone, when you are applying the same habits to a team project.