Event Modelling
summary
Event modeling is a compact workflow of five elements — command, event, read model, gear, UX/UI — and seven steps that turn sticky-note brainstorms into a development blueprint. The example uses a ship-visit declaration: commands validate input, events record facts, gears automate translations or trigger follow-up commands, read models feed UIs, and slices map to teams for vertical-slice delivery and time estimates. Tools include Miro plugins, eventmodeling.org and Proofboard, and the plugin exports JSON to generate code.
AI-written summary · about
chapters (8)
- 0:00Introduction to event modeling
- 1:18Five elements of event modeling
- 2:22Seven steps to blueprint
- 3:30Storyboarding and UI/UX
- 5:12Commands and read models
- 6:59Aggregates and tests
- 8:26Tools and resources
- 9:13Slices and development tracking
related talks
50mHow EventStorming Transformed Our Domain Modeling Process
22mExample Mapping – Theory and Practice
40mBuilding Event Collection SDKs and Data Models
30mExample Mapping: A Structured, Collaborative Discovery Technique
41mEfficient Domain-Driven Design: An Introduction to Event Storming
50mEventStorming from the trenches
30mTurning stories into software
42mERD, Flowcharts and Other Documentation