> Home > Views & Perspectives < Prev | Next >
Event Storming
Event Storming, as described on eventstorming.com, “is a flexible workshop format for collaborative exploration of complex business domains”.
It is used in many scenarios of which the following are of interest to us.
- to explore the viability of a new start-up business model;
- to envision new services, that maximise positive outcomes to every party involved;
- to design clean and maintainable Event-Driven software, to support rapidly evolving businesses.
We have used this technique to identify the Domain Events that are evident in the system.
We’ve gone through each of the 10 initial requirements to come up with the business flow required to satisfy the requirement. The key element of the business flow is the event. Please note that this is not an exact process, and it is only used to clarify the concepts involved in the business processes. It also does not clarify which of the systems (Foods or Family) may take on the process in the final design.
Standard coloured boxes are used to draw these diagrams, as shown in the below key.
It is enough to keep the following in mind to understand these diagrams:
- The orange boxes represent Domain Events.
- The blue boxes represent Commands (which result in a Domain Event).
- The yellow boxes represent Users.
- The coloured boxes are placed on a time line.
The Key
The requirement numbers used here match those used in Business Goals and Requirements
Requirements #1, #6, and #7 : Customer Profile, Medical Profile, Profile Customization
Requirement #2 : Geographical Trend Analysis
Requirement #4: Dietician Advice & Interaction
Requirement #8: Third Party Relationships
Requirement #9: Holistic UX
Requirement #10: Customer Engagement
