A model is a simplification. It is an interpretation of reality that abstracts the aspects relevant to solving the problem at hand and ignores extraneous detail.
#The Utility of a Model in Domain-Driven Design
Three basics uses determine the choice of a model.
-
The model and design shape each other: Their close connection ensures the analysis behind the model is reflected in the final product. This also makes maintenance easier, since the code can be understood through the model.
-
The model is a common language for the whole team: Developers and domain experts use the same terms to discuss the system, removing the need for translation between them.
-
The model is distilled knowledge: It reflects the team's agreed-upon way of thinking about and structuring the domain, helping developers and domain experts collaborate effectively.
#The Heart of Software
Software exists to solve real problems for its users. To do this well, developers must deeply understand the business domain and continuously sharpen their design and modeling skills.
Team leaders who grasp the importance of the domain can steer the project back on track when the focus on building a deep, meaningful model starts to fade.
Developers can use systematic thinking and proven design techniques to build effective models and bring order to complex software. Cultivating these skills makes a developer far more valuable, even in an unfamiliar domain.