13.7 Summary

In this chapter, we evaluated strategies for transforming the architecture of the legacy RSS to a modern, component-based architecture. The strategy we followed in this chapter can be applied in other architectural transformations and other decisions for which the consequences are not immediately apparent. The strategy is simple: When selecting among several unknown paths, walk down each path a hundred yards before deciding on the most appropriate route.

Once the transformation strategy is understood , we can consider an optional, preparatory step. The purpose of this step is to prepare the system for architectural transformation, or componentization, in the case study. The preparatory step may involve code reduction, retargeting, refactoring, or another form of reengineering. Whatever steps are taken, the development team must be confident that these steps will reduce the overall cost, and possibly complexity, of the architectural transformation. Precomponentization options for RSS are considered in the next chapter.