Evans Eric. Domain-Driven Design: Tackling Complexity in the Heart of Software

Addison Wesley, 2003. — 560 p. — ISBN 0-321-12521-5.Specific topics covered include:Representing processes as domain objects
Creating functions free of side effects
Conceptual contours
Standalone classes
Extending specifications
Applying analysis patterns
Relating design patterns to the model
Maintaining model integrity
Formulating the domain vision statement
Choosing refactoring targets
Responsibility layers
Creating a pluggable component framework
Bringing together large-scale structures and bounded contextsPraise for Domain-Driven Design
ForewordContrasting Three Projects
The Challenge of Complexity
Design Versus Development Process
The Structure of This Book
Who Should Read This Book
A Domain-Driven TeamPutting the Domain Model to Work
Crunching Knowledge
Ingredients of Effective Modeling
Knowledge Crunching
Continuous Learning
Knowledge-Rich Design
Deep Models
Communication and the Use of Language
Ubiquitous Language
Modeling Out Loud
One Team, One Language
Documents and Diagrams
Explanatory Models
Binding Model and Implementation
Model-Driven Design
Modeling Paradigms and Tool Support
Letting the Bones Show: Why Models Matter to Users
Hands-On ModelersThe Building Blocks of a Model-Driven Design
Isolating the Domain
Layered Architecture
The Domain Layer Is Where the Model Lives
The Smart UI "Anti-Pattern"
Other Kinds of Isolation
A Model Expressed in Software
Associations
Entities (a.k.a. Reference Objects)
Value Objects
Services
Modules (a.k.a. Packages)
Modeling Paradigms
The Life Cycle of a Domain Object
Aggregates
Factories
Repositories
Designing Objects for Relational Databases
Using the Language: An Extended Example
Introducing the Cargo Shipping System
Isolating the Domain: Introducing the Applications
Distinguishing ENTITIES and VALUE Objects
Designing Associations in the Shipping Domain
AGGREGATE Boundaries
Selecting REPOSITORIES
Walking Through Scenarios
Object Creation
Pause for Refactoring: An Alternative Design of the Cargo AGGREGATE
MODULES in the Shipping Model
Introducing a New Feature: Allocation Checking
A Final LookRefactoring Toward Deeper Insight
Breakthrough
Story of a Breakthrough
Opportunities
Focus on Basics
Epilogue: A Cascade of New Insights
Making Implicit Concepts Explicit
Digging Out Concepts
How to Model Less Obvious Kinds of Concepts
Supple Design
Intention-Revealing Interfaces
Side-Effect-Free Functions
Assertions
Conceptual Contours
Standalone Classes
Closure of Operations
Declarative Design
A Declarative Style of Design
Angles of Attack
Applying Analysis Patterns
Example
Earning Interest with Accounts
Example
Insight into the Nightly Batch
Analysis Patterns Are Knowledge to Draw On
Relating Design Patterns to the Model
Strategy (A.K.A.Policy)
Composite
Why Not FLYWEIGHT?
Refactoring Toward Deeper Insight
Initiation
Exploration Teams
Prior Art
A Design for Developers
Timing
Crisis as OpportunityStrategic Design
Maintaining Model Integrity
Bounded Context
Continuous Integration
Context Map
Relationships Between BOUNDED CONTEXTS
Shared Kernel
Customer/Supplier Development Teams
Conformist
Anticorruption Layer
Separate Ways
Open Host Service
Published Language
Unifying an Elephant
Choosing Your Model Context Strategy
Transformations
Distillation
Core Domain
An Escalation of Distillations
Generic Subdomains
Domain Vision Statement
Highlighted Core
Cohesive Mechanisms
Segregated Core
Abstract Core
Deep Models Distill
Choosing Refactoring Targets
Large-Scale Structure
Evolving Order
System Metaphor
Responsibility Layers
Knowledge Level
Pluggable Component Framework
How Restrictive Should a Structure Be?
Refactoring Toward a Fitting Structure
Bringing the Strategy Together
Combining Large-Scale Structures and BOUNDED CONTEXTS
Combining Large-Scale Structures and Distillation
Assessment First
Who Sets the Strategy?
Six Essentials for Strategic Design Decision MakingEpilogues
Looking Forward
Appendix The Use of Patterns in This Book
Pattern Name