Scribd
Upload
13 views2 pages

Architecture Development Method

TOGAF Architecture Development Method

Uploaded by

devendra_rit
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
13 views2 pages

Architecture Development Method

TOGAF Architecture Development Method

Uploaded by

devendra_rit
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Architecture Development Method

(ADM)
Project Description:
Let's imagine a scenario where Company A is supporting a client with their digital transformation
efforts. In this context, the Architecture Development Method (ADM) from TOGAF standards plays a
crucial role.

The ADM provides a proven and repeatable process for developing architectures that align IT
strategies with business goals. As Company A guides their client through digital transformation, ADM
can be systematically applied to ensure that all technological investments and decisions support the
client’s overall objectives.

Here’s how ADM fits into the picture:

Preliminary Phase:
 Goal: Get ready for the digital transformation.
 Activities: Company A sets up a framework for the project, defines guiding principles (like
focusing on customer experience), and gets approval from Toyota's top management.

Phase A: Architecture Vision:


 Goal: Define what Toyota wants to achieve with the digital transformation.
 Activities: Company A works with Toyota to create a high-level plan, set goals (like
improving production efficiency and customer satisfaction), identify stakeholders (like
factory managers, IT staff, and customers), and develop a business case showing the benefits
of the transformation.

Phase B: Business Architecture:


 Goal: Design the business processes to support the transformation.
 Activities: Company A maps out Toyota's current business processes, identifies what needs
to change (like automating certain manufacturing steps), and defines new business functions
and roles needed to support the digital initiatives.

Phase C: Information Systems Architectures:


 Goal: Design the data and application systems.
 Data Architecture: Company A decides how data will be stored and managed, such as
implementing a centralized database for real-time tracking of parts and inventory.
 Application Architecture: Company A defines how different software applications (like
supply chain management and customer relationship management systems) will interact
and support the new business processes.
Phase D: Technology Architecture:
 Goal: Plan the technology infrastructure needed.
 Activities: Company A specifies the hardware, software, and network infrastructure needed
to support the new systems, such as new servers, cloud services, and enhanced
cybersecurity measures.

Phase E: Opportunities and Solutions:


 Goal: Identify projects to implement the transformation.
 Activities: Company A conducts a gap analysis to see what's missing, prioritizes projects (like
upgrading the assembly line with IoT devices), and creates a high-level plan for
implementing these projects.

Phase F: Migration Planning:


 Goal: Develop a detailed roadmap for the transformation.
 Activities: Company A creates a step-by-step migration plan, defines interim states (like
phases of upgrading different plants), and plans resource allocation (budget, time, and
personnel).

Phase G: Implementation Governance:


 Goal: Ensure the plan is followed correctly.
 Activities: Company A monitors the implementation, manages any changes needed during
the process, and ensures everything complies with the planned architecture.

Phase H: Architecture Change Management:


 Goal: Manage changes as the transformation evolves.
 Activities: Company A sets up a process to handle new change requests, assesses these
requests, and updates the architecture to accommodate new business needs or
technological advancements.

Requirements Management:
 Goal: Continuously manage and prioritize requirements.
 Activities: Company A captures, analyses, and tracks requirements throughout the project,
ensuring they are addressed in each phase and adjusting priorities as needed.

You might also like