← Graph

Event Modeling

concept 6 connections

Modeling technique coined by Adam Dymitruk in 2018 at the EventStorming Summit, originally called 'single flow event storming'. Draws business processes like frames in a movie on a board, using a limited vocabulary: commands (blue stickies — intents to change state), events (orange stickies — business facts, with who/what/where/when properties), views/read models (green stickies — what the user sees) and automations (robots listening for events and dispatching commands between modules). Avoids technical terms like policies or aggregates. Events form the contract between slices. Includes a completeness check — for every field in an event or view, verify where it first appeared — with Miro board extensions that automate it. Mateusz Nowak prefers it over process-level and design-level EventStorming and uses it to organize work into parallel vertical slices (write/read/automation).

category
practice
coined_at
EventStorming Summit 2018
coined_by
Adam Dymitruk
former_name
single flow event storming
about
Event Modeling concept
Uses Event Modeling as the core modeling notation and process.
about
Event Modeling concept
Asks how calculations are expressed in Event Modeling terminology.
person Mateusz Nowak
recommends
Event Modeling concept
Prefers Event Modeling over process-level and design-level EventStorming.
concept Event Modeling
related_to
Adam Dymitruk person
Event Modeling was coined by Adam Dymitruk at the EventStorming Summit 2018, originally as 'single flow event storming'.
concept Event Modeling
related_to
EventStorming concept
Event Modeling evolved from EventStorming and shares the event-first vocabulary.
concept Vertical Slice
related_to
Event Modeling concept
Event Models are split vertically into write, read and automation slices for parallel team work.

Provenance

Read by
2 extractions