<!-- .slide: data-background="white" --> # Domain Driven Design aws event storming workshop 學習心得 --- <!-- .slide: data-background="white" --> ## 多人協做(~~多人混戰~~)系統  --- <!-- .slide: data-background="white" --> ## 多人協做系統的困難點 1. 每個參與者對系統理解不同 2. 系統要解決的問題很龐大，難以一次性處理 --- <!-- .slide: data-background="white" --> ## 使用相同語句來描述相同概念  --- <!-- .slide: data-background="white" --> ## 分而治之  --- <!-- .slide: data-background="white" --> # Domain(領域)  --- <!-- .slide: data-background="white" --> # Bounded Context * 為了有效討論, 界定某個關注的邊界使用相同語言描述概念 --- <!-- .slide: data-background="white" --> # 具體實踐 --- <!-- .slide: data-background="white" --> # Event Storming  * 在 2012 由 [Alberto Brandolini](https://www.avanscoperta.it/en/trainer/a-brandolini/) 提出 --- <!-- .slide: data-background="white" --> ## 範例 1. 需求：we were challenged to develop new software services to attend base functionalities of Inventa's new marketplace such as shopping cart, checkout payments, and order creations. --- <!-- .slide: data-background="white" --> ## 1. List Events  --- <!-- .slide: data-background="white" --> ## 2. Find the Actor and Command trigger Events  --- <!-- .slide: data-background="white" --> ## 3. Mapping out Complexity through Policies  --- <!-- .slide: data-background="white" --> ## 4. Reorganizing the Modeling Components in a Timeline  --- <!-- .slide: data-background="white" --> ## 5. Reorganizing the Modeling Components in a Timeline  --- ref: 1. https://medium.com/building-inventa/how-we-used-event-storming-meetings-for-enabling-software-domain-driven-design-401e5d708eb