Skip to main content

Learning Resources

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

Learning objectives​

  • Explain Learning Resources in terms of architectural scope, quality attributes, and tradeoffs instead of slogans about “good design.”
  • Use Learning Resources 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, learning-domain-driven-design 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
  • learning-domain-driven-design

Source routes​

Clean Architecture​

Fundamentals Of Software Architecture​

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

Just Enough Software Architecture​

  • /books/just-enough-software-architecture via Fairbanks: Approach description, Fairbanks: Architects architecting architectures, Fairbanks: Example - home media player, Fairbanks: Guidance on choosing techniques, Fairbanks: Integration of COTS components part 1, Fairbanks: Integration of COTS components part 2, Fairbanks: Planned and evolutionary design, Fairbanks: Project management risks, software engineering risks, Fairbanks: Risk-driven model, Fairbanks: Team communication part 1, Fairbanks: Team communication part 2, Fairbanks: Team communication part 3, Fairbanks: What is software architecture, Fairbanks: Why is software architecture important (1)

Learning Domain Driven Design​

Supporting curriculum routes​

No supporting curriculum routes linked yet.

External enrichment​

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 Learning Resources, and treat outside material as supporting enrichment only.