vices could be shared is not possible. Hence, the identification of shared services will be incremental, like all other aspects of CMS modernization and transformation.
Implementation of the Mappings
A considerable amount of the meta-methodology described above is intended to ensure appropriate context and identification of affected source and target components. The actual transitions—modernizations or transformations—that result from the planned mappings, however, take place on individual components and/or the lowest-level elements of the architecture. The final task in the modernization and transformation of a chosen component is to plan for the implementation of the mappings defined in the fourth task above and then to implement them. For each of these mappings, the implementation plan will include (1) creating a development version of the newly envisioned technical ecosystem, (2) testing and evaluating this version against requirements, and (3) moving this ecosystem to production once the requirements are satisfied, replacing the source ecosystem. Implementing a single source to target information system mapping often requires a significant project and considerable resources.15, 16 Implementing a source to target information ecosystem mapping that involves multiple information systems is correspondingly larger and more complex, requiring an incremental approach.
The information ecosystems requirements developed in the above analysis and mapping steps should be used to justify the information ecosystem mapping and thus provide the information systems details for the relevant business case.
15 For example, see Michael L. Brodie and Michael R. Stonebraker, 1995, Legacy Information Systems Migration: The Incremental Strategy, San Francisco, Calif.: Morgan Kaufmann Publishers.
16 For example, see Willem-Jan van den Heuvel, 2007, Aligning Modern Business Processes and Legacy Systems: A Component-Based Perspective, Cambridge, Mass.: MIT Press.