Introduction
The Architecture Development Method (ADM) is a core component of the TOGAF framework, providing a structured approach to developing and managing enterprise architecture. However, the ADM is often misunderstood as a linear, waterfall process. This guide aims to clarify the iterative nature of the ADM, highlighting key concepts, best practices, and practical examples to ensure effective implementation.
Key Concepts in ADM Iteration
1. Iterative Nature of ADM
The ADM is not a linear process but an iterative one. It involves cyclical phases that allow for continuous improvement and adaptation. Each iteration of the ADM refines the architecture, ensuring it aligns with the organization’s evolving needs and goals.
2. Information Flow
The ADM graphic represents essential information flows rather than a sequential process. It shows how different phases of the ADM interact and how information is exchanged between them. Understanding this information flow is crucial for effective architecture development.
3. Interdependency of Phases
The phases of the ADM are interdependent. Changes in one phase can impact others. For example, developing a Target Architecture (Phase E) requires considering the current architecture (Phase B) and the gaps that need to be addressed (Phase C).
4. Essential Outputs
Each phase of the ADM produces essential outputs that serve as inputs for other phases. For instance, the Architecture Vision (Phase A) provides the foundation for the Business Architecture (Phase B), which in turn informs the Information Systems Architectures (Phase C) and Technology Architecture (Phase D).
5. Effective Information Inputs and Outputs
Practitioners must use effective information inputs and produce useful outputs. This ensures that the architecture development process is efficient and aligned with the organization’s goals.
Best Practices for ADM Iteration
1. Start with Phase A
Every ADM cycle must start with Phase A (Architecture Vision). This phase initiates the architecture project and defines the scope, stakeholders, concerns, and business objectives. Without a clear vision, the subsequent phases lack direction and coherence.
2. Consider the Impact on All Domains
When developing the Target Architecture, practitioners must consider the impact on all other domains. This includes understanding the resulting set of gaps and the work required to address them. This holistic approach ensures that the architecture is comprehensive and aligned with the organization’s goals.
3. Use Effective Information Inputs
Ensure that each phase of the ADM uses effective information inputs. This includes consuming mandatory inputs and producing mandatory outputs. For example, roadmap development (Phase E) requires inputs from the Architecture Vision (Phase A) and the current architecture (Phase B).
4. Produce Useful Outputs
Each phase of the ADM must produce useful outputs that inform subsequent phases. For instance, the Architecture Vision (Phase A) should provide a clear foundation for the Business Architecture (Phase B), which in turn should inform the Information Systems Architectures (Phase C) and Technology Architecture (Phase D).
5. Address Complexity with Effective Techniques
The interdependent nature of developing a Target Architecture requires considering the entire architecture, resulting gaps, and the work to address them simultaneously. Best practice ensures practitioners use effective techniques to manage this complexity, such as gap analysis and impact assessment.
6. Tailor the ADM to Specific Needs
Depending on the specific requirements of the architecture project, the phases of the ADM used will vary. For example, integrating an acquisition may require a different configuration of the ADM compared to modernizing a platform. Tailoring the ADM to specific needs ensures that the architecture development process is efficient and aligned with the project’s goals.
Practical Examples of ADM Iteration
Example 1: Moving to the Cloud
Objective: Enable cloud migration while keeping organizational design, customer interface, and processes unmodified.
ADM Iteration:
- Phase A (Architecture Vision): Define the scope, stakeholders, concerns, and business objectives for cloud migration.
- Phase B (Business Architecture): Assess the current business architecture and identify gaps that need to be addressed for cloud migration.
- Phase C (Information Systems Architectures): Develop the information systems architecture that supports cloud migration while keeping organizational design, customer interface, and processes unmodified.
- Phase D (Technology Architecture): Define the technology architecture required to support cloud migration.
- Phase E (Opportunities and Solutions): Develop a roadmap that outlines the steps for cloud migration, addressing identified gaps and work packages.
- Phase F (Migration Planning): Create an implementation and migration plan that details the steps for cloud migration.
- Phase G (Implementation Governance): Implement governance mechanisms to ensure that the cloud migration adheres to the architectural requirements and constraints.
- Phase H (Architecture Change Management): Manage the architectural changes required for cloud migration and ensure that the implementation delivers the expected value.
Example 2: Integrating an Acquisition
Objective: Integrate an acquisition with minimal change while sustaining current high-efficiency processes and unique capabilities.
ADM Iteration:
- Phase A (Architecture Vision): Define the scope, stakeholders, concerns, and business objectives for integrating the acquisition.
- Phase B (Business Architecture): Assess the current business architecture and identify gaps that need to be addressed for integrating the acquisition.
- Phase C (Information Systems Architectures): Develop the information systems architecture that supports the integration while sustaining current high-efficiency processes and unique capabilities.
- Phase D (Technology Architecture): Define the technology architecture required to support the integration.
- Phase E (Opportunities and Solutions): Develop a roadmap that outlines the steps for integrating the acquisition, addressing identified gaps and work packages.
- Phase F (Migration Planning): Create an implementation and migration plan that details the steps for integrating the acquisition.
- Phase G (Implementation Governance): Implement governance mechanisms to ensure that the integration adheres to the architectural requirements and constraints.
- Phase H (Architecture Change Management): Manage the architectural changes required for integrating the acquisition and ensure that the implementation delivers the expected value.
Example 3: Modernizing a Platform
Objective: Modernize a particular platform without impacting anyone outside IT.
ADM Iteration:
- Phase A (Architecture Vision): Define the scope, stakeholders, concerns, and business objectives for modernizing the platform.
- Phase B (Business Architecture): Assess the current business architecture and identify gaps that need to be addressed for modernizing the platform.
- Phase C (Information Systems Architectures): Develop the information systems architecture that supports the modernization while ensuring no impact outside IT.
- Phase D (Technology Architecture): Define the technology architecture required to support the modernization.
- Phase E (Opportunities and Solutions): Develop a roadmap that outlines the steps for modernizing the platform, addressing identified gaps and work packages.
- Phase F (Migration Planning): Create an implementation and migration plan that details the steps for modernizing the platform.
- Phase G (Implementation Governance): Implement governance mechanisms to ensure that the modernization adheres to the architectural requirements and constraints.
- Phase H (Architecture Change Management): Manage the architectural changes required for modernizing the platform and ensure that the implementation delivers the expected value.
Conclusion
Understanding the iterative nature of the ADM is crucial for effective enterprise architecture development. By following best practices and utilizing key concepts such as the iterative nature of the ADM, information flow, interdependency of phases, essential outputs, effective information inputs and outputs, addressing complexity, and tailoring the ADM to specific needs, organizations can ensure that their architecture development process is efficient and aligned with their goals. Practical examples, such as moving to the cloud, integrating an acquisition, and modernizing a platform, demonstrate the application of these concepts in real-world scenarios. By adopting these best practices and leveraging the capabilities of modeling and analytic software, organizations can achieve strategic alignment, efficient resource allocation, and successful implementation of their enterprise architecture goals.