Use bright yellow stickies to identify user roles or personas. Optional: Identify the various views that your users will need to carry out their actions, and important roles for various users. These event clumps or common groupings give us our notional service candidates (actors or aggregates depending on how rigid the team is with DDD definitions) These will be used during the Boris exercise. Clumping these nouns together into related trees of data can help you form your aggregates. You can also crowd-source identification of the nouns present on the event-storming board and place them to the side. If you want to start bounding models with less permanence use stickies to mark general areas and withhold drawing boundaries with permanent markers until your confidence justifies it. Draw lines with arrowheads to show direction of domain events flowing between bounded contexts. Tip: Draw boundaries and lines with arrows to show flow on the modeling surface. Highlight anything caused by a set time period (like batch processes or cron jobs) in a new color sticky note and place them next to triggers they controlĪfter all the events are posted, pair with the domain experts to post a locally ordered sequence of events and enforce a timeline.
Storm it systems series#
Have the group “storm the business” process by writing a series of domain events on orange sticky notes, one per note. It’s expressed as a verb in the past tense, such as ‘Order Placed’ or ‘Refund Initiated’.” Example: “A ‘Domain Event’ represents a state transition in the domain.
0 kommentar(er)
