Module 1: Key Changes in the TOGAF® Standard
The TOGAF® Document Set
The difference between the Fundamental Content and the TOGAF® Series Guides
Describe how the TOGAF® Fundamental Content and the TOGAF® Series Guides together form the TOGAF® Standard
How the structure of the TOGAF® Standard reflects the structure and content of an Architecture Capability within an Enterprise
TOGAF® Series Guides and their Applicability
Guidance available to the person tasked to lead the effort to establish or evolve an Enterprise Architecture Capability
The TOGAF® Library
How Enterprise Architecture services can be provided through a Service Delivery Model
Architecture Alternatives and Trade-off
Module 2 – Introducing the Context for Enterprise Architecture
Guiding Effective Change: The Purpose of Enterprise Architecture
What does an Enterprise Architecture look like?
Architecture Governance and the role of an Enterprise Architect
The Iterative Nature of the Architecture Development Method (ADM)
The Four Contexts of Organizational Evolution towards a Digital Enterprise as identified by the DPBoK™ Standard
Module 3 – Enterprise Architecture and the Practitioner Role
How an Architecture enables alignment to Organizational Objectives using Agile development as an example
How the TOGAF® Standard can be applied to support the Digital Enterprise
The Role of the Enterprise Architect and Enterprise Architecture in a Digital Enterprise
Module 4 – Applying TOGAF® Concepts in the Context for Enterprise Architecture
Guiding effective change: the Purpose of Enterprise Architecture
What an Enterprise Architecture looks like
Architecture Capability
The need to manage Multiple Architecture States
Enterprise Security Architecture
Security, a Cross-Cutting Concern
Managing the uncertainty of the success of change to optimize maximum business benefit and minimum business loss
Module 5 – Stakeholder Management
How to identify Stakeholders, their Concerns, Views, and the Communication involved
The use of Architecture Views
Stakeholder Engagement and Requirements Management
Using Trade-off to Support Architecture Development
Module 6 – Phase A, the Starting Point
Identifying the information necessary to execute the Architecture Vision phase, and how iteration cycles provide more information to take into account in order to execute the phase
How to execute Phase A and how it contributes to the Architecture Development
Security-specific Architecture Design that is Sufficient — Phase A
Outputs necessary to proceed with the Architecture Development
Module 7 – Architecture Development
Steps applicable to all ADM Phases
Risk and Security considerations during the Architecture Development (ADM Phases B to D)
Relevant Information to produce outputs valuable to the Architecture Development
How to apply Phase B and how it contributes to the Architecture Development work
Information that is relevant to Phase C (Data and Applications) to produce outputs relevant to the Architecture Development
How to apply Phase C and how it contributes to the Architecture Development work
Information needed in Phase D to produce outputs relevant to the Architecture Development
How to apply Phase D and how it contributes to the Architecture Development work
Outputs of Phases B, C, and D necessary to proceed with the Architecture Development work
Module 8 – Implementing the Architecture
Risk and Security considerations for Phases E, F, and G
Steps (Phase E) to create the Implementation and Migration Strategy
Basic Approaches to Implementation
How to identify and group Work Packages
How to create and document Transition Architectures
The impact of the Migration Projects on the Organization and the Coordination required
Why and how Business Value is assigned to each Work Package
How to prioritize the Migration Projects (Phase F)
Confirm the Architecture Roadmap (Phase F)
Outputs of Phase F necessary to proceed with the Architecture Implementation
Inputs to Phase G Implementation Governance
How Implementation Governance is executed (Phase G)
Outputs necessary to support Architecture Governance
How Architecture Contracts are used to communicate with Implementers
Module 9 – Supporting the ADM Work
How The Open Group TOGAF® Library can be used to support the Practitioner’s Work
Business Scenarios
The purpose of Compliance Assessments
How Migration Planning techniques are used to review and consolidate the Gap Analysis results from earlier Phases
How a Repository can be structured using the TOGAF® Architecture Repository as an example
What to expect in a well-run Architecture Repository
How the concepts of Architecture Levels are used to organize the Architecture Landscape
Different Levels of Architecture that exist in an organization
Determining the Level an Architecture is being developed at
The Role of Architecture Building Blocks (ABBs)
