Henning loves to code. He follows this passion as a software architect and consultant at WPS – Workplace Solutions in Hamburg, Germany. His projects are domain-driven designed, agile and in programming languages like Java, C# and even ABAP. Henning is interested in the evolution of domain models, long-living software architectures and big refactorings. Recently he translated »Domain-Driven Design distilled« into german. Henning is married and has children.
(With Stefan Hofer)
DDD practitioners want to identify bounded contexts and work out ubiquitous languages. Domain experts, however, often work together across contexts. The boundaries that shape our software systems must therefore not become borders that prevent people from working together. Domain Storytelling helps us to see how bounded contexts are connected. Domain Storytelling means that we bring together domain experts and developers. We let them tell us stories about their collaborative tasks. While listening, we record the stories using a pictographic language. The experts can see immediately whether or not we understand their story. After very few stories, we are able to talk about the people, tasks, tools, work items, and events in that domain. The visualized stories give us clues for finding context boundaries. As we learn more about a domain and refine our ubiquitous languages, we will adapt the context boundaries. The talk will consist of two parts: We introduce Domain Storytelling with a short, interactive tutorial. In the second part, we will discuss examples. These will illustrate how to find context boundaries and how to capture cooperation across contexts.
(With Stefan Hofer)
When we want to apply DDD, we must first master the domain. In this hands-on session, I will show you how you can build up domain knowledge with Domain Storytelling. Domain Stories help us better understand a domain, to identify what is core, to segregate bounded contexts, and to constitute ubiquitous language.
Domain Storytelling means that we let domain experts tell us stories about their tasks. While listening, we record the stories using a pictographic language. The domain experts can see immediately whether or not we understand their story. After very few stories, we are able to talk about the people, tasks, tools, work items, and events in that domain.
Suggested structure:
Missed #DDDEU?
Get tickets for the next edition
