Event Storming also enables the early identification of risks
Posted: Sat Jan 25, 2025 5:46 am
However, event storming is hardly known in the requirements engineering community, even though it is a very lightweight brainstorming method for quickly obtaining an overview of the entire business process to be mapped in the software. Event storming is also an excellent method for requirements gathering and analysis, as it does not require any modeling knowledge and hardly any preparation.
In event storming, all relevant business events are first collected and put in the correct order. Care is taken early on to ensure that everyone involved speaks the same language. Homonyms and synonyms are identified and standardized. Then it is analyzed what has to happen for an event to occur. This could be, for example, commands from the user, sets of rules or a decision from a third-party system. Based on this, business processes, data objects and aggregates as well as the required information on the user interfaces (view models) can be derived.
The events and their triggers are clustered into different areas bolivia consumer email list​ and summarized in specialist and subdomains, whereby the timeline can now be neglected. Based on the subdomains, the context boundaries, relationships and dependencies can then be defined. The result is the basis for the domain model and for an initial software design.
oddly designed business processes and know-how gaps. All critical areas, key features, risks and opportunities for improvement are marked accordingly. This means that there are no surprises later.
This gives the system a good, maintainable structure and the number of refactorings is lower than without the knowledge acquired in Event Storming.
How can a requirements engineer support the domain-driven design approach?
The answer is basically obvious from Dr. Ute Heimann's quote: the focus is on the technical aspects, not the technology. As a result, a requirements engineer can familiarize himself with the procedure and provide excellent support even without a deeper technological background.
In everyday business, a requirements engineer works closely with experts to identify and capture the goals and business requirements. His tasks also include creating a context overview and defining the context boundaries.
By understanding the core concept of Domain Driven Design, the Requirements Engineer will be able to create the domain model together with the architect and model the business domain logic using the patterns and principles of Domain Driven Design. In doing so, the Requirements Engineer can ensure that the design is aligned with the business goals and meets the requirements of the project.
The requirements engineer can also help define the ubiquitous language by creating a glossary so that the language is understood and spoken by the entire team.
Event Storming is incorporated into the standard toolbox of a requirements engineer, so that right from the start of the project the approach is aligned with Domain Driven Design, our customers are trained in it and understand the principle of Domain Driven Design.
In event storming, all relevant business events are first collected and put in the correct order. Care is taken early on to ensure that everyone involved speaks the same language. Homonyms and synonyms are identified and standardized. Then it is analyzed what has to happen for an event to occur. This could be, for example, commands from the user, sets of rules or a decision from a third-party system. Based on this, business processes, data objects and aggregates as well as the required information on the user interfaces (view models) can be derived.
The events and their triggers are clustered into different areas bolivia consumer email list​ and summarized in specialist and subdomains, whereby the timeline can now be neglected. Based on the subdomains, the context boundaries, relationships and dependencies can then be defined. The result is the basis for the domain model and for an initial software design.
oddly designed business processes and know-how gaps. All critical areas, key features, risks and opportunities for improvement are marked accordingly. This means that there are no surprises later.
This gives the system a good, maintainable structure and the number of refactorings is lower than without the knowledge acquired in Event Storming.
How can a requirements engineer support the domain-driven design approach?
The answer is basically obvious from Dr. Ute Heimann's quote: the focus is on the technical aspects, not the technology. As a result, a requirements engineer can familiarize himself with the procedure and provide excellent support even without a deeper technological background.
In everyday business, a requirements engineer works closely with experts to identify and capture the goals and business requirements. His tasks also include creating a context overview and defining the context boundaries.
By understanding the core concept of Domain Driven Design, the Requirements Engineer will be able to create the domain model together with the architect and model the business domain logic using the patterns and principles of Domain Driven Design. In doing so, the Requirements Engineer can ensure that the design is aligned with the business goals and meets the requirements of the project.
The requirements engineer can also help define the ubiquitous language by creating a glossary so that the language is understood and spoken by the entire team.
Event Storming is incorporated into the standard toolbox of a requirements engineer, so that right from the start of the project the approach is aligned with Domain Driven Design, our customers are trained in it and understand the principle of Domain Driven Design.