Domain-Driven Transformation

Chapter 13. Step 4—Prioritization and Implementation of the Transformation Measures

This chapter concludes Part III and covers planning and conducting the transformation measures from the previous chapter. First, refactorings are broken down into manageable steps, then they are applied to the system under transformation.

From the sheer length of this chapter compared to the preceding chapters, it can be seen that step 4 takes more effort than steps 1 and 2, and even more effort than step 3.

After the idealized target context map was created in step 2, and the lists of findings and refactorings were developed in step 3, step 4 now deals with the prioritization and implementation of the refactorings.

In contrast to the refactorings, the findings cannot be implemented directly. At the end of this chapter, we will see how to deal with this challenge.

With the refactorings, the development team can finally get their hands on the code and implement their improvement ideas. But wait! Before that, there needs to be discussion with the development team, product owner, and architecture analyst. They need to choose the bounded context that should be carved out first.

In Figure 13-1 you can see the substeps that are now due. Product owner, architecture analyst, domain modeler, and developers choose the strategic refactoring from the refactoring list to extract the first bounded context (substep 4.1). Once this decision is made and possibly the next candidates are determined, the developers add ...