Domain Driven Design Meetup - Focus on Bounded Context
Two developers from Signal Iduna have presented their approach to modularizing application domains as part of strategic domain-driven design. Their focus was on experiences in using the “Bounded Context Canvas”.
The Bounded Context Canvas is presented by the DDD crew as a collaborative tool to describe a bounded context. The department and technology work together here. The goal is a general and shared understanding of the domain, the development of the common language (→ Ubiquitous Language), and the identification of incoming and outgoing communication (queries, commands, and events).
The experiences of the two speakers, Kai Rüstmann and Falco Wehber, show that even in a highly regulated market (insurance) and a large company (Signal Iduna has many thousands of employees), there is the possibility of establishing agile processes and applying DDD. The challenges are sometimes enormous because it is important to get ahead of the wave with the process. What they meant by this was to develop and model the bounded context with the department and technology before creating a new one The project has been “staggered”, financed, and has already started rolling.
Another aspect of the lecture looked at the visualization of the processes using the “Domain Storytelling” method. You use it as a precursor to the Bounded Context Canvas. The domain storytelling artifacts, such as actors, work items, and activities, are reflected in the ubiquitous language, communication, and business rules. Appropriately, I'm currently reading the book Domain Storytelling by Stefan Hofer and Henning Schwentner (the authors were present). This resulted in inspiring discussions.
The central insight from this evening is to see how the theory from the books interacts to create value, that domain storytelling works in complex processes and pays off in the modeling step that follows.
