DDD tactical patterns work best in a domain that has a fair amount of complexity.
In the startup phase of a system, you model often and turn it up-side-down when new insights emerge. However, when a first release is in production and the system keeps getting expanded, models stabilize, become more elaborate and need to tie in with other models.
To ensure common understanding, it is also important that models are consistent after changes and use the agreed ubiquitous language. But how to manage this just using whiteboards, brown paper and sticky notes (or the online version of those) ?
In this talk I will show how you can capture your DDD workshops output and convert them into models that can be easily maintained in a repository. Using these as a basis for designs, code and also to communicate about the system so that ubiquitous language is really applied, delivering clear documentation, easier impact analysis and quicker implementation of changes.