The Open Group OGEA-101 - TOGAF Enterprise Architecture Part 1 Exam (English)

Risk Management is the process of identifying, assessing, and responding to risks that may affect the achievement of the enterprise’s objectives. Risk Management involves balancing positive and negative outcomes resulting from the realization of either opportunities or threats. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.3 Risk Management.

The Architecture Requirements Specification is one of the TOGAF deliverables that provides a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture12. It is a companion to the Architecture Definition Document, which provides a qualitative view of the solution and aims to communicate the intent of the architect. The Architecture Requirements Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture3. It typically forms a major component of an implementation contract or contract for more detailed Architecture Definition4. References:

•Deliverable: Architecture Requirements Specification - The Open Group

•Architecture Requirements Specification - Visual Paradigm Community Circle

•The TOGAF Standard, Version 9.2 - Definitions - The Open Group

•The TOGAF Standard, Version 9.2 - Architecture Requirements Specification - The Open Group

Ensuring compliance with internal and external standards and regulatory obligations is one of the activities included as part of Architecture Governance. Architecture Governance is the practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level. It involves establishing processes, roles, responsibilities, policies, and standards to ensure that architectures are aligned with the enterprise’s strategy and objectives, and meet the quality and performance requirements. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.6 Architecture Governance.

According to the TOGAF standard, the objectives of each ADM phase are as follows1:

•Phase E: Opportunities and Solutions

oDetermine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value

oIdentify and group major work packages within the Architecture Roadmap

oIdentify and group major implementation projects to realize the Architecture Roadmap

oIdentify dependencies between increments and projects

oEstimate cost, benefit, and risk at a high level for each increment and project

oConduct initial prioritization and sequencing of the Architecture Roadmap and projects

•Phase F: Migration Planning

oGenerate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D

oConfirm the Transition Architectures with relevant stakeholders

oCreate the Implementation and Migration Plan, including Transition Architectures, work packages, projects, and other activities

oConfirm and agree the Architecture Roadmap and Implementation and Migration Plan with relevant stakeholders

•Phase G: Implementation Governance

oFinalize the Architecture Roadmap and the supporting Implementation and Migration Plan

oEnsure conformance with the Target Architecture by implementation projects

oPerform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests

oEnsure that the architecture lifecycle is maintained

oEnsure that the Architecture Governance Framework is executed

•Phase H: Architecture Change Management

oEnsure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

oManage risks and issues related to the Architecture Roadmap and Implementation and Migration Plan

oMonitor the implementation projects and Transition Architectures

oManage changes to the architecture baseline

oManage changes to the Architecture Capability

Therefore, the correct matching of the objectives and the phases is:

•1G: Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value

•2E: Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D

•3F: Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan

•4F: Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization’s structure, which may change over time or differ from the architecture’s scope and boundaries. Reference: The TOGAF® Standard | The Open Group Website, Section 2.5 Architecture Partitioning.

Architecture Principles are general rules and guidelines that inform and support the way in which an organization sets about fulfilling its mission. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions. One of the purposes of Architecture Principles is to establish a common understanding of how to control the business in pursuit of strategic objectives, by providing a framework for evaluating and agreeing on the changes that affect the enterprise’s architecture3 References: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles : The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 31: Architecture Principles

Phase B of the ADM cycle is the Business Architecture phase. It describes the development of a Business Architecture to support an agreed Architecture Vision. The objectives of this phase are to describe the baseline and target Business Architecture, identify candidate Architecture Roadmap components based on gaps between the baseline and target, and determine whether an incremental approach is required. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.2 Phase B: Business Architecture.

According to the TOGAF Standard, 10th Edition, documents which are under development and have not undergone any formal review and approval process are called draft documents, while documents which have been reviewed and approved are called approved documents 1. Draft documents are typically marked with a version number of 0.x, indicating that they are incomplete or provisional. Approved documents are typically marked with a version number of 1.0 or higher, indicating that they have been finalized and authorized. The other options are not correct, as they are not the terms used by the TOGAF Standard to distinguish between documents under development and documents that have been reviewed and approved. The terms “finalized”, “concept”, “deliverable”, and “Version 0.1” and “Version 1.0” are not specific to the TOGAF Standard, and they may have different meanings or interpretations in different contexts. References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 7: Applying Iteration to the ADM, Section 7.2.3 Document Categorization.

The statement illustrates iteration and the ADM. Iteration is the technique of repeating a process or a phase with the aim of improving or refining the outcome. Iteration allows for feedback loops and adaptations at any point in the architecture development and transition process. Separate projects may operate their own ADM cycles concurrently, with relationships between the different projects, to address different aspects or levels of the architecture in an iterative manner. Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.

 In Phase E of the ADM cycle, building block gaps become associated with work packages that will address the gaps. This phase involves creating an Implementation and Migration Plan that defines a set of work packages and Transition Architectures that will deliver the Target Architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.5 Phase E: Opportunities & Solutions.