.
Preliminary Phase
Phase A (Architecture Vision)
Phase B (Business Architecture)
Phase E (Opportunities and Solutions)
Preliminary Phase
Phase A (Architecture Vision)
Phase B (Business Architecture)
Phase H (Architecture Change Management)
Part II: Architecture Development Method
Part III: ADM Guidelines and Techniques
Part VI: TOGAF Reference Models
Part VII: Architecture Capability Framework
Enterprise Architecture Capability
IT Governing Board
Program Management Office
Quality Assurance department
Phase E (Opportunities and Solutions)
Phase F (Migration Planning)
Phase G (Implementation Governance)
Phase H (Architecture Change Management)
Part I, the Enterprise Continuum describes a model for structuring a virtual repository
Part II, the Architecture Development Method, describes the definitions of terms used in TOGAF and the difference between TOGAF versions
Part III, Tools and Support, describes a collection of guidelines and techniques which can be used in the method
Part VII, the Architecture Capability Framework, describes processes and skills to establish the enterprise function
To catch errors in a project architecture early
To guide decision making throughout the enterprise
To highlight shortfalls between the baseline and target architectures
To mitigate risk when implementing an architecture project
To define the solution architecture needed to support the Application Architecture
To define technology components into a set of technology platforms
To define the Transition Architectures needed to achieve the Target Architecture
To select a set of technology products that will form the basis of a solution architecture
Architecture Requirements Specification
Statement of Architecture Work
Architecture Vision
Request for Architecture Work
Perform a Gap Analysis
Design a viewpoint to address all stakeholder concerns
Develop views for the target architecture first
Refer to the existing viewpoint library to determine if there is an existing viewpoint which can be re-used
Ensure that major stakeholders receive the correct information at the right time in the architecture cycle
During the Implementation Governance phase checks that delivery projects are meeting their requirements
Tracks the progress of implementation of Transition Architectures from Baseline to Target architecture
In the Architecture Change Management phase, it informs the Architecture Board of the status of delivery projects
A description of the scope and approach for completion of the architecture project
A set of rules and guidelines to support fulfilling the mission of the organisation
A set of quantitative statements outlining requirements on the implementation
A high-level description of how the new capability will address stakeholder concerns
Requirements Impact Analysis
Statement of Architecture Work
Compliance Assessment
Change Request
Part I
Part II
Part IV
Part VI
Baseline
Solution
Strategic
Target
Architecture Capability
Architecture Metamodel
Governance Log
Reference Library
This phase addresses and resolves requirements between the ADM phases
This phase is a central process which prioritises requirements for the other ADM phases
This phase is used to dispose of resolved requirements for all ADM phases
This phase stores requirements and manages their flow into the relevant ADM phases
Techniques support specific tasks within the ADM while Guidelines help to adapt the ADM to deal with different scenarios
Guidelines support specific tasks within the ADM while Techniques help to adapt the ADM to deal with different scenarios
Techniques describes a general set of rules and guidelines for the architecture being developed
Guidelines describe a generic step-by-step approach to developing an architecture
It is a detailed data model that can be tailored to specific industries
It is an example of a Common Systems Architecture
It is a foundation architecture upon which more specific architectures can be based
It is a model of application components and application services software, including brokering applications
Phase D
Phase E
Phase F
Phase G