Home › Resources › Monthly archive

March 2009

Preface to Domain-Driven Design (pages xix-xxvi)

by Eric Evans

Leading software designers have recognized domain modeling and design as critical topics for at least twenty years, yet surprisingly little has been written about what needs to be done or how to do it. Although it has never been formulated clearly, a philosophy has emerged as an undercurrent in the object community, a philosophy I call domain-driven design.

Table of Contents

Foreword
Preface
Acknowledgments

Part I. Putting the Domain Model to Work

Foreword to Domain-Driven Design (pages xvii-xviii)

by Martin Fowler
April 2003

There are many things that make software development complex. But the heart of this complexity is the essential intricacy of the problem domain itself. If you’re trying to add automation to complicated human enterprise, then your software cannot dodge this complexity— all it can do is control it.

About the cover

Why this cover?

  • Finding order in chaos and complexity
  • Creating a language of abstraction
  • Putting those abstractions to work
  • 3137 reads

Chapters 16 & 17

Domain Driven Design Final Session
Chapter 16 + Chapter 17
February 3, 2004
Guest author: Eric Evans

Russ: p. 442, "large-scale structure can save a project?"

Chapter 14

Notes 20 January 2004
Domain Driven Design (VIII)
Guest Author: Eric Evans

Russ: Let's start with Strategic Design (Part IV) -- what do we need it for? How about considering the ways to get in trouble on the extremes. How do you look at a system and understand whether we're doing what Eric's doing, or one of the bad alternatives he discussed. (p. 328, halfway down). The more systems I see, the more surprised I am by the range of systems

Chapter 10 continued

Notes 13 Jan 2004
Domain Driven Design (VII)
Guest Author: Eric Evans

(Ken Scott-Hlebek starts with a discussion of the "Master of Software Arts" program at UIUC. He is part of the group of students involved in a trial run.)

Russ: Perhaps we could move on to Chapter 10? (starting p.246, Intention-Revealing Interface)

John B: Smalltalk Best Practice Patterns, "Intention-Revealing Selector." I tend to think of the Java keyword for interfaces.

Chapters 10 & 13

Domain Driven Design (VI) + Industry Roundtable
Guest Author: Eric Evans
Notes by John Brewer and Jeff Miller

(some discussion of John Corbett's picture discussed on the list representing evolution of a software system and easy/hard features within reach)

(lengthy roundtable discussion, omitted, of interesting new trends in software, eventually rolling around to outsourcing)

Part III Intro & Chapter 8

December 2003
Notes 9, 4th Session
Guest Author: Eric Evans

Part III introduction

Robert: The 3 issues on p.188, the qualifications for doing domain-driven development

(mention of OO databases)

Eric: [use of OO databases is rare] Because there aren't so many people using rich domain models.

Tracy: Isn't there also a comfort level with relational databases?

Robert: And ad-hoc reporting, etc.

Chapters 3 & 4

25-Nov-2003
Domain Driven Design (Evans) II.
Notes by Jeff Miller

This meeting revisits the final published form of a book that SVP reviewed in an earlier draft two years ago.

(some comments and questions unattributed)

(notes start with discussion in progress)

(previous to this point, Eric compared and contrasted model-driven design with domain-driven design)