Free Practice Questions for The Open Group OGEA-101 Exam

According to the TOGAF standard, the deliverables that match the descriptions are as follows:

1 Architecture Principles: These are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission1. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions1.

2 Architecture Contracts: These are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture2. They are used to ensure that the architecture is implemented and governed according to the agreed-upon specifications and standards2.

3 Request for Architecture Work: This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle3. It defines the scope, schedule, budget, deliverables, and stakeholders of the architecture project3.

4 Architecture Requirements Specification: This is a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture4. It defines the requirements for each architecture domain, as well as the relationships and dependencies among them4.

 1: Architecture Principles 2: Architecture Contracts 3: Request for Architecture Work 4: Architecture Requirements Specification

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

Phase A: Architecture Vision is the first phase of the Architecture Development Method (ADM) cycle, which is the core of the TOGAF standard. The main purpose of this phase is to define the scope and approach of the architecture development, and to create the Architecture Vision, which is a high-level description of the desired outcomes and benefits of the proposed architecture. To achieve this purpose, this phase focuses on defining the problem to be solved, identifying the stakeholders, their concerns, and requirements, and establishing the business goals and drivers that motivate the architecture work. This phase also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process.

The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 5: Introduction to the ADM : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18.3: Inputs : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18.4: Steps

According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system from the perspective of a related set of concerns1. It consists of one or more architecture models that demonstrate how the system addresses the stakeholder concerns1.

An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1. It defines the perspective, scope, notation, and techniques for creating an architecture view of a system1.

Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture, because23:

Architecture views and viewpoints help to communicate and visualize the architecture in a way that is meaningful and relevant to different stakeholders, addressing their specific interests and needs.

Architecture views and viewpoints help to elicit and validate the stakeholder concerns and requirements, ensuring that they are aligned with the business goals and objectives, and that they are consistent and feasible within the architecture context.

Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs among the stakeholder concerns and requirements, ensuring that they are balanced and prioritized in the architecture design and decision-making.

Architecture views and viewpoints help to demonstrate and verify the value and benefits of the architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture outcome and governance.

1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders

2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an Architecture Framework?

3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section 31.1: Basic Concepts

Phase F: Migration Planning – Objectives/Outputs include:

“The outputs for this phase: … Finalized Architecture Roadmap … Implementation and Migration Plan … projects assigned business value and risk.”

“To prioritize all work packages… by assigning business value to each and conducting a cost/business analysis.” Open Group Publications

When considering agile development, Architecture to Support Project will identify what products the enterprise needs, the boundary of the products, and what constraints a product owner has. This defines the enterprise’s backlog. A backlog is a list of features or tasks that need to be done to deliver a product or service. It is prioritized by the product owner based on the value and urgency of each item. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.5 Architecture to Support Project.

The Implementation Governance Model is a framework that defines the roles, responsibilities, processes, and standards for governing the implementation of the target architecture. It ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance, which is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. The Implementation Governance Model is part of the Implementation and Migration Plan, which is the output of Phase F: Migration Planning of the Architecture Development Method (ADM)12 References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance

According to the TOGAF standard, the need for the ADM process to be governed is to ensure that the architecture development and implementation activities are conducted in a consistent, coherent, and compliant manner1. Governance provides the means to verify that the method is being applied correctly and effectively, and that the architecture deliverables and artifacts meet the quality and standards criteria1. Governance also enables the management of risks, issues, changes, and dependencies that may arise during the ADM process1.

Some of the benefits of governing the ADM process are2:

•Improved alignment of the architecture with the business strategy and objectives

•Enhanced stakeholder engagement and communication

•Increased reuse and integration of architecture assets and resources

•Reduced complexity and duplication of architecture efforts

•Increased agility and adaptability of the architecture to changing needs and requirements

•Improved compliance and auditability of the architecture outcomes and outputs

The Architecture Landscape is a class of information within the Architecture Repository that shows an architectural view of the building blocks that are in use within the organization today (the Baseline Architecture), as well as those that are planned for the future (the Target Architecture). The Architecture Landscape typically contains a list of the applications in use within the enterprise, along with their relationships and dependencies, as well as other relevant architectural information. The Architecture Landscape helps to identify opportunities for re-use, consolidation, or retirement of existing applications, as well as gaps or overlaps in the current or future architecture.

The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 34: Architecture Landscape : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 47: Architecture Repository