After identifying the gap between base and target architectures, consider how to reach the target while addressing risks. Conduct a context analysis to identify factors influencing the project, such as stakeholders and regulations, and a risk analysis to identify potential project risks, categorizing them by probability and impact. Assign actions to manage these risks. Context analysis also identifies positive factors to leverage. Both analyses are crucial for continuous risk management and sustainable change management in the project.

Implementing a new business model involves more than just programming an application. It requires a gap analysis to compare current and target process landscapes and enterprise architecture, identifying necessary changes. The analysis specifies tasks and deliverables (documents, software, hardware, workflows, regulations) needed to achieve objectives. This informs effort estimation and decision-making. Omitting gap analysis risks overlooking critical aspects, necessitating a thorough, methodical change management process, potentially including retiring outdated components and structures.

Implementing a new business model affects business processes, potentially requiring new workflows, organizational structures, and collaboration models. Changes in business processes influence application services, leading to modifications in application components and software, impacting IT infrastructure. Additionally, new business models raise important security concerns, possibly necessitating changes in IT department organization. Using standard modeling for the target process landscape helps visualize project complexity, with new entities in green and changes highlighted in red, indicating the scope of required modifications.