Event storming
Method for modeling software systems / From Wikipedia, the free encyclopedia
Dear Wikiwand AI, let's keep it short by simply answering these key questions:
Can you list the top facts and stats about Event Storming?
Summarize this article for a 10 year old
Event storming is a workshop-based method to quickly find out what is happening in the domain of a software program.[1][2] Compared to other methods it is extremely lightweight and intentionally requires no support by a computer. The result is expressed in sticky notes on a wide wall.
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
|
The business process is "stormed out" as a series of domain events which are denoted as orange stickies. It was invented by Alberto Brandolini in the context of domain-driven design (DDD). Event storming can be used as a means for business process modeling and requirements engineering. The idea is to bring together software developers and domain experts and learn from each other.[3] The name was chosen to show that the focus should be on the domain events and the method works similar to brainstorming or agile modeling's model storming.