Domain-Driven Transformation

Chapter 11. Step 2—Modeling the Domain-Driven Target Architecture

The previous chapter discussed rediscovering domain knowledge; this chapter covers how that domain knowledge helps define the target architecture.

To model the domain-driven target architecture, we must derive the target context map from the subdomains modeled in step 1 (see Figure 11-1). This is the second step of the strategic Domain-Driven Transformation, the coarse-grained process that we saw in Figure III-1. In Figure 11-1, we see the substeps that make up step 2.

In Figure 11-1 the architecture analyst works together with the domain modeler on the following substeps: First, the target context map is derived from the subdomains and the to-be business processes (substep 2.1). Then, the bounded contexts in the context map are categorized as core, supporting, and generic subdomains (substep 2.2). In substep 2.3, the teams are assigned to the individual bounded contexts, and finally, in substep 2.4, the interfaces between the bounded contexts are defined.

Step 2, like step 1, takes place in an imaginary greenfield. Not until step 3 do we turn to the existing software system and leave the greenfield. This second step is about finding the ideal context map (ideal from today’s point of view). A target definition, in other words, that asks the question: “Where actually do we want to go?” At the same time, such a context map is never something final, but a snapshot. Better understanding of the domain and changes in it are ...