Responsibility Driven Design Revisited
summary
Argues that Responsibility-Driven Design is the missing foundation under DDD and shows concrete modeling tools: write a design story, pull out candidates, and flesh responsibilities on CRC cards then simulate a use case with index cards and a soft‑ball pass. Models a Quest Worlds contest end‑to‑end (session creation, dice roll, result calculator, outcome adjudicator) and iterates to distributed, delegated control. Produces explicit roles, collaborations and contracts that simplify implementation and reduce rework.
AI-written summary · about
chapters (13)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:30Introduction: Why Responsibility-Driven Design Matters
- 3:10The Origins of DDD & What’s Missing
- 6:40The Problem with Data-Centric Modeling
- 10:05What is Responsibility-Driven Design?
- 14:20Core Concepts: Responsibilities, Roles & Behavior
- 18:45Objects, Collaboration & Control Styles Explained
- 22:30From Theory to Practice: Design Story & Themes
- 26:10Identifying Candidates & Modeling with CRC Cards
- 30:05Simulating Behavior Through Use Cases
- 33:40Refining Models: Responsibilities & Collaborations
- 36:10Applying RDD in Modern Agile Development
- 38:20Final Thoughts: Why Behavior-First Design Wins
related talks
38mModel-Driven Design
38mWhat I talk about when I talk about Domain Driven design
44mStrategic Domain-Driven Design for dummies
35mTrivialization of DDD or Not?
47mDomain-Driven Design: A Complete Example
01h 01mThe DDD Do-Over: Domain-Driven Design Lessons Learned
45mDon't Overdose on Domain-Driven Design
29m20 Years of Domain-Driven Design: What I’ve Learned About DDD