Software design EventStorming
Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
Process modeling EventStorming is an EventStorming format that uses structured, detailed collaborative modeling to design or analyze a business process and its future states.
- How it is used
- Designs future-state business processes during product or process modernization.
- How deep it goes
- Distinguishes structured, detailed process modeling from chaotic big picture exploration, but does not specify software-level implementation.
- Examples
- Uses customer dropout from a purchasing flow as a problem worth investigating before redesign.
- What you can do after
- Practice/perform collaborative design of a new or future-state process after identifying problems and opportunities.
Collaborative Software Design: How to facilitate domain modeling decisions
Software Design EventStorming is an EventStorming format for designing and implementing software around specific business scenarios.
- How it is used
- Shapes software design and implementation around a specific business scenario through collaborative event-flow modeling.
- How deep it goes
- Guides collaborative scenario modeling through events, timelines, legends, assumptions, and design alternatives; defers implementation mechanics.
- Examples
- Uses ticket purchasing and separate group event models merged into a scenario timeline.
- What you can do after
- Evaluate/understand scenario-driven software design decisions, assumptions, and competing bounded-context alternatives collaboratively.
Also covered in
What to know first
- big picture EventStormingBig picture EventStorming is a collaborative format for exploring a broad business domain and identifying its domains, subdomains, and complexity.
- customer problemA customer problem is a need, difficulty, constraint, or desired outcome experienced by an intended user or customer that a product or service may address.
- Domain Message Flow ModelingDomain Message Flow Modeling is a technique for representing messages exchanged among participants, subdomains, or systems in a business domain.
- Example MappingExample Mapping is a collaborative technique for clarifying a requirement by organizing its rules, examples, and open questions.
Related concepts
- chaotic explorationhas part · Chaotic exploration is a collaborative discovery mode in which participants contribute knowledge and ideas in parallel before imposing structure.
- eventuses · A software event is an occurrence, state change, or notification that a system can detect, record, communicate, or handle.
- big picture EventStormingincludes · Big picture EventStorming is a collaborative format for exploring a broad business domain and identifying its domains, subdomains, and complexity.
- collaborative discovery and modelingkind of · Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.
- customer journeyuses · A customer journey is the sequence of interactions and experiences through which a person pursues a goal while engaging with a product, service, or organization.
- Domain Storytellingcontrasts with · Domain Storytelling is a collaborative modeling technique that captures domain knowledge through visual stories of actors, activities, objects, and interactions in a process.
Questions about software design EventStorming
What is software design EventStorming?
Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.
Which Manning books explain software design EventStorming?
Architecture Modernization: Socio-technical alignment of software, strategy, and structure and Collaborative Software Design: How to facilitate domain modeling decisions.
What should I know before learning software design EventStorming?
Manning books that teach software design EventStorming usually introduce big picture EventStorming, customer problem, Domain Message Flow Modeling and Example Mapping first.
What is the difference between software design EventStorming and Domain Storytelling?
Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior. Domain Storytelling is a collaborative modeling technique that captures domain knowledge through visual stories of actors, activities, objects, and interactions in a process.
What kinds of software design EventStorming are there?
Kinds of software design EventStorming include big picture EventStorming.
What is software design EventStorming a kind of?
Software design EventStorming is a kind of collaborative discovery and modeling. Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

