Compare tactics and preserve the limits of evidence
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/concepts/cluster-06-evidence-contracts/18-tactic-experiments.md - App:
architecture - Semester:
semester-07-architecture-ddd - Module:
module-01-architecture-fundamentals-quality - Unit kind:
concept - Curation level:
module_curated
Learning objectives
- Explain Compare tactics and preserve the limits of evidence in terms of architectural scope, quality attributes, and tradeoffs instead of slogans about “good design.”
- Use Compare tactics and preserve the limits of evidence to reason about why certain decisions become expensive to reverse as systems and teams grow.
- Use
fundamentals-of-software-architectureto 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
fundamentals-of-software-architecture
Source routes
Fundamentals Of Software Architecture
- /books/fundamentals-of-software-architecture via
Fundamentals of Software Architecture
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
- Socratic tutor
- Challenge my understanding
- Diagnose my confusion
- Connect forward / backward
Source-of-truth note
This teaching unit is learner-facing guidance. Its canonical source backbone is the referenced book fundamentals-of-software-architecture, and outside material should only clarify or strengthen that backbone.