OG0-091 TOGAF 9 Part 1 Questions and Answers

Common Systems Solutions

Strategic Solutions

Industry Solutions

Organization-Specific Solutions

Foundation Solutions

To create the initial version of the Architecture Roadmap

To develop a vision of the business value to be delivered by the proposed enterprise architecture

To select and implement tools to support the Architecture Capability

To obtain approval for the Statement of Architecture Work

To document the baseline architecture

The categorization after implementation of mitigating actions

The categorization after initial risk assessment

The categorization after mitigation and residual risk assessment

The categorization before determining and implementing mitigating actions

The categorization before risk identification

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

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

Architecture Contract

Architecture Landscape

Architecture Roadmap

Requirements Impact Statement

Transition Architecture

Architecture Maturity Models

Business Scenarios

Gap Analysis

Mind Maps

SWOT Analysis

Architecture Contract

Architecture Definition Document

Architecture Vision

Request for Architecture Work

Statement of Architecture Work

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

To determine if the organization is ready to undergo change

To determine if the stakeholders support the implementation plan

To ensure that there are adequate trained engineers to develop the solution

To ensure that there is sufficient funding to execute the transformation

To plan the migration steps needed to achieve the transformation

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

A description of the organization specific architecture framework and method

A record of the governance activity across the enterprise

Guidelines and templates used to create new architectures

Processes to support governance of the Architecture Repository

Specifications to which architectures must conform

Enterprise Architecture Capability

IT Governing Board

Program Management Office

Quality Assurance department

Service Management department

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

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

The ARTS data model

The Integrated Information Infrastructure Reference Model

The Resource-Event-Agent model

The STEP framework

The TOGAF Technical Reference Model

Phase D

Phase E

Phase F

Phase G

Phase H

Common Systems Architecture

Foundation Architecture

Industry Architecture

Organization Specific Architecture

Product Line Architecture

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

activity model, perspective

viewpoint, requirements

view, concerns

Node Connectivity Diagram, interconnections

Architecture trade-off analysis, constraints

TOGAF Core

TOGAF Extension

TOGAF Mandatory

TOGAF Recommended

TOGAF Supporting

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

determining if the organization is ready to accept change

planning the migration steps needed to achieve the transformation

ensuring that there are adequate trained developers and engineers to implement the solution

ensuring that there is sufficient financial capacity to execute the desired transformation

determining if there is adequate stakeholder support for the implementation process

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

addresses and resolves requirements between ADM phases

is a central process that prioritizes requirements for all ADM phases

is used to dispose of resolved requirements for all ADM phases

generates new requirements and passes them to all ADM phases

stores requirements and manages their flow into relevant ADM phases

Architecture Landscape

Architecture Vision

Enterprise Continuum

Governance Log

Standards Information Base

determining the technical readiness of a project

ensuring the application of best practices

identifying business transformation risks for an architecture project

identifying errors in an architecture project

identifying where architecture standards require modification

To allocate the resources needed to implement the architecture project

To define the framework that is going to be used to develop the enterprise architecture

To define an IT Strategy that maps out the technology infrastructure

To prepare a Solution Architecture for the enterprise

To secure formal approval to proceed

TOGAF Core

TOGAF Mandated

TOGAF Recommended

TOGAF Referenced

TOGAF Supporting

It contains a high level description of the business strategy for the organization

It is the key document describing how the new architecture capability will meet the business goals

It provides prerequisite knowledge for undertaking work in the other architecture domains

It mobilizes operations to support the ongoing business architecture development

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

activity model, perspective

business scenario, requirements

use case, interconnections

view, concerns

business transformation readiness assessment, constraints

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

Develop the Architecture Vision document

Draft the Implementation and Migration Plan

Ensure conformance requirements for the target architecture are defined

Establish the Organizational Model for enterprise architecture

Operate the governance framework

Building Block

Catalog

Diagram

Matrix

Deliverable

A good Building Block should not be composed of other Building Blocks

Architecture Building Blocks should be first selected in Phase D

Building Block specifications should be loosely coupled to implementation

Custom developments are known as Architecture Building Blocks

Develop an Architecture Roadmap

Populate the Architecture Repository

Populate the Enterprise Continuum

Use the Architecture Development Method

Use the Implementation Governance Phase

Allocating resources for architecture projects

Decision making for changes in the architecture

Enforcing Architecture Compliance

Improving the maturity of the organization ' s architecture discipline

Production of governance materials

To review the validity of a project ' s Architecture Vision

To review a project for compliance to external laws and regulations

To review a project against established architecture criteria and business objectives

To ensure that stakeholder concerns are being addressed by a project

observations of the CIO/CTO

opinions of the sponsors

observations of the architect staff

concerns of stakeholders

stakeholder requirements

Addressing requirements

Disposal of resolved requirements

Generating requirements

Managing the flow of requirements

Prioritizing requirements

Architecture Capability Framework

Architecture Continuum

Architecture Development Method

Architecture Landscape

Architecture Repository

TOGAF Guidelines and Techniques

TOGAF Recommended

TOGAF Supporting

TOGAF Extension

Architecture

Metamodel

Model

Ontology

Pattern

To define the capabilities of the organization

To communicate the technical readiness of the project

To evaluate the readiness of the organization to undergo change

To produce a new Request for Architecture Work

Foundation Architecture

Common Systems Architecture

Industry Architecture

Organization Specific Architecture

Product Line Architecture

architecture building block

architecture model

architecture vision

requirement

viewpoint

A bottom-up change to enhance operational capability

An incremental change handled via change management techniques

A re-architecting change that puts the whole architecture through an ADM cycle

A revision change of the enterprise architecture

A simplification change handled via change management techniques

Phase D

Phase E

Phase F

Phase G

Phase H

Part II: Architecture Development Method

Part III: ADM Guidelines and Techniques

Part IV: Architecture Content Framework

Part VI: TOGAF Reference Models

Part VII: Architecture Capability Framework

The organization must utilize an architecture tool in order to tailor the templates for use

It must be adapted to satisfy organization specific requirements

It can be utilized by most enterprises without further customization

It can only be used for enterprise level architecture projects

It should only be employed under the supervision of highly trained consultants

Defining an architecture that can be understood by the stakeholders

Defining an architecture that is complete and consistent

Defining an architecture that is stable

Defining data entities that are normalized to minimize update anomalies

Defining data entities relevant to the enterprise

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

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

They are most effective when they are embraced and used across the organization

They are based on enterprise principles

They are detailed policies that prescribe behaviors and requirements

Even though they may appear generic, they should be tailored to reflect an organization ' s culture and goals

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

To show the evolution of deliverables

To permit adaptation as required

To enable use with the Architecture Content Framework

To support change management

Content

Context

Process Flow Control

Repository

Vision

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

Phase A: Architecture Vision

Phase D: Technology Architecture

Phase F: Migration Planning

Phase E: Opportunities and Solutions

Phase B: Business Architecture

Existing application models

Generic business models relevant to the organization’s industry sector

Existing IT services

Generic data models relevant to the organization’s industry sector

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

A repository area holding a description of the organization specific architecture framework and method

A repository area holding a record of the governance activity across the enterprise

A repository area holding guidelines and templates used to create new architectures

A repository area holding processes to support governance of the Architecture Repository

A repository area holding specifications to which architectures must conform

Procurement policies

Business scenarios

Functional Requirements

Stakeholder concerns

Architecture principles

An abstract framework for the development of standards and processes for a business architecture

A collection of components organized to accomplish a specific set of functions

A process model, best practices and assets to aid production, use and maintenance of enterprise architectures

A reference model containing taxonomy defining terminology for an enterprise architecture, together with an associated graphic

A system development lifecycle method for software engineering

Business Scenarios

Gap Analysis

Interoperability Analysis

Requirements Management

Architecture Principles

All requirements fed into the phase are prioritized, and those of low priority are deferred until the next iteration of the ADM cycle

The phase generates the requirements for a given ADM cycle using the Business Scenario technique

The phase manages the flow of requirements, storing them, and feeding them in and out of the relevant ADM phases

The phase operates like a waiting room, and all requirements fed in to the phase must be resolved by the end of the current ADM cycle

The phase resolves the requirements that are fed into it from the other ADM phases

Building blocks at a functional level are known as Solutions Building Blocks

Solutions Building Blocks are selected in Phases A, B, C and D

The specification of a building block should be loosely coupled to its implementation

The gap analysis technique should be used to identify building blocks for re-use

Parameters, structures, and processes to support governance of the repository

Specifications to which architectures must conform

The organization specific architecture framework, including a method for architecture development and a metamodel for architecture content

A record of the governance activity across the enterprise

Patterns, templates, and guidelines used to create new architectures

Architecture Repository

Architecture Requirements

Implementation and Migration plan

Standards Information Base

Strategic Architecture

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

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

ADM Guidelines and Techniques

Architecture Capability Framework

Architecture Content Framework

Architecture Development Method

Enterprise Continuum & Tools

Ensuring consistency between sub-architectures

Ensuring flexibility of the enterprise architecture to meet business needs

Improving the maturity of the organization ' s architecture discipline

Monitoring of architecture contracts

Preparing architecture review reports

Application Architecture should be developed first, then Data Architecture

Application Architecture should be developed concurrently with Data Architecture

Data Architecture should be developed first, then Application Architecture

Application Architecture and Data Architecture may be developed in either sequence

Catalog

Matrix

Diagram

View

Viewpoint

Phases E and F

Preliminary Phase

Phase B, C, and D

Phase G and H

Phase A

Identifying business transformation risks for an architecture project

Identifying errors in the project architecture

Identifying relationships between management frameworks

Identifying stakeholders and their concerns

Architecture principles

Business scenarios

Business Transformation Readiness Assessment

Capability-based planning

Gap analysis

Phase A

Phase F

Phase D

Phase G

Phase E

Industry Architecture

Foundation Architecture

Transition Architecture

Common Systems Architecture

Organization-Specific Architecture

A high-level outline architecture

A formally reviewed, preliminary architecture

A draft, detailed architecture

A formally reviewed, detailed architecture

A preliminary outline architecture

Architecture Road map

Architecture Requirements Specification

Communications Plan

Implementation and Migration Plan

Implementation Governance Model

viewpoint, views

viewpoint, stakeholders

view, concerns

view, stakeholders

view, requirements