Module 5: Architecture Decision Records & Reviews
This page aggregates the generated reference routes used by the learner-facing module.
- Semester:
semester-07-architecture-ddd - App:
architecture
Read only if stuck
- Fundamentals: Defining software architecture
- Fundamentals: Architectural thinking
- Fundamentals: Analyzing trade-offs
- Fundamentals: Architecture decisions
- Just Enough: Software architecture
- Just Enough: Why is software architecture important (part 1)
- Just Enough: Why is software architecture important (part 2)
- Just Enough: Make rational architecture choices
- Just Enough: Risk-driven model
- Fundamentals: Basic structure (ADR)
- Fundamentals: Architecture decision records
- Just Enough: Team communication (part 1)
- Just Enough: Team communication (part 2)
- Just Enough: PM risks vs SE risks
- Just Enough: Guidance on choosing techniques
- Just Enough: Planned and evolutionary design
- Just Enough: Features and risk - a story
- Just Enough: Quality attribute scenarios
- Just Enough: Analyzing architecture models (part 1)
- Just Enough: Analyzing architecture models (part 2)
- Fundamentals: Risk matrix
- Fundamentals: Making teams effective
- Fundamentals: Team warning signs
- Fundamentals: Leveraging checklists
- Fundamentals: Negotiation and facilitation
- Fundamentals: Negotiating with other architects
- Fundamentals: The software architect as a leader
- Fundamentals: Leading teams by example
- Fundamentals: Risk storming
- Fundamentals: Risk storming examples
- Just Enough: Team communication (part 3)
- Fundamentals: Measuring architecture characteristics
- Fundamentals: Fitness functions
- Fundamentals: Integrating with the development team
- Fundamentals: Developing a career path
- Just Enough: Architectural mismatch
- Just Enough: Challenges (part 1)
- Just Enough: Challenges (part 2)
- Fundamentals: Basic structure