Note: this course is taught by Eric Evans in person.
Learn to put the domain model to work, hands-on, in this intensive 4-day course.
Finding and exploiting domain models is key to success with large software systems. By cultivating a strong connection between the language used by experts, users, and developers, the right kind of models can dramatically accelerate the process of translating the customers’ needs into working software. Strong domain modeling coupled with programming best practices such as exploiting design patterns, refactoring, and test-driven development yield a principled yet practical approach to the development of large software systems.
“The best class I’ve been to in a very long time. I went home, put my kids to bed, and started refactoring my system!”
This intensive course will aid participants in striking a healthy balance between digging into their subject matter and addressing technological issues, which, while unavoidable, cannot be allowed to dominate the development process for commercially viable systems.
We weave together lecture, discussion and classroom exercises, including hands-on coding projects. In discussions, attendees have the opportunity to discuss their own experiences and relate their own work to the principles and techniques presented in the class.
- Some exposure to medium to large-scale software development in a multi-team environment.
- Basic knowledge of object modeling and design.
- We encourage non-technical managers and analysts to attend. A mixed class is ideal. To make the code exercises work, we only need half of the attendees to have programming skills on the target platform (basic Java).
Day 1: Model Exploration and Ubiquitous Language
- Domain-driven design overview
- Making implicit concepts explicit
- Ubiquitous Language
- Brainstorming models
- Techniques and pitfalls of bringing about a creative collaboration.
Day 2: Strategic Design
Morning: Context Mapping
- Pragmatic approach to dealing with diverse models and designs on real projects
- Relationships between subsystems/ relationships between teams
Afternoon: Distilling the Core Domain
- Distinguishing the core from the mass
- Ways of focusing effort
- Clarifying a shared vision
- Setting up a project for success
Day 3: Implementation Concerns and Supple Design
- Expressing a model in software
- Building-block patterns (entities, value objects, repositories, etc.)
- Test-first development as a modeling process
- Patterns and techniques to tighten models and their connection to code.
- Making code obvious, easier to use and change
- Modeling for transactional integrity and distributed systems
Day 4: Bringing it Together
- Deeper into Strategic Design
- Design/code challenge – model supple design with context map
- In-depth discussion and Q&A, relating all topics to each other and to your own work
About Eric Evans
Eric Evans is the author of "Domain-Driven Design: Tackling Complexity in Software," Addison-Wesley 2004.
Since the early 1990s, he has worked on many projects developing large business systems with objects with many different approaches and many different outcomes. The book is a synthesis of that experience. It presents a system of modeling and design techniques that successful teams have used to align complex software systems with business needs and to keep projects agile as systems grow large.
Eric now leads "Domain Language", a consulting group which coaches and trains teams applying domain-driven design, helping them to make their development work more productive and more valuable to their business.