Functional coupling
Noun based domain models have the downside of introducing high functional coupling in a system.
Which is contrary to the recommendation to keep coupling low and cohesion high.
When data is grouped in noun based models, subsequent steps in a business workflow need access to show, or amend, some of the data embedded in that model.
This couples each subsequent step to that functional model. Individual capabilities usually only care about a subset of the data.
As more nouns are introduced to the model, the functional coupling tends to increase.
A better way to divide your domain model is by business capability.
Only store the data required by the capability in a local model.
As the workflow progresses, pass data from one capability to the next.
This can be done either via the frontend, or via event publishing in the backend (depends on how much time there is between the steps).
