Hands-on: Introduction to domain storytelling





Who is this presentation for?
- Developers, architects, and domain experts
Level
Description
When you want to apply DDD, you must first master the domain. In this hands-on examination, Stefan Hofer, and Dorota Kochanowska show you how to build up domain knowledge with domain storytelling. Domain stories help you better understand a domain, identify what is core, segregate bounded contexts, and constitute ubiquitous language.
Domain storytelling means that you let domain experts tell you stories about their tasks. While listening, you record the stories using a pictographic language. The domain experts can see immediately whether or not you understand their story. After very few stories, you’re able to talk about the people, tasks, tools, work items, and events in that domain.
Outline:
- Motivation and short, interactive tutorial (“my first domain story”)
- Domain storytelling explained
- Hands-on group exercise 1
- Feedback
- Hands-on group exercise 2
- Clues for identifying bounded contexts
- Develop ubiquitous language
- Retrospective (using an interactive workshop format)
What you'll learn
- Gain a new modeling tool for your toolbox
Stefan Hofer
WPS - Workplace Solutions
Stefan Hofer is bad at drawing. However, he thinks he can build up domain knowledge by drawing domain stories. He hops from one domain to the next, assisting people to figure out how software can help them to get their job done. Stefan studied software engineering in Austria, has a PhD in computer science, and co-authored a book about Domain Storytelling.

dorota kochanowska
Workplace Solutions
Dorota Kochanowska is a software architect at Workplace Solutions, where she consults for a migration process from individual to off-the-shelf software. As a computer scientist, she’s worked in different domains like banking, telecommunication, or managing international IT projects.
Comments on this page are now closed.
Gold Sponsor
Silver Sponsors
Exhibitor
Innovator
Supporter
Diversity & Inclusion Sponsor
Contact us
confreg@oreilly.com
For conference registration information and customer service
partners@oreilly.com
For more information on community discounts and trade opportunities with O’Reilly conferences
Become a sponsor
For information on exhibiting or sponsoring a conference
pr@oreilly.com
For media/analyst press inquires
Comments
With the rise of micro-services and now micro-frontends, How can we better organize product owners and team to efficiently to take advantage of DDD and devise a good ownership model?
There will be services and subsystems and teams working on various subsystems/domains (and sometimes team owing multiple subsystems) in an enterprises and there will be always an area where multiple work converges.
In there lies confusion around domain ownership. Would like to hear stories or advices on how teams can collaborate without stepping on each others toes.