SuperAPI AI Directory

event-storming

Coding & development

View repository

Updated 11-13 03:38

About this skill

Event Storming

When to use

  • The requirements or specifications lack descriptions of events
  • You are unsure about naming events or distinguishing between events and resources
  • You want to organize and add to Event Storming artifacts (events/commands/aggregates/read models)

Rules (key points)

  • An event is a significant occurrence in the domain and is expressed as a past tense verb
  • Because events represent important business behavior, organize around events
  • As a principle, one event per command , and do not generate multiple events from one command
  • Make the verb in the command name correspond to the verb in the event name (e.g., AddCartItem → CartItemAdded)
  • If the verbs differ, treat them as separate events and do not confuse them (e.g., AppendCartItem に CartItemAdded do not assign)
  • Express relationships using "R(, )"

For details, refer to references/event-storming-notes.md .

Procedure (concise)

  1. List the significant occurrences and finalize the event names in past tense
  2. Work backward to determine the command corresponding to each event
  3. Determine the aggregate that receives each event and adjust the boundaries
  4. Define the read models needed for queries
  5. Organize R(Event, Resource) / R(Event, Event) / R(Resource, Resource)
  6. If the distinction between events and resources is unclear, apply the decision rules

Output template

## Event Storming の前提モデル

### イベント
- ...

### コマンド
- ...

### 集約
- ...

### リードモデル
- ...