How to Event Model using markdown tables for AI
By @IvanTheGeek
Most basic slice (which is a column):
| SLICE-NAME-INTENT |
|---|
| UI |
| COMMAND/VIEW |
| EVENT |
Basic CommandSlice:
| COMMAND-SLICE-NAME-INTENT |
|---|
| UI |
| COMMAND |
| EVENT |
The naming for Slices is likely omitted from the graph as the command is usuaully the intent. Markdown is causing issues without a header file.
EXAMPLES:
| Slice1 |
|---|
| ExpenseScreen |
| LogLaundryExpense |
| ExpenseLogged |
| Slice1 |
|---|
| ExpenseScreen |
| LogLaundryExpense |
| ExpenseLogged |
| HOTEL |
|---|
| BookingScreen |
| BookRoom |
| RoomBooked |
Basic ViewSlice:
| VIEW-SLICE-NAME-INTERPRETATION |
|---|
| UI |
| COMMAND |
| EVENT |
The naming for Slices is likely omitted from the graph as the command is usually the intent.
- I@IvanTheGeek
Trigger: What ’triggers’ a use case? It can be a user via a UI or it can be a some external piece of software calling our public API. Or it can even be a robot aka an automated process.