(An introduction to) Domain Storytelling
summary
Domain Storytelling is presented as a collaborative modeling method that brings domain experts and development teams together to record users’ task stories using a simple pictographic notation. The talk explains how recording a few such stories makes it easy to identify people, tasks, tools, work items, events, clarify requirements, and find microservice boundaries.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 4:10From cave paintings to Domain Storytelling
- 7:01Speaker background
- 8:07Breaking down monoliths
- 9:12Leasing example
- 12:20Why Domain Storytelling?
- 13:03Creative Modeling explained
- 15:53Workshop roles
- 17:21Storytelling with experts
- 18:50Active listening and misunderstandings
- 21:19Simple notation and symbols
- 25:32Why model one case?
- 27:00Scenario-based modeling
- 28:07Actors and work objects
- 30:13Scope and granularity
- 32:03First exercise: Train journey
- 43:03Train journey summary
- 44:06Purpose of Domain Stories
- 45:09Link to User Stories
- 48:23Code derivation from Stories
- 49:48Domain language in code
- 50:08Strategic design and modularization
- 51:33Tools for Domain Storytelling
- 53:37Book and resources
- 54:01Q&A
related talks
50mHow EventStorming Transformed Our Domain Modeling Process
30mTurning stories into software
41mEfficient Domain-Driven Design: An Introduction to Event Storming
30mExample Mapping: A Structured, Collaborative Discovery Technique
01h 29mDriving Engagement with User Stories
12mWhat a Good User Story Should Look Like
54mDomain Driven Testing: Know What You're Doing
24mStorytelling with data