# ADM - Architecture Development Method

### **Introduction**

The Architecture Development Method (ADM) is the core of the TOGAF framework. It provides a step-by-step, iterative approach for developing and managing enterprise architecture to align IT solutions with business goals

The ADM cycle consists of **10 phases**, starting from establishing the architecture vision to managing its implementation and ongoing changes. Each phase delivers specific outputs, which are used in subsequent phases.

### **Phases of the TOGAF ADM**

1. **Preliminary Phase: Preparing the Architecture Effort**
    
    
    - **Purpose:** Establish the architecture capability within the organization.
    - **Key Activities:**
        - Define architecture principles.
        - Develop the architecture governance framework.
        - Set up the Architecture Repository.
    - **Outputs:**
        - Architecture Principles.
        - Governance Framework.
2. **Phase A: Architecture Vision**
    
    
    - **Purpose:** Define the high-level vision, goals, and scope of the architecture project.
    - **Key Activities:**
        - Identify stakeholders and their concerns.
        - Create an Architecture Vision document.
        - Validate business goals and objectives.
    - **Outputs:**
        - Statement of Architecture Work.
        - Architecture Vision document.
3. **Phase B: Business Architecture**
    
    
    - **Purpose:** Develop the business architecture to support the agreed architecture vision.
    - **Key Activities:**
        - Analyze the business strategy and objectives.
        - Define the business capabilities, processes, and organizational structure.
    - **Outputs:**
        - Business Architecture artifacts (catalogs, matrices, diagrams).
4. **Phase C: Information Systems Architectures**
    
    
    - **Purpose:** Define architectures for data and applications.
    - **Sub-phases:**
        - **Data Architecture:** Focuses on the organization and management of data.
        - **Application Architecture:** Addresses the structure and interaction of application systems.
    - **Outputs:**
        - Data and Application Architecture artifacts.
5. **Phase D: Technology Architecture**
    
    
    - **Purpose:** Develop the technology architecture to support business, data, and application needs.
    - **Key Activities:**
        - Identify technology standards and platforms.
        - Define infrastructure services and systems.
    - **Outputs:**
        - Technology Architecture artifacts (network diagrams, infrastructure models).
6. **Phase E: Opportunities and Solutions**
    
    
    - **Purpose:** Identify and prioritize potential solutions to address business needs.
    - **Key Activities:**
        - Assess and consolidate implementation opportunities.
        - Develop a high-level roadmap.
    - **Outputs:**
        - Transition Architecture(s).
        - Project work packages.
7. **Phase F: Migration Planning**
    
    
    - **Purpose:** Create a detailed implementation and migration plan.
    - **Key Activities:**
        - Develop a roadmap showing dependencies and timelines.
        - Align project sequencing with organizational priorities.
    - **Outputs:**
        - Implementation and Migration Plan.
8. **Phase G: Implementation Governance**
    
    
    - **Purpose:** Ensure the solutions are implemented in accordance with the defined architecture.
    - **Key Activities:**
        - Provide architectural oversight for projects.
        - Ensure compliance with standards and guidelines.
    - **Outputs:**
        - Architecture Contract.
        - Compliance assessments.
9. **Phase H: Architecture Change Management**
    
    
    - **Purpose:** Manage changes to the architecture and ensure it evolves with the business.
    - **Key Activities:**
        - Monitor the environment for changes.
        - Assess impact and update the architecture.
    - **Outputs:**
        - Updated Architecture Requirements.
        - Architecture Change Request.
10. **Requirements Management**

- **Purpose:** Central phase that spans the ADM cycle to ensure requirements are identified, managed, and traceable.
- **Key Activities:**
    - Maintain a continuous feedback loop between phases and stakeholders.
- **Outputs:**
    - Updated requirements documentation.

---

### **ADM Cycle and Iteration**

The ADM is **iterative**, allowing architects to revisit phases as required:

- **Iteration Levels:**
    - **Enterprise Level:** Broad, strategic initiatives.
    - **Segment Level/Functional Decompositions:** Focus on specific areas like departments or business functions.
    - **Capability Level:** Address specific capabilities or solutions.
- **Iteration Approach:**
    - **Analyse Current State:** Determine why changes are needed.
    - **Functional Decomposition:** Process of breaking down specific areas like departments, business functions, or deliverables into sub-systems.
    - **Define Future State**: Determine the set of conditions to meet the business needs.
    - **Benchmarking**: The process of comparing an organization’s practices, performance, and strategies against industry standards, competitors, or best-in-class organizations.
    - **Market Research**: The process of gathering, analyzing, and interpreting information about market trends, customer preferences, competitive landscapes, and emerging technologies.

---

### **Outputs of the ADM Phases**

Each ADM phase produces artifacts, deliverables, and building blocks:

- **Artifacts:** Detailed representations, such as diagrams and catalogs.
- **Deliverables:** formal outputs shared with stakeholders, such as an Architecture Definition Document.
- **Building Blocks:** components that represent either conceptual capabilities (ABBs) or deployable solutions (SBBs).

<div drawio-diagram="102"><img src="https://eu2.contabostorage.com/66dddabd753e470297bef6533e98fb71:bookstack/uploads/images/drawio/2024-11/drawing-1-1732518324.png" alt=""/></div>