Domain Modeling Made Functional

Wrapping Up

At the beginning of the chapter, we emphasized the importance of creating a shared model of the domain and solution—a model that is the same for the development team and the domain experts.

We then discussed four guidelines to help us do that:

• Focus on events and processes rather than data.
• Partition the problem domain into smaller subdomains.
• Create a model of each subdomain in the solution.
• Develop an “everywhere language” that can be shared between everyone involved in the project.

Let’s see how we applied them to the order-taking domain.

Events and Processes

The event-storming session quickly revealed all the major Domain Events in the domain. For example, we learned that the order-taking process is triggered by receiving an order ...