Overview[1]#

Domain-Driven Design is a Software Development Life Cycle by connecting the implementation to with an Emergent Design.

Domain-Driven Design's main premise is the following:

• placing the project's primary focus on the core domain and domain logic;
• basing complex designs on a model of the domain;
• initiating a creative collaboration between technical and domain experts to iteratively refine a conceptual model that addresses particular domain problems.

The term was coined by Eric Evans in his book of the same title

Domain-Driven Design: Tackling Complexity in the Heart of Software Hardcover – August 30, 2003[3]

Bounded Context is a central pattern in Domain-Driven Design. Domain-Driven Design is the focus of DDD's strategic design section which is all about dealing with large models and teams. DDD deals with large models by dividing them into different Bounded Contexts and being explicit about their interrelationships.[2]

More Information#

There might be more information for this subject on one of the following:

• Bounded Context
• Domain
• Domain Event
• Entity
• Repository
• Service

---

• [#1] - Domain-driven_design - based on information obtained 2015-05-18
• [#2] - BoundedContext - based on 2015-05-18
• [#3] - Domain-Driven Design: Tackling Complexity in the Heart of Software Hardcover – August 30, 2003 - based on information obtained 2015-05-18