OG0-091 Sample Questions Answers

Architecture Capability

Architecture Landscape

Architecture Metamodel

Governance Log

Reference Library

Defining the Strategic Business Plan

Describing the Baseline Business Architecture

Developing the Target Business Architecture

Selecting relevant viewpoints for key stakeholders

A checklist for compliance reviews

An evaluation tool to select vendors to conduct a proof of concept demonstration

A tool for calculating detailed cost estimates

A tool for project planning the implementation activities

A tool for selling the benefits of the proposed capability to stakeholders

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 develop a migration plan to deliver incremental capabilities

To select a set of technology products that will form the basis of a solution architecture

To create a roadmap that describes the evolution of the architecture over time

To prepare a Solution Architecture for the enterprise

To define an IT Strategy that maps out the technology infrastructure

To allocate the resources needed to implement the architecture project

To articulate an Architecture Vision

A document that triggers the start of an architecture development cycle

A qualitative view of the solution to communicate the intent of the architect

A quantitative view of the solution to measure the implementation

A record of deviations from the planned architectural approach

Risk analysis is best conducted in the Architecture Vision phase so that the risk is eliminated in subsequent phases

Risk analysis should be carried out first in the Migration Planning phase

Risk analysis is outside the scope of enterprise architecture projects

Risk is pervasive in all enterprise architecture activity and should be managed in all phases of the ADM

The only risks that are within the scope of enterprise architecture are technological risks

TOGAF Guidelines and Techniques

TOGAF Recommended

TOGAF Supporting

TOGAF Extension

They are a package of functionality intended to meet the business needs across the organization

They should have stable, published interfaces that allow other building blocks to interoperate with them

They are equivalent to software component objects or web services

They may have multiple implementations but with different, interdependent Building Blocks

They may be assembled from other Building Blocks

Rational, Explained, Precise, Stated, Identifiable

Comprehensive, Future proof, Short, Concise, Consistent

Open, Enabling, Flexible, Agile, Dynamic

Stable, Understandable, Complete, Robust, Consistent

Configuration Database

library of architecture artifacts

Requirements Management System

Standards Information Base

view of the Architecture Repository

Authoring the Architecture Definition Document

Ensuring the compliance of individual projects to the enterprise architecture

Controlling the implementation and deployment organizations

Authoring the Communications Plan for a given architecture project

Conducting Business Scenarios

Name

Statement of Principle

Rationale

Enforcement Policy

Implications

An artifact contains one or more deliverables

Artifacts and deliverables are synonymous; there is no difference between them

Deliverables are prepared by the Project Manager, whereas artifacts are defined by the Architect

Deliverables are reusable, whereas artifacts are unique to a given architecture project

Deliverables are specified as contractual outputs from a project, whereas artifacts are not

The TOGAF Architecture Development Method mandates the use of the Technical Reference Model for large complex architecture projects

The Technical Reference Model is an integral part of the TOGAF Architecture Development Method

The Technical Reference Model should not be modified

The Technical Reference Model includes a set of graphical models and a corresponding taxonomy

The Technical Reference Model provides a direct mapping to the Zachman Framework

Preliminary Phase

Phase A

Phase B

Phase H

Requirements Management Phase

Common Systems, Foundation, Industry, Organization-Specific

Organization-Specific, Industry, Foundation, Common Systems

Foundation, Common Systems, Industry, Organization-Specific

Industry, Foundation, Common Systems, Organization-Specific

Organization-Specific, Industry, Common Systems, Foundation

Application, Business, Data, Technology

Capability, Segment, Strategic

Context, Definition, Governance, Transformation

Definition, Realization, Transition, Vision

nonconformant solution building blocks

an error has occurred and the architecture must be re-evaluated

requirements have not been properly documented

functionality that should be eliminated

a new function that must be built or procured

a complete ADM cycle

a complete re-architecting change

a full revision of the enterprise architecture

an incremental change

a simplification change

Common Systems Architecture

Industry Specific Architecture

Foundation Solution

Organization Specific Solution

Technology Neutral Implementation

architecture building block

architecture model

architecture vision

requirement

viewpoint

They should not be reused in other enterprise architecture projects

They should have stable, published interfaces that allow other building block to interoperate with them

They are packages of functionality intended to meet the business needs across the organization

They have defined boundaries

Design a viewpoint to address all stakeholder concerns

Develop views for the target architecture first

Ensure completeness of the architecture

Refer to existing libraries of viewpoints, to identify one for re-use

An agreement between development partners and sponsors on the deliverables

A description to allow measurement of the compliance of the implementation

A description to communicate the intent of the architect

A document that triggers the start of an architecture development cycle

A set of general rules and guidelines

Foundation Architecture

Common Systems Architecture

Industry Architecture

Organization Specific Architecture

Product Line Architecture

Architecture governance

Business imperatives

Solution architecture

Service level agreements

Time horizon

The Architecture Repository

The Enterprise Continuum

The Integrated Information Infrastructure Model

The TOGAF Technical Reference Model

Architecture Maturity Models

Business Scenarios

Gap Analysis

Mind Maps

SWOT Analysis

establish quality parameters for the architecture

identify potential missing or overlapping functions

validate nonfunctional requirements

identify commercial building blocks to be purchased

determine the required service levels for the architecture

Architecture Domains

Enterprise Focus

Level of Detail

Subject Matter

Time Period

Enterprise Architecture Capability

IT Governing Board

Program Management Office

Quality Assurance department

Service Management department

To define the Baseline Architecture for this cycle of the ADM

To define the application systems for the Target Architecture

To define the framework and methodologies to be used

To define the relevant stakeholders and their concerns

To define and prioritise work packages

Phase D

Phase E

Phase F

Phase G

Phase H

Application Architecture

Business Architecture

Data Architecture

Technology Architecture

It highlights areas of stakeholder concern

It highlights the impacts of change

It highlights services that are yet to be developed

It highlights services that are available

It highlights different viewpoints

observations of the CIO/CTO

opinions of the sponsors

observations of the architect staff

concerns of stakeholders

stakeholder requirements

A business planning technique that focuses on business outcomes

A business planning technique that focuses on horizontal capabilities

A business planning technique that focuses on vertical capabilities

A human resource planning technique that focuses on capable architects

Business requirements

Cultural aspirations

Forecast financial requirements

Strategic Intent

Technical elegance

Requirements Management

Phase E

Phase F

Phase G

Phase H

Addressing requirements

Disposal of resolved requirements

Generating requirements

Managing the flow of requirements

Prioritizing requirements

To ensure that architecture information is communicated to the right stakeholders at the right time

To evangelize the architecture to the end user community

To govern the architecture through to implementation

To keep the Architecture Review Board informed of changes to the architecture

To show progression of change from the Baseline Architecture to the Target Architecture

Creating the Architecture Vision deliverable

Defining a set of Architecture Principles

Developing an Architecture Contract

Extending the business scenario with business modeling

Preparing a consolidated Gap Analysis

TOGAF Reference Models

Architecture Content Framework

Architecture Capability Framework

Enterprise Continuum & Tools

Architecture Development Method

consumer

CxOs

lead architect

sponsor

stakeholder

To create an implementation and migration strategy

To establish an architecture change management process

To priorities work packages and projects

To validate the business principles, goals, drivers and key performance indicators

ADM Guidelines and Techniques

Architecture Capability Framework

Architecture Content Framework

Architecture Development Method

Enterprise Continuum & Tools

is used to store different classes of architectural output created by the ADM

is a categorisation mechanism for classifying architecture and solution artifacts

is a detailed model of architectural work products, including deliverables and artifacts

is an architecture of generic functions and services

is a set of resources to help establish an architecture capability within an organization

robustness

consistency

completeness

stability

understandability

To coordinate with the other management frameworks in use

To describe how an architecture addresses stakeholder concerns

To identify and understand business requirements

To provide a system for continuous monitoring

To structure re-usable architecture and solution assets

Requirements

Principles

Concerns

Architecture viewpoints

Architecture views

A detailed description of the interfaces between building blocks

An implementation specific solution building block

A package of functionality defined to meet the business needs of the organization.

A way to put building blocks together into context

A work product describing an aspect of an architecture

Phase A

Phase E

Phase F

Phase G

Phase H

Phase H

Phase F

Phase E

Preliminary Phase

Phase G

Common Systems Solutions, Organization-Specific Solutions and Industry Solutions

Catalogs, Matrices and Diagrams

Artifacts, Best Practices and Standards

Audit Information, Process Status and Reference Data

Capability, Segment, and Transition Architectures

It is used to develop requirements for Transition Architectures that deliver business value

It is used to dispose of, address and prioritize architecture requirements

It is used to establish requirements for Phase A

It is used to manage architecture requirements throughout the ADM cycle

It is used to review business requirements

Opportunities and Solutions

Business Architecture

Data Architecture

Architecture Vision

Technology Architecture

Phase A

Phase B

Phase C

Phase D

Phase E

Phases E and F

Preliminary Phase

Phase B, C, and D

Phase G and H

Phase A

A change driven by a requirement to derive additional value from the existing investment

A change driven by a requirement to increase investment in order to create new value for exploitation

A change driven by a requirement to reduce investment

A change driven by a requirement to re-align with the business strategy

A change driven by a requirement to derive additional value from the existing investment

A change driven by a requirement to increase investment in order to create new value for exploitation

A change driven by a requirement to reduce costs

A change driven by a requirement to reduce investment

A change driven by a requirement to re-align with the business strategy

Foundation, Common and Solution Architectures

Business, Data, Applications and Technology Architectures

Capability, Segment and Strategic Architectures

Corporate EA, Project Team and Portfolio Team Architectures

Baseline, Transition and Target Architectures

Business Transformation Readiness Assessment

Business Value Assessment Technique

Capability-Based Planning

Communications and Stakeholder Management

Gap Analysis

Critical

Initial

Intermediate

Residual

Unmitigated

Identifying business transformation risks for an architecture project

Identifying errors in the project architecture

Identifying relationships between management frameworks

Identifying stakeholders and their concerns

It provides for effective communication of the end architecture project to the stakeholders

It is sent from the sponsor and triggers the start of an architecture development cycle

It contains an assessment of the current architecture requirements

It lists work packages on a timeline showing progress towards the Target Architecture

It forms the basis of a contractual agreement between the sponsor and the architecture organization

Procurement policies

Business scenarios

Functional Requirements

Stakeholder concerns

Architecture principles

Implications

Name

Rationale

Statement

Resolve impacts across the Architecture Landscape

Define candidate roadmap components

Conduct formal stakeholder review

Create Architecture Definition Document

Develop Architecture Definition Document

Develop Baseline Architecture

Conduct formal stakeholder review

Create Architecture Definition Document

Define Roadmap components

Perform gap analysis

Select reference models, viewpoints and tools

Industry Architecture

Foundation Architecture

Transition Architecture

Common Systems Architecture

Organization-Specific Architecture

The Capability Maturity Model

The Document Categorization Model

The Integrated Infrastructure Information Model

The Organizational Model for Enterprise Architecture

The Technical Reference Model

A change to re-align with the business strategy.

A change to derive additional value from the existing investment.

A change to reduce costs.

A change to increase investment in order to create new value for exploitation.

Develop a vision of the proposed enterprise architecture

Document the baseline architecture

Obtain approval for the Statement of Architecture Work

Operate the governance framework

Select and implement tools

A repository area that lists the set of specifications to which architectures must conform

A repository area that describes the organization specific architecture framework and method.

A repository area that defines the parameters, structures, and processes to support governance

A repository area that provides guidelines, templates, and patterns used to create new architectures

A repository area that provides a record of the governance activity across the enterprise

assess the performance of the architecture and make recommendations for change

ensure the baseline architecture continues to be fit-for-purpose

ensure conformance with the defined architecture by the implementation projects

establish an architecture change management process for the architecture finalized in the previous ADM phase

operate the governance framework

Foundation Architectures to re-usable architecture assets

generic architectures to Oganization-Specific Architectures

generic solutions to Industry Models

generic architectures to reusable Solution Building Blocks

Solutions Architectures to Solution Building Blocks

To confirm the ability of the enterprise to undergo change

To demonstrate how stakeholder concerns are addressed in the Business Architecture

To develop a Target Technology Architecture to support the business

To finalize the Architecture Vision and Architecture Definition documents

To maximize the business value from the architecture

It contains only solution building blocks

It contains business functions and processes specific to a particular industry sector

It contains building blocks and their corresponding standards

It includes a model of application components and application services software, including brokering applications

It includes models for common high-level business functions, such as supply chain management

Enabling the vision of an integrated information infrastructure

Getting information to the right people at the right time in a secure, reliable and timely manner

Enabling effective global communications between countries

Enabling the flow of information to all stakeholders

Providing a visual representation of information provider, consumer and brokering applications

Architecture governance

Corporate governance

IT governance

Portfolio management

Technology governance

Viewpoints

Concerns

Requirements

Principles

Views

Interview the project principals to obtain background information

Prepare the Architecture Compliance Review report

Schedule the Architecture Review meeting

Send the assessment report to the Architecture Review co-ordinator

Tailor the checklists to address business requirements

To catch errors in a project architecture early

To guide decision making throughout the enterprise

To help identify and understand business requirements

To highlight shortfalls between the baseline and target architectures

To mitigate risk when implementing an architecture project

identifies services to be shared

focuses on business outcomes

ensures business information is communicated to the right people at the right time

ensures the application of business best practices

ensures timely solutions