Process Step 4: Define the Conceptual Solution Architecture    (3ZRR)

Activity 4.3: Identify and analyze system and service transition dependencies    (3ZRS)

Activity Description:    (3ZRT)

During process step 5, transition options are developed and formulated into implementation recommendations. However, it is beneficial during process step 4 to analyze and explore transition alternatives that may be driven by logical dependencies, risks, or issues that may exist between as-is and target systems and services. This activity is focused on identifying, analyzing, and selecting recommendations for transition alternatives that are based on logical dependencies or other considerations (e.g., cost savings / cost avoidance) that may introduce intermediate transitional states along the path to achieving the target state. This analysis also helps to reduce and simplify the number of transition options to be included in the transition planning within process step 5.    (3ZRU)    (3ZRV)

Activity Inputs:    (3ZRW)

4.3.1 Identify and analyze alternatives for transition    (3ZS3)

In some cases, it may not be possible to plan a straightforward transition from the as-is to target systems and services state. One of the primary reasons for this task is to identify the need for intermediate target states that may be necessary on the road to achieving the ultimate goal of the target state.    (3ZS4)

Logical dependencies could be required to support a new system supporting a mission-critical need before an existing similar system is decommissioned in order to maintain continuity of operations. Additional transition constraints may sometimes be derived based on other factors or risks, such as budget cycle requirements for obtaining investment funds or the need to maintain an intermediate state between the as-is and the target during an extended deployment horizon. Examples of risks or issues include risks associated with implementing new technologies and complexity that requires several interrelated systems to undergo conversion at the same time.    (3ZS5)

The architecture decision matrix provides a structured approach to identifying alternatives for the transition from the as-is to the target conceptual solution architecture. This analysis technique identifies and analyzes risks and issues and develops alternatives to address each. The architecture decision matrix also provides a structured approach to determining risks associated with business fit along the dimensions of performance, business, data, and service management and includes consideration of risks or issues associated with technology fit for application, technology, and security components. Alternatives are captured using the matrix for a decision by the core team.    (3ZS6)

4.3.2 Develop recommendations outlining selected alternatives    (3ZS7)

Based on the analysis in the previous task, the core team selects the alternatives for transition. These may include implementing intermediate target states and developing alternative funding strategies based on cost and available investment funds. Once approved, these recommendations will carry forward into the summary of findings and recommendations developed for the segment blueprint in process step 5. Milestones for the recommendations may be established during this task, however, it is understood that additional milestones may be developed in process step 5 as well.    (3ZS8)

Communications Considerations:    (3ZS9)

Review and validate transition recommendation plans and resource requirements with appropriate governance bodies and key stakeholders.    (3ZSA)

Activity Outputs:    (3ZSB)

Suggested Analytical Techniques:    (3ZSF)    (3ZSJ)

Next Activity: 4.4 /Validate_and_communicate_the_conceptual_solution_architecture    (3ZSK)