What Is Domain-Driven Design?

Part I. Strategic Design

According to the principles of domain-driven design, efficient software design requires knowledge of the business domain and the ability to model its problem domain. Discovery and modeling of domain knowledge is the topic of the first part of this report:

• In Chapter 1, we will look at patterns for exploring and analyzing the company’s business domain: core, generic, and supporting subdomains.

• Chapter 2 introduces an essential practice for knowledge discovery and sharing: using a ubiquitous language. You will see how this contributes to fostering a shared understanding between all project-related stakeholders.

• In Chapter 3, we will examine how to employ the “bounded context” pattern to transform the discovered knowledge into a model of the problem domain.

• Chapter 4 deals with the social aspect of software design—the interaction between teams working on the system’s components.

You will learn about DDD’s patterns for defining inter-team collaboration, and how each model can be beneficial. You will also see how to graphically plot these interactions and gain a bird’s-eye view of the project’s landscape.