What are your experiences when facilitating modelling sessions such as EventStorming? Any tips or clue? What I experienced is that this visual anchor helps the group to reason about parts of the process, enabling a discussion about the different boundaries within a process it makes it easier to reason and discover those bounded contexts. Although there are some specialists in some parts of the process, the process doesn’t cross silos because they don’t exist! It is useful for use cases, where the group (or organisation) is in a scale-up mode. As example: Example of a visual anchor for a Big Picture EventStorming session Usually, at this point, the boundaries emerge, but not always.įor those cases, it’s good to use some visual anchors, as scaffolding for further exploration. At this point, the group starts to discuss the events and builds a coherent story. Thus, as a facilitator, I want to capture as many knowledge as people have, before given structure.Īfter the Chaotic Exploration, the group enters into the phase known as Enforcing the Timeline. However, by the nature of a Big Picture session, we start in a Chaotic Exploration mode, where the language is fuzzy, and boundaries (apparently) don’t exist. Quote from DDD Reference, from Eric Evans Model expressions, like any other phrase, only have meaning in context. It is often unclear in what context a model should not be applied. Communication among team members becomes confused.
#BOUNDED CONTEXT EXAMPLE SOFTWARE#
Multiple models are inevitable, yet when code based on distinct models is combined, software becomes buggy, unreliable, and difficult to understand. The tool set may also be different, meaning that program code cannot be shared. Teams working independently may solve the same problem in different ways through lack of communication. Two subsystems commonly serve very different user communities, with different jobs, where different models may be useful.
Multiple models are in play on any large project. Wait, what is a Bounded Context?īounded Context is a strategic design pattern described by Eric Evans in his seminal book “ Domain-Driven Design: Tackling Complexity in the Heart of Software“: During a Big Picture session, it is normal to see Bounded Contexts emerging. It aims to convey the knowledge across different silos, capturing what’s in people’s minds. One of the forms of EventStorming is Big Picture.
0 kommentar(er)
