TOGAF — Architecture Development Method (ADM) — Part 2
This article is part of the Enterprise Architecture series. In previous article Architecture Development Method (ADM) — Part 1, we discussed first five phases of ADM The Preliminary Phase, Phase A: Architecture Vision, Phase B: Business Architecture, Phase C: Information Systems Architectures and Phase D: Technology Architecture
Next phase of ADM is
Phase E: Opportunities and Solutions is the fifth phase of the TOGAF . It focuses on identifying opportunities to improve the organisation’s systems and infrastructure and defining the solutions that will be implemented to address these opportunities.
The main objectives of Phase E are:
1. To identify opportunities for improvement in the organisation’s systems and infrastructure based on the results of the previous ADM phases.
2. To define the solutions that will be implemented to address these opportunities, including new or modified systems, processes, and infrastructure.
3. To define the scope of each solution, including the specific systems, processes, and infrastructure that will be affected.
4. To define the requirements for each solution, including the functional and non-functional requirements.
5. To develop a high-level plan for implementing each solution, including timelines and milestones.
6. To identify any risks or issues that may arise during the implementation of each solution and develop a plan for managing these risks and issues.
During this phase, the Opportunities and Solutions document is produced. It provides a comprehensive view of the opportunities for improvement in the organisation’s systems and infrastructure, and the solutions that will be implemented to address these opportunities. The document should be reviewed and updated regularly to ensure that the solutions remain aligned with the organisation
Phase F: Migration Planning is the sixth phase of the TOGAF. It focuses on defining the plan for migrating the organisation’s systems and infrastructure from the current state to the target state.
The main objectives of Phase F are:
1. To develop a detailed plan for migrating the organisation’s systems and infrastructure from the current state to the target state.
2. To define the specific steps that will be taken to migrate the organisation’s systems and infrastructure to the target state.
3. To identify any risks or issues that may arise during the migration process and develop a plan for managing these risks and issues.
4. To identify the organisational and technical dependencies that need to be considered when migrating to the target state.
5. To define the testing and validation procedures that will be used to ensure that the organisation’s systems and infrastructure are properly migrated to the target state.
6. To define the support and maintenance procedures that will be used after the migration is complete.
During this phase, the Migration Planning document is produced. It provides a comprehensive view of the plan for migrating the organisation’s systems and infrastructure from the current state to the target state, and it is used to guide the implementation of the migration plan. The document should be reviewed and updated regularly to ensure that the migration plan remains aligned with the organisation’s goals and objectives.
Migration Planning is an important step in the ADM, as it ensures that the organisation’s systems and infrastructure are properly migrated to the target state in a controlled and structured manner. It also helps to identify and mitigate any risks and issues that may arise during the migration process.
Phase G: Implementation Governance is the seventh phase of the TOGAF (The Open Group Architecture Framework). It focuses on defining the governance processes and policies that will be used to manage the implementation of the enterprise architecture (EA) initiative.
The main objectives of Phase G are:
1. To define the governance processes and policies that will be used to manage the implementation of the EA initiative.
2. To establish a governance structure that will be responsible for managing the implementation of the EA initiative.
3. To establish a set of metrics that will be used to measure the success of the EA initiative.
4. To establish a communication plan that will be used to keep stakeholders informed of the progress of the EA initiative.
5. To establish a change management process that will be used to manage changes to the organisation’s systems and infrastructure during the implementation of the EA initiative.
6. To establish a risk management process that will be used to identify and manage risks that may arise during the implementation of the EA initiative.
During this phase, the Implementation Governance document is produced. It provides a comprehensive view of the governance processes and policies that will be used to manage the implementation of the EA initiative, and it is used to guide the implementation of the EA initiative. The document should be reviewed and updated regularly
Phase H: Architecture Change Management is the eighth phase of the TOGAF. It focuses on defining the processes and procedures that will be used to manage changes to the organisation’s systems and infrastructure after the enterprise architecture (EA) initiative has been implemented.
The main objectives of Phase H are:
1. To define the processes and procedures that will be used to manage changes to the organisation’s systems and infrastructure.
2. To establish a change management process that ensures that changes to the organisation’s systems and infrastructure are aligned with the organisation’s goals and objectives.
3. To establish a process for evaluating and approving changes to the organisation’s systems and infrastructure.
4. To establish a process for implementing approved changes to the organisation’s systems and infrastructure.
5. To establish a process for testing and validating changes to the organisation’s systems and infrastructure.
6. To establish a process for monitoring and reporting on changes to the organisation’s systems and infrastructure.
During this phase, the Architecture Change Management document is produced. It provides a comprehensive view of the processes and procedures that will be used to manage changes to the organisation’s systems and infrastructure, and it is used to guide the management of changes to the organisation’s systems and infrastructure. The document should be reviewed and updated regularly to ensure that the change management process remains aligned with the organisation’s goals and objectives.
Architecture Change Management is an important step in the ADM, as it ensures that changes to the organisation’s systems and infrastructure are managed in a controlled and structured manner, and that they are aligned with the organisation’s goals and objectives. It also helps to identify and mitigate any risks and issues that may
Requirement management:
The Architecture Development Method (ADM) does not have a specific phase dedicated to requirement management. However, the process of gathering, analysing, and documenting requirements is an important aspect that is addressed throughout the various phases of the ADM.
In Phase A: Architecture Vision, the organisation’s goals and objectives are defined, which helps to identify the requirements for the EA initiative.
In Phase B: Business Architecture, the organisation’s business processes, functions, and information flows are identified and analysed, which helps to identify the requirements for the EA initiative.
In Phase C: Information Systems Architectures, the organisation’s information systems architecture is defined, which helps to identify the requirements for the EA initiative.
In Phase E: Opportunities and Solutions, the solutions that will be implemented to address the identified opportunities are defined, which includes the identification of requirements for the solutions.
In Phase F: Migration Planning, the specific steps that will be taken to migrate the organisation’s systems and infrastructure to the target state are defined, which includes the identification of requirements for the migration process.
In summary, requirement management is an ongoing process throughout the ADM and it is integrated in each phase of the ADM, which helps to ensure that the organisation’s systems and infrastructure are aligned with the organisation’s goals and objectives and support the business processes and functions.
Final Thoughts:
The TOGAF ADM provides a systematic approach for developing and managing an enterprise architecture, and can be used to ensure that the organisation’s systems, processes, and technology are aligned with its overall goals and strategies.
