[ENG] Master your Domain with Domain Storytelling @ DDD Europe

2h Hands-On at Domain-Driven Design Europe 2017.

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.

Transcript

1. Brought to you by Stefan (@hofstef) and Henning (@hschwentner). We are two DDD Enthusiasts working at WPS – Workplace Solutions GmbH in the beautiful city of Hamburg.
2. @hofstef @hschwentner
3. @hofstef @hschwentner
4. @hofstef @hschwentner Domain Knowledge
5. @hofstef @hschwentner Ludwig Wittgenstein »Whereof one cannot speak, thereof one must be silent.«
6. @hofstef @hschwentner Start the container Domain Expert IT Expert
7. @hofstef @hschwentner Fach- sprache Domain Expert IT Expert
8. @hofstef @hschwentner @hofstef @hschwentner
9. @hofstef @hschwentner
10. @hofstef @hschwentner Schedule 1. Domain Storytelling Applied 2. Domain Storytelling Explained 3. Exercises 4. Reflection
11. Exercise 1: Learn about the cinema domain „Reserve Tickets at the Cinema Counter“ as Domain Story @hofstef @hschwentner
12. @hofstef @hschwentner Workshop Result
13. Pictographic Language @hofstef @hschwentner
14. @hofstef @hschwentner actor work object activity annotation
15. @hofstef @hschwentner customer reservation number writes down
16. @hofstef @hschwentner person group IT-System
17. @hofstef @hschwentner …asks for reservation …sends reservation to …prints reservation reservation reservation reservation asks for prints to sends
18. @hofstef @hschwentner The cashier tells the customer her reservation number. tells reservation number customer cashier
19. @hofstef @hschwentner 1 1 1
20. Concrete Stories @hofstef @hschwentner
21. @hofstef @hschwentner
22. @hofstef @hschwentner actor work object activity
23. @hofstef @hschwentner asks for Reservation (movie, time, seats) cashier customer 1 Screen plan finds available seats in CineSoft 2 seats recommends 3
24. @hofstef @hschwentner Draw here Leave some empty space there  Annotations, variations, and purpose Preconditions, assumptions, and triggers
25. @hofstef @hschwentner „Three good examples are better than a bad abstraction.“ Paraphrased from: Peter Hruschka in Busines Analysis und Requirements Engineering, S.102, Hanser, 2014
26. Workshops @hofstef @hschwentner
27. @hofstef @hschwentner
28. @hofstef @hschwentner @hofstef @hschwentner
29. @hofstef @hschwentner
30. Tools @hofstef @hschwentner
31. @hofstef @hschwentner PowerPoint asks for Reservation (movie, time, seats) cashier customer 1 Screen plan finds available seats in CineSoft 2 seats recommends 3
32. @hofstef @hschwentner Visio, yEd, draw.io, …
33. @hofstef @hschwentner ADOxx/ Open Models Initiative austria.omilab.org/psm/content/egpm/info
34. @hofstef @hschwentner Whiteboard Kit
35. Exercises @hofstef @hschwentner
36. Participants‘ Feedback
37. Stefan: sh@wps.de @hofstef speakerdeck.com/hofstef http://domainstorytelling.org The pictures used in this talk are public domain, unless noted otherwise. Screenshots and examples © WPS - Workplace Solutions GmbH Henning: hs@wps.de @hschwentner speakerdeck.com/hschwentner