OGEA-103: TOGAF Enterprise Architecture Combined Part 1 and Part 2 ExamDemo

The Preliminary Phase includes establishing the Enterprise Architecture Capability. Phase G, Implementation Governance, provides architectural oversight during implementation to ensure conformance with the architecture.

Improving resilience to ransomware requires architecture change management across the enterprise: establish the business-continuity requirements, assess gaps in the current architecture, define the necessary changes, and submit them for Architecture Board governance. When the change requires further architecture development, an approved change request leads to a new Request for Architecture Work and an ADM cycle to define and deliver the changed architecture.

The Solutions Landscape contains planned or deployed solution building blocks and is associated with delivering business outcomes. The Architecture Requirements Repository holds authorized architecture requirements that drive enterprise architecture work. The Architecture Landscape represents enterprise assets in use or planned, is structured according to the architecture metamodel, governed, and assessed for standards compliance.

The ADM classifies documents that have not yet completed formal review and approval as draft documents. Version 0.1 may be used for an early architectural outline in an ADM version-numbering convention, but it is not the general status designation for all unreviewed documents.

The Architecture Trade-off Method uses the architecture vision, principles, requirements, and other information to establish evaluation criteria, define architecture alternatives, and select one alternative—or combine features of several alternatives—after considering the trade-offs.

An EA Capability provides the organizational ability to carry out enterprise architecture activity effectively, including the necessary structures, roles, responsibilities, skills, and processes.

This table corresponds to TOGAF ADM Phase G, Implementation Governance. Phase G's purpose is to provide architectural oversight of the implementation, ensuring that implementation projects conform to the Target Architecture and that appropriate governance functions are performed for the solution and any implementation-driven architecture change requests. Its output/outcome is the completion of the projects that implement the changes needed to reach the (possibly adjusted) target state, governed through signed Architecture Contracts, compliance assessments, and change requests. The essential knowledge for this phase includes understanding the purpose and constraints placed on the implementation team — drawn from gap analysis results, the Architecture Requirements Specification, and governance controls — as well as understanding how stakeholder priority and preference shift in response to the success, value, effort, and risk associated with the change, which enterprise architects must track to help stakeholders decide how to respond when an implementation project underperforms or drifts from the architecture.

TOGAF ADM Phase A identifies stakeholders, their concerns, and the business requirements that the architecture must address. Business scenarios can be used to discover and document those requirements, while stakeholder analysis identifies the relevant people and concerns. This work supports the initial high-level descriptions of the baseline and target architectures before detailed architecture development begins.

A stakeholder is a person, group, or organization that has an interest in or concern about a system or architecture.

TOGAF ADM Phase E, Opportunities and Solutions, consolidates architecture gaps into work packages and evaluates their value, effort, risk, and dependencies in order to reach the adjusted target architecture. Phase F turns the selected approach into an approved implementation and migration plan of projects.

Enterprise Architecture provides a structured, organization-wide view that aligns business and technology so that change can be planned and carried out effectively.

A business scenario describes a business problem and the business and technology environment in which that problem occurs.

Phase E, Opportunities and Solutions, establishes the incremental delivery approach, identifies Transition Architectures that deliver continuing business value, and creates the initial Architecture Roadmap using the gap analysis and candidate components from Phases B, C, and D. Phase F, Migration Planning, finalizes that roadmap and its Implementation and Migration Plan, while ensuring that stakeholders understand the value and cost of work packages and Transition Architectures.

TOGAF uses stakeholder analysis to identify stakeholders and their concerns, then defines relevant views to demonstrate how the architecture addresses those concerns. The Architecture Vision records the high-level outcomes and stakeholder concerns early in the ADM. Treating risk mitigation as an ongoing requirement with regular assessments supports governance of AI-related risks while enabling iterative, supervised implementation of continuous machine learning.

A Business Scenario is a technique for developing a business model that describes a business problem or opportunity and its needs in a structured way.

In the TOGAF Architecture Principles template, the Rationale section states the business justification for a principle and highlights the business benefits of adhering to it, using business terminology.

Architecture partitioning divides Enterprise Architecture into manageable segments, simplifying its development and management while supporting governance and ownership. It is distinct from architecture levels and is not defined specifically for agile Enterprise Architecture teams.

Phase A (Architecture Vision) identifies stakeholders and their concerns so that the architecture vision, scope, and high-level requirements can be agreed. Enterprise Architecture Capability is established in the Preliminary Phase, while target architectures are developed in the subsequent Business, Information Systems, and Technology Architecture phases.

Enterprise Architecture governance provides the decision rights, oversight, and controls needed to ensure that architectural work and implementation deliver the intended organizational value. Best-practice governance therefore enables the organization to control value realization.

TOGAF migration planning uses the Consolidated Gaps, Solutions, and Dependencies Matrix as a planning tool for creating work packages. Proposed solutions are classified as new development, purchased solutions, or existing products, and similar solutions are grouped into work packages. The work packages are regrouped into Capability Increments and scheduled as Transition Architectures while accounting for implementation constraints such as clinical-trial schedules. The Architecture Definition Increments Table documents the incremental transition plan.

An Architecture Board oversees the implementation of the Architecture Governance strategy across the enterprise, providing governance and direction for architecture activities.

The TOGAF ADM is iterative rather than a strictly sequential process. Requirements Management is continuous across the ADM, and iteration permits later phases to revise deliverables produced earlier. Starting a new phase does not require the preceding phase to be closed permanently.

Phase B develops the Business Architecture that supports the agreed Architecture Vision. Its work includes establishing the architecture for the business domain, obtaining stakeholder review and approval, identifying gaps between baseline and target states, and defining candidate roadmap work to address those gaps.

In the TOGAF ADM, Phase F—Migration Planning addresses stakeholders’ understanding of the value and cost of work packages and Transition Architectures. Phase G—Implementation Governance ensures implementation-project conformance with the Target Architecture. Phase H—Architecture Change Management maintains the architecture development cycle and executes the Architecture Governance Framework.