Reference and Selective Reading

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-01-architecture-fundamentals-quality/reference/index.md
• App: architecture
• Semester: semester-07-architecture-ddd
• Module: module-01-architecture-fundamentals-quality
• Unit kind: reference
• Curation level: module_curated

Learning objectives

• Explain Reference and Selective Reading in terms of architectural scope, quality attributes, and tradeoffs instead of slogans about “good design.”
• Use Reference and Selective Reading to reason about why certain decisions become expensive to reverse as systems and teams grow.
• Use clean-architecture, fundamentals-of-software-architecture, just-enough-software-architecture to connect the learner-facing explanation to concrete architecture characteristics, scenarios, and decision framing.

Prerequisites

• Comfort with systems, databases, and the idea that different design choices create different operational tradeoffs.

Source books

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

Source routes

Clean Architecture

• /books/clean-architecture via Clean: Behavior to fight for the architecture, Clean: The goal

Fundamentals Of Software Architecture

• /books/fundamentals-of-software-architecture via Fundamentals: Analyzing trade-offs, Fundamentals: Architectural thinking, Fundamentals: Architecture characteristics defined, Fundamentals: Architecture characteristics ratings, Fundamentals: Balancing architecture and hands-on coding, Fundamentals: Case study - Going, going, gone - discovering components, Fundamentals: Case study - Silicon Sandwiches partitioning, Fundamentals: Connascence, Fundamentals: Cross-cutting architecture characteristics, Fundamentals: Defining software architecture, Fundamentals: Discovering components, Fundamentals: Engineering practices, Fundamentals: Explicit characteristics, Fundamentals: Extracting characteristics from requirements, Fundamentals: Fitness functions, Fundamentals: Going, going, gone case study, Fundamentals: Have business domain knowledge, Fundamentals: Identifying architectural characteristics, Fundamentals: Implicit characteristics, Fundamentals: Measuring architecture characteristics, Fundamentals: Measuring modularity, Fundamentals: Measuring modularity 2, Fundamentals: Modularity, Fundamentals: Monolithic vs distributed architectures, Fundamentals: Operations - DevOps, Fundamentals: Scope of architecture characteristics

Just Enough Software Architecture

• /books/just-enough-software-architecture via Fairbanks: Example - home media player, Fairbanks: Integration of COTS components (part 1), Fairbanks: Integration of COTS components (part 2), Just Enough: Approach description, Just Enough: Architects architecting architectures, Just Enough: Guidance on choosing techniques, Just Enough: PM risks vs SE risks, Just Enough: Planned and evolutionary design, Just Enough: Risk-driven model, Just Enough: Team communication (part 1), Just Enough: Team communication (part 2), Just Enough: Team communication (part 3), Just Enough: What is software architecture, Just Enough: Why is software architecture important (part 1)
• /books/just-enough-software-architecture/chapter-03-architects-architecting-architectures via Just Enough: Architects architecting architectures
• /books/just-enough-software-architecture/chapter-05-what-is-software-architecture via Just Enough: What is software architecture
• /books/just-enough-software-architecture/chapter-06-why-is-software-architecture-important-part via Just Enough: Why is software architecture important (part 1)
• /books/just-enough-software-architecture/chapter-08-approach-description via Just Enough: Approach description
• /books/just-enough-software-architecture/chapter-09-risk-driven-model via Just Enough: Risk-driven model
• /books/just-enough-software-architecture/chapter-11-guidance-on-choosing-techniques via Just Enough: Guidance on choosing techniques
• /books/just-enough-software-architecture/chapter-12-planned-and-evolutionary-design via Just Enough: Planned and evolutionary design
• /books/just-enough-software-architecture/chapter-15-example-home-media-player via Fairbanks: Example - home media player
• /books/just-enough-software-architecture/chapter-16-team-communication-part via Just Enough: Team communication (part 1), Just Enough: Team communication (part 2), Just Enough: Team communication (part 3)
• /books/just-enough-software-architecture/chapter-17-integration-of-cots-components-part via Fairbanks: Integration of COTS components (part 1), Fairbanks: Integration of COTS components (part 2)

Supporting curriculum routes

No supporting curriculum routes linked yet.

External enrichment

• Martin Fowler: Evolutionary Architecture and Fitness Functions (optional_deep_dive) - Connects architecture characteristics to measurable, evolving constraints in real systems.
• SEI Quality Attribute Workshop (official_docs_companion) - Provides a disciplined way to think about quality-attribute scenarios and architectural reasoning.

AI companion modes

• Explain simply
• Diagnose my confusion
• Revision mode
• 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 Reference and Selective Reading, and treat outside material as supporting enrichment only.