Why bother with models?
Many development teams undertake modeling, yet they often end up with little more than a data schema which does not deliver on the productivity promises for object design. What does it take to make a domain model truly pull its weight and positively transform a project? To do that we need a model that is not just a diagram or an analysis artifact, but that provides the very foundation of the design, the driving force of analysis, even the basis of the language spoken on the project.
In this talk, Eric Evans outlines some of the foundations of domain-driven design:
- How models are chosen and evaluated
- How multiple models coexist
- How the patterns help avoid the common pitfalls, such as overly interconnected models
- How developers and domain experts together in a domain-driven design team engage in progressively deeper exploration of their problem domain and make that understanding tangible as a practical software design.
View the 60-minute InfoQ exclusive presentation Domain-Driven Design - Putting Models to Work to learn how to tackle complexity in software. Remember - the most critical complexity of most software projects is understanding the business domain itself.