ddd-crew / eventstorming-glossary-cheat-sheet Goto Github PK

I always find useful to show to EventStorming participants, the "Pro ES modeling tricks" Miro board @NTCoding made: https://miro.com/app/board/o9J_ksetago=/
Could we add a new section called "More tips & tricks" where we could add some useful links?

i think it should be splitted.
there is too much information, especially for a first titme person.

I propose these differents markdown files :
1- glossary(General Terms)
2- Event Storming big picture. (Specific glossary, techniques of splitting(swimlanes, ...), How To, facilitation)
3- Event Storming use cases. (Specific glossary, How To, facilitation)

What do you think about it team ?

Thank you for your contribution.

Let me take the liberty to ask a question.
Why Don't we have event storming + event modelling?

Just a minor typo, I don't know how to fix/PR the picture.

The cheat sheet talks about constraints but not about aggregates. In the change history, aggregates are marked as "legacy". However, there is not reasoning given. Alberto's book dedicates a whole chapter to aggregates so this cheat sheet gives a different idea about event storming which is confusing. It would be great to give the reasoning to better understand why we shouldn't use aggregates any more. I am afraid "...since we prefer not to use the word aggregate with business stakeholders" doesn't really explain it.
The cheat sheet says constraint "was called an aggregate before". But it seems constraint is a different concept from aggregate. The cheat sheet says a "constraint is a restriction we have or need to design from our problem space when we want to perform a command/action". Aberto mentions "aggregates as state machines" and "what I am really looking for are units of consistent behavior" - so a unit that behave in a specific, consistent way similar (but not identical) to aggregates in DDD tactical design.
Adding some reasoning somewhere would be great. Aggregate was a confusing term because they are also part of tactical design and Alberto's chapter in it current form doesn't really explain what they are. So changing the concept is a great idea but more explanation would be great. 🙂