Responsibility Driven Design Revisited
summary
Claims that modeling behavior first avoids data‑first design and reduces rework, demonstrated by modeling a Quest Worlds contest where a small prototype domain emerges: session maker, contest runner, result calculator, outcome adjudicator and a dice roller. Uses CRC cards and live collaboration with a tossed ball to simulate message flow, then maps responsibilities, collaborators and contracts. Finds RDD aligns with TDD (tests drive behaviors), encourages tearing up and iterating cards, and points to Rebecca Wirfs‑Brock’s free PDF for deeper guidance.
AI-written summary · about
chapters (8)
- 0:00Responsibility Driven Design intro
- 1:02Domain Driven Design overview
- 10:57Responsibility Driven Design explained
- 20:10Stereotypes and roles in RDD
- 30:31Quest Worlds modeling
- 40:08CRC cards and assignment
- 46:13CRC card simulations
- 51:29Modern relevance and call to action
related talks
40mBarely Enough Design
01h 11mAn introduction to DDD
58mDDD really matters!
57mDomain-Driven Design in Productland
51mUXDD: A New Pragmatic Methodology for Domain Modeling and User Experience.
39mDomain-Driven Design: Hidden Lessons from the Big Blue Book
01h 04mDomain Driven Design: The Good Parts
01h 05mGetting to DDD: Pragmatic or Principled?