A domain model is much more than the “M” in MVC. As Martin Fowler writes, “Learning how to design and use a Domain Model is a significant exercise--one that has led to many articles on the ‘paradigm shift’ of objects use.”
Let’s talk about evolving a domain model in sustainable ways that allow a codebase to organically grow in a way that supports agility and adaptability. Highlights include:
- What is a domain model? What are the alternatives?
- What is sustainable software development?
- Ubiquitous language, and thinking twice about naming something a Manager, Service, or DAO
- Sharing objects between client and server?
- Why mock objects?
- Bringing it together with outside-in test-driven development
Examples are in Ruby, JavaScript, and Java, but this is not a language-specific session.