The terms FlowMade uses
FlowMade works with a small set of terms: four core concepts, a few more once you go deeper, and a comparison with the EventStorming and DDD vocabulary for those who know it.
Event
Something that has happened, and that the process reacts to. For example: "Quote approved".
Action
Something someone does on purpose. For example: "Prepare the quote".
Role
The person or function that performs an action. For example: "Employee" or "Manager".
Automation
A rule that automatically reacts to an event. For example: "Apply the loyalty discount when the customer ordered before".
And if you want to go deeper?
Entity
The things and data your process revolves around — a quote, an order.
Boundary
The edge of a coherent part of your business — not just a visual grouping, but where one whole ends and the next begins.
Business Area
A larger area of your business, made of several coherent parts.
These simple terms correspond to the professional terms of EventStorming and DDD. If you already know those, FlowMade will feel familiar fast:
| Simplified | EventStorming / DDD |
|---|---|
| Business Area | Bounded Context |
| Boundary | Aggregate |
| Entity | Entity |
| Action | Command |
| Event | Domain Event |
| Automation | Policy |
| View | Read Model |
| Role | Actor |
| Question | Hotspot |
| Integration | External System |
Not every rule in the model is automated — some deliberately stay human decisions.