Book Exercise Lanes

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface

• Open learner-facing unit
• Curriculum path: content/curriculum/architecture/semester-07-architecture-ddd/module-05-architecture-decision-records-reviews/exercises.md
• App: architecture
• Semester: semester-07-architecture-ddd
• Module: module-05-architecture-decision-records-reviews
• Unit kind: exercise
• Curation level: module_curated

Learning objectives

• Explain Book Exercise Lanes as part of an architecture feedback loop involving decisions, review, and long-term consequences.
• Use Book Exercise Lanes to make architecture work inspectable: what was decided, why, what risks remain, and how success will be measured.
• Use fundamentals-of-software-architecture, just-enough-software-architecture to connect the learner explanation to ADRs, review methods, and architectural fitness functions.

Prerequisites

• Comfort with architecture tradeoffs, modular patterns, DDD boundaries, and API design decisions from the earlier semester modules.

Source books

• fundamentals-of-software-architecture
• just-enough-software-architecture

Source routes

Fundamentals Of Software Architecture

• /books/fundamentals-of-software-architecture via Fundamentals: Analyzing trade-offs, Fundamentals: Architecture decision records, Fundamentals: Architecture decisions, Fundamentals: Basic structure (ADR), Fundamentals: Fitness functions, Fundamentals: Leveraging checklists, Fundamentals: Making teams effective, Fundamentals: Measuring architecture characteristics, Fundamentals: Negotiating with other architects, Fundamentals: Negotiation and facilitation, Fundamentals: Risk matrix, Fundamentals: Risk storming, Fundamentals: Risk storming examples

Just Enough Software Architecture

• /books/just-enough-software-architecture/chapter-09-risk-driven-model via Just Enough: Risk-driven model
• /books/just-enough-software-architecture/chapter-10-project-management-risks-software-engineering-risks via Just Enough: Project management risks vs software engineering risks
• /books/just-enough-software-architecture/chapter-11-guidance-on-choosing-techniques via Just Enough: Guidance on choosing techniques
• /books/just-enough-software-architecture/chapter-16-team-communication-part via Just Enough: Team communication part 2
• /books/just-enough-software-architecture/chapter-20-features-and-risk-a-story via Just Enough: Features and risk - a story
• /books/just-enough-software-architecture/chapter-50-quality-attribute-scenarios via Just Enough: Quality attribute scenarios
• /books/just-enough-software-architecture/chapter-63-analyzing-architecture-models-part via Just Enough: Analyzing architecture models part 1, Just Enough: Analyzing architecture models part 2
• /books/just-enough-software-architecture/chapter-64-architectural-mismatch via Just Enough: Architectural mismatch
• /books/just-enough-software-architecture/chapter-66-challenges-part via Just Enough: Challenges part 1, Just Enough: Challenges part 2

Supporting curriculum routes

No supporting curriculum routes linked yet.

External enrichment

• ADR GitHub Organization (official_docs_companion) - Connects ADR concepts to real templates and conventions learners can use immediately.
• SEI: Architecture Tradeoff Analysis Method (official_docs_companion) - Useful for connecting informal peer review with formal architecture-evaluation techniques.

AI companion modes

• Explain simply
• Socratic tutor
• Challenge my understanding
• Diagnose my confusion
• Connect forward / backward

Source-of-truth note

This teaching unit is learner-facing guidance assembled from multiple canonical book routes. Use the listed source books as the primary conceptual spine for Book Exercise Lanes, and treat outside material as supporting enrichment only.