liveBook · Manning

Software design EventStorming

Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.

How 2 Manning books explain it

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.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains software design EventStorming →

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.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains software design EventStorming →

Also covered in

What to know first

Related concepts

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.