Alistair Jones and James Lewis (May 7,2008)

Domain Driven Design is a philosophy for writing software, that places emphasis on a business-aligned domain model, and provides a vocabulary for how to implement the model in object oriented code. Following DDD when writing business software focuses effort on the high-value parts of the system, and helps consistent translation of business concepts into objects.

We give an overview of Domain Driven Design and then discuss the practical implications of following it. How do you implement an isolated domain model? What kinds of objects do you need in your model? How does your model make use of Dependency Injection and Object-Relational Mapping? We will introduce an example business domain, identify roles that objects could play in the domain model, and then show how to implement those objects in code. Are you following DDD? What are your experiences with it? What are the reasons why you wouldn't choose to follow it?