What writing a book taught us about collaborative modeling


Writing a book about a modeling method (in our case: Domain Storytelling) necessarily makes you reflect on your own modeling practices. We had to frame things that we intuitively did in workshops. And we had to put our own approach into relation to other modeling methods. In this Meetup, we would like to talk about two concepts that came from these thoughts and discuss with you if they are applicable to collaborative modeling in general:

Scope: Before a workshop, we try to figure out which kind of model is needed to make the workshop successful. This led to the concept of “scope”: Which point in time should we model? At which level of granularity should we model? Should we model the pure business process or how the software-supported process works?

Scenario-based modeling: Several modeling methods that are popular with DDD practitioners are based on scenarios – meaning that one model shows only one case. Scenarios help a lot to learn and to deal with complexity. But they also raise the questions of which scenarios are relevant and how to keep an overview over many scenarios.


Follow us

Read our latest news from Virtual DDD on any of these social networks!

Recent videos

Managing Domain Knowledge with Chris Simon

From example mapping, to BDD, to DDD practices like event storming and domain storytelling, we're fortunate to have a wide range of tools for collaboratively building domain knowledge and creating models of those domains in software. One gap that many...

Connascence: beyond Coupling and Cohesion – Marco Consolaro

In 2009 Jim Weirich defined Connascence as "The Grand Unified Theory Of Software Development". The concept it is simple, yet very powerful in context of Object Oriented software development. It generalizes the ideas of Cohesion and Coupling, combining them...