Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Togaf > Togaf > Flashcards

Togaf Flashcards

1
Q

Togaf 9.2 Document Structure

A 
Part I. Introduction
Part II. Architecture Development Method
Part III. ADM Guidelines and Techniques
Part IV. Architecture Content Framework
Part V. Enterprise Continuum and Tools
Part VI. Architecture Capability Framework
Part VII. Appendices
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

An Enterprise Architecture is …

A

An Architecture that crosses multiple systems, and multiple functional groups within the enterprise.

Can be applied to either an entire enterprise, encompassing all of its business activities and capabilities, information, and technology that make up the entire infrastructure and governance of the enterprise, or to one or more specific areas of interest within the enterprise.

1.3 page 6

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Difference between an artifact and a deliverable

A

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

29.1 page 271

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Main Components within the TOGAF Architecture Repository

A

At a high level, the following classes of architectural information are expected to be held within an Architecture Repository:

The Architecture Metamodel describes the organizationally tailored application of an architecture framework, including a method for architecture development and a metamodel for architecture content
The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository
The Architecture Landscape presents an architectural representation of assets in use, or planned, by the enterprise at particular points in time
The Standards Information Base captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization
The Reference Library provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise
The Governance Log provides a record of governance activity across the enterprise
The Architecture Requirements Repository provides a view of all authorized architecture requirements which have been agreed with the Architecture Board
The Solutions Landscape presents an architectural representation of the Solution Building Blocks (SBBs) supporting the Architecture Landscape which have been planned or deployed by the enterprise

37.1 page 391

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Why the ADM numbering scheme for versioning output is an example and not mandatory?

A

To permit adaptation as required

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Where should architecture governance artifacts be stored?

A

In the Architecture Repository

2.7 page 16

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Implications of TOGAF being a generic framework

A

It must be adapted to satisfy organisation specific requirements

2.10 page 20

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Which domain describes the logical software and hardware capabilities?

A

Technology Architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Which section of the TOGAF document describes the processes, skills and roles to establish and operate and architecture function within the enterprise

A

Part VI. Architecture Capability Framework

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is an architecture framework?

A

An architecture framework is a foundational structure, or a set of structures, which can be used for developing a broad range of different architectures. It should describe a method for designing a target state of the enterprise in terms of a set of building blocks, and for showing how the building blocks fit together. It should contain a set of tools and provide a common vocabulary. It should also include a list of recommended standards and compliant products that can be used to implement the building blocks.

1.3 page 8

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Classifies architecture assets that are applicable across the entire scope of the enterprise architecture.
Classifies contextual assets used to develop architectures, such as policies, standards, strategic initiatives, organizational structures, and enterprise-level capabilities. Can also classify solutions (as opposed to descriptions or specifications of solutions).

A

Enterprise Continuum

39.3

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

To promote effective architectural activity within the enterprise, TOGAF 9 recommends the establishment of …

A

Enterprise Architecture Capability

2.8 page 18

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

An Enterprise Architecture practice should establish capabilities in the following areas

A 
Financial Management
Performance Management
Service Management
Risk Management
Resource Management
Communications and Stakeholder Management
Quality Management
Supplier Management
Configuration Management
Environment Management
2.9 page 19
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Benefits of Architecture Governance

A

The benefits of Architecture Governance include:
Increased transparency and accountability and informed delegation of authority
Controlled risk management
Protection of the existing asset base through maximizing reuse of existing architectural components
Proactive control, monitoring and management mechanisms
Process, concept, and component re-use across all organizational business units
Value creation through monitoring, measuring, evaluation, and feedback
Increased visibility
Greater shareholder value
Integrates with existing processes

2.9 page 19

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Phase of the ADM used to finalize a set of transition architectures that will support implementation

A

Phase F

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

TOGAF 9.2 part III provides techniques, such as developing principles and gap analysis, to support tasks within the …

A

Architecture Development Method

17.2 page 175

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Recommended dimensions to define the scope of an architecture

A

Architecture Domains
Level of detail
Enterprise focus
Time Period

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Show a long-term summary view of the
entire enterprise.
Provide an organizing framework for
operational and change activity and allow for direction setting at an executive level.

A

Strategic Architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What part of Architecture Repository holds specifications to which architectures must conform?

A

Standards Information Base

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

An association of companies has defined a data model for sharing inventory and pricing information. Where this model would fit in the Architecture Continuum

A

Industry Architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Key objectives of Phase A of the TOGAF ADM

A

Develop a high level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture
Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What document is used to initiate ADM cycle

A

Request for Architecture Work

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Togaf defines 4 ADM iteration cycles (iterations)

A

Architecture Capability Iteration 0-A
Architecture Development Iteration B-D
Transition Planning Iteration E-F
Architecture Governance Iteration G-H

18.2 page 180

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Which of the following is the usual approach for developing the Baseline Business Architecture if no architecture of few architecture assets exists

A

Bottom up

7.3.2

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

First phase directly concerned with the planning of the implementation of the target architecture

A

Phase E

12.3.8 page 136

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

Phase which focuses on the governance and management of the Architecture Contracts that cover the overall implementation and deployment process

A

Phase G

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

A server consolidation project that does not change the operating characteristics of the application would require …

A

a simplification change

15.5.2 page 162

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Objective of the Preliminary Phase

A

To define the architecture principles

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

What drives the requirements and performance metrics when scoping the enterprise architecture work in the Preliminary Phase

A

Business imperatives

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Requirements Management Phase is responsible for

A

Managing the flow of requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

The Business Transformation Readiness Assessment is primarily focused on

A

determining if the organization is ready to accept change

Chapter 26 page 249

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

Architecture Principles

A

are a set of principles that relate to architecture work.
They reflect a level of consensus across the enterprise, and embody the spirit and thinking of existing enterprise principles.
Architecture principles govern the architecture process, affecting the development, maintenance, and use of the Enterprise Architecture.
Architecture principles may restate other enterprise guidance in terms and form that effectively guide architecture development.
Each Architecture principle should be clearly related back to the business objectives and key architecture drivers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

Architecture Principles template sections

A

Name
Statement or Principle
Rationale
Implications

20.3 page 198

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

Five Quality criteria for defining Architecture Principles

A

Stable, Understandable, Complete, Robust, Consistent

20.4.1 page 199

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

Gap analysis purpose

A

Identify potential missing or overlapping functions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

In a Gap Analysis a building block which appears in the Target Architecture but does not appear in the Baseline Architecture indicates

A

A new function that must be built or procured

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

Parts of the conceptual structure of the TOGAF Architecture Governance Framework

A 
Context
Process
Content
Repository
Process Flow Control

44.2.1 page 449

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

Architecture Board is responsible and accountable for …

A

ensuring consistency between sub-architectures
enforcement of architecture compliance
identifying and approving components for reuse
providing the basis for all decision-making with regard to the architectures
flexibility of the enterprise architecture
improving the maturity level of architecture discipline within the organization
….
41.2 page 413

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

Architecture compliance review purpose

A

To review a project against established architectural criteria, spirit, and business objectives.
Normally forms the core of an Enterprise Architecture Compliance strategy.
Catch errors in the project architecture early, reduce cost and risk of changes required later
Ensure application of best practices
Provide an overview of the compliance
Identify where the standards themselves may require modification
Identify services which are application-specific but might be provided as part of the enterprise infrastructure
Document strategies for collaboration, resource sharing, and other synergies
Take advantage of advances in technology
Communicate to management the status of technical readiness
Identify key criteria for procurement activities
Identify and communicate significant architectural gaps

42.3 page 421

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

TOGAF guidelines to use the ADM to establish an architecture capability

A

Use the same approach as with any other capability
Regard the establishment as an ongoing practice
Apply the ADM with the specific vision to establish the practice

40.1 p.407

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

Architecture

A
  1. The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution
  2. The structure of components, their inter-relationship, and the principles and guidelines governing their design and evolution over time

3.7 page 22

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
42
Q

Viewpoints represent

A

concerns of the stakeholders

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
43
Q

Building block (definition)

A

A (potentially re-usable) component of enterprise capability that can be combined with other building blocks to deliver architectures and solutions.
3.23 page 24

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
44
Q

Architecture Building Blocks vs Solution Building Blocks

A

Architecture building blocks define functionality where as Solution building blocks define the implementation of functionality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
45
Q

Purpose of Architecture Definition Document

A

The Architecture Definition Document is the deliverable container for the core architectural artifacts created during a project and for important related information. The Architecture Definition Document spans all architecture domains (business, data, application, and technology) and also examines all relevant states of the architecture (baseline, transition, and target).

A Transition Architecture shows the enterprise at an architecturally significant state between the Baseline and Target Architectures. Transition Architectures are used to describe transitional Target Architectures necessary for effective realization of the Target Architecture.

The Architecture Definition Document is a companion to the Architecture Requirements Specification, with a complementary objective:

  • The Architecture Definition Document provides a qualitative view of the solution and aims to communicate the intent of the architects
  • The Architecture Requirements Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture

A description to communicate the intent of the architect

32.2.3 page 352

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
46
Q

Who initiates a Request for Architecture Work

A

The sponsoring organization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
47
Q

Togaf Technical Reference Model

A

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

The TOGAF TRM is an example of a Foundation Architecture. It is a fundamental architecture
upon which other, more specific architectures can be based.

A Foundation Architecture consists of generic components, inter-relationships, principles, and
guidelines that provide a foundation on which more specific architectures can be built. The
TOGAF ADM is a process that would support specialization of such Foundation Architectures
in order to create organization-specific models.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
Q

Integrated Infrastructure Reference Model (III-RM) is an example of an

A

Application Architecture reference model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

Simplest way of thinking about Enterprise Continuum

A

View of the Architecture Repository

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
50
Q

Class of architectural information within the Architecture Repository that defines processes that support governance of the Architectural Repository

A

Architecture Capability

Chapter 39 page 434

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
51
Q

Most generic artifact in the Architecture Continuum

A

Foundation Architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
52
Q

As the architecture evolves, the assets in the Solutions Continuum progresses towards a

A

Organization Specific Solutions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
53
Q

In which phase are the business principles, business goals and strategic drivers first validated?

A

Phase A

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
54
Q

Primary use of the Architecture Vision Document

A

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

The Architecture Vision is created early on in the ADM cycle. It provides a summary of the
changes to the enterprise that will accrue from successful deployment of the Target Architecture.
The purpose of the Architecture Vision is to provide key stakeholders with a formally agreed
outcome. Early agreement on the outcome enables the architects to focus on the detail necessary
to validate feasibility. Providing an Architecture Vision also supports stakeholder
communication by providing a summary version of the full Architecture Definition.

32.2.8 page 356

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
55
Q

Phase B objectives

A

Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve business goals, and respond to strategic drivers set out in the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns

Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures

7.1 page 78

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
56
Q

Phase C objectives

A

Develop the Target Information Systems Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns

Identify candidate Architecture roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures

8.1 page 96

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
57
Q

Model for use in Phase C Application Architecture

A

The Integrated Information Infrastructure Reference Model

35.4.1 page 379

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
58
Q

What document establishes the connection between the architecture organization and the implementation organization in Phase G?

A

Architecture Contract

43.2.2 page 443

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
59
Q

Phase H approach

A

Managing changes to the architecture in a cohesive and architected way.
Establish and support the implemented Enterprise Architecture as a dynamic architecture; one having the flexibility to evolve rapidly in response to changes in the technology and business environment.
Capacity Measurement
Change Management
Measuring Business Growth

page 160

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
60
Q

Business imperatives to be considered when determining the requirements for enterprise architecture work in the Preliminary Phase.

A

Business requirements
Cultural aspirations
Forecast financial requirements
Strategic intent

5.5.3 page 59

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
61
Q

ADM ongoing activity visited throughout TOGAF

A

Requirements Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
62
Q

Risk management in ADM

A

Risk is pervasive in all enterprise architecture activity and should be managed in all phases of the ADM.
Classification, Identification, Initial Risk Assesment, Mitigation, Residual Risk Assessment

27.2 page 258

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
63
Q

A business planning technique that focuses on business outcomes. It also copes well with the friction of co-ordinating projects across corporate functional domains that together enable the enterprise to achieve that capability.

A

Capability based planning

Chapter 28 page 263

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
64
Q

Technique recommended by TOGAF to help identify and understand requirements

A

Business Scenarios

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
65
Q

Foundation for making architecture and planning decisions, framing policies, procedures and standards and supporting resolution of contradictory situations

A

Architecture principles

20.4.1 page 199

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
66
Q

Recommended to define requirements and articulate the Architecture Vision created in Phase A

A

Business Scenario

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
67
Q

It highlights services that are yet to be developed

A

Gap Analysis

chapter 23 page 235

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
68
Q

Practice by which the enterprise architecture and other architectures are managed and controlled at an enterprise level

A

Architecture Governance

44.1.1 page 445

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
69
Q

What does TOGAF Part VI recommend in order to implement an Enterprise Architecture Capability?

A

Architecture Development Method

Chapter 40 page 407

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
70
Q

Essential aspect of architecture governance

A

Ensuring the compliance of individual projects to the enterprise architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
71
Q

Architecture Compliance review purpose

A

To communicate the technical readiness of the project

42.3.1 page 421

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
72
Q

A … is used to describe … of the stakeholder

A

View, Concern

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
73
Q

Every architecture view has an associated … that describes it, at least implicitly

A

Viewpoint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
74
Q

TOGAF building blocks

A

Packages of functionality intended to meet business needs across the organization
Should have stable, published interfaces that allow other building blocks to interoperate with them
May have multiple implementations but with different, interdependent Building Blocks
May be assembled from other Building Blocks

33.2.2 page 365

A building block’s boundary and specification should be loosely coupled to its implementation; i.e. it should be possible to realize a building block in several different ways without impacting the boundary or specification of the building block

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
75
Q

Legacy systems and processes that are going to be used again in the future are considered …

A

Reusable Building Blocks

33.3.1.2 page 368

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
76
Q

Purpose of the Architecture Requirements Specification

A

A quantitative view of the solution to measure the implementation

32.2.6 page 354

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
77
Q

Purpose of Communications Plan

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
78
Q

TOGAF Technical Reference Model …

A

is an example and should be tailored to the needs of an organization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
79
Q

Which TOGAF component was created to enable architects to design architectures addressing Boundaryless Information Flow

A

The Integrated Information Infrastructure Model

35.4.1. page 379

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
80
Q

Getting information to the right people at the right time in a secure, reliable manner in order to support the operations that are core to the extended enterprise

A

Boundaryless Information Flow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
81
Q

TOGAF Technical Reference Model …

A

is a fundamental architecture upon which more specific architectures can be based

35.4.1 page 379

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
82
Q

Which phase of the ADM ensures that implementation projects conform to the defined architecture

A

Phase G

14.1 page 150

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
83
Q

The requirements management phase …

A

stores requirements and manages their flow into relevant ADM phases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
84
Q

Preliminary phase objective …

A

To define the framework and methodologies to be used

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
85
Q

When creating views for a particular architecture, what is the recommended first step?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
86
Q

which of the following architectures in the Architecture Continuum contains the most re-usable architecture elements?

A

Foundation Architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
87
Q

Architecture Vision document

A

A high level description of the baseline and target architectures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
88
Q

Enterprise Continuum use in organizing and developing an architecture

A

Used to structure re-usable architecture and solution assets

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
89
Q

Document sent from sponsoring organization to trigger start of an ADM cycle

A

Request for Architecture Work

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
90
Q

Architecture Governance

A

The practice by which enterprise architectures are controlled at an enterprise-wide level

44.1.1 page 445

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
91
Q

Component within Architecture Repository that holds best practice or template materials that can be used to construct architectures

A

Reference Library

37.3 page 393

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
92
Q

Architecture Board responsibilities

A

Decision Making for changes in the architecture
Enforcing Architecture Compliance
Improving the maturity of the organization’s architecture discipline
Production of governance materials.

41.2 page 413

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
93
Q

Purpose of Compliance Assesment

A

To govern the architecture throughout its implementation process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
94
Q

Key objective of Technology Architecture Phase

A

Togaf 9.2 - 11.1

The objectives of Phase D are to:

Develop the Target Technology Architecture that enables the Architecture Vision, target business, data, and application building blocks to be delivered through technology components and technology services, in a way that addresses the Statement of Architecture Work and stakeholder concerns
Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

To define technology components into a set of technology platforms

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
95
Q

Why the ADM should be adapted

A

To suit the specific needs of the enterprise

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
96
Q

In which phase of the ADM are Gap Analysis results from earlier phases consolidated

A

Phase E

12.1 page 132

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
97
Q

Purpose of business scenario

A

To help identify and understand the business requirements that an architecture must address

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
98
Q

Purpose of enterprise architecture

A

To optimise an enterprise into an environment that is responsive to business needs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
99
Q

How Architecture Principles are used within the ADM

A

They are used to guide decision making within the enterprise

20.1 page 197

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
100
Q

TOGAF Building Blocks use in the ADM cycle

A

Building block become more implementation specific in Phase E

12.1 page 132

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
101
Q

Phase A objective

A

To secure formal approval to proceed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
102
Q

TOGAF Part III provides

A

a set of resources that can be used to adapt and modify the Architecture Development Method

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
103
Q

Objective of Phase B, Business Architecture

A

To demonstrate how stakeholder concerns are addressed in the Business Architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
104
Q

Which section of the TOGAF template for Architecture Principles should highlight the business benefits for adhering to the principle

A

Rationale - Should highlight the business benefits of adhering to the principle, using business terminology. Point to the similarity of information and technology principles to the principles governing business operations. Also describe the relationship to other principles, and the intentions regarding a balanced interpretation. Describe situations where one principle would be given precedence or carry more weight than another for making a decision.

20.3 page 198

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
105
Q

Defined by TOGAF as a representation of a system from the perspective of a related set of concerns

A

Architecture View

31.1 page 319

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
106
Q

TOGAF Architecture Governance Framework includes …

A

a model for governance including process, content and context
44.2.1 page 449

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
107
Q

Order of solutions ranging from generic to enterprise specific

A

Foundation, Common Systems, Industry, Organisation specific

35.4.1 page 378

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
108
Q

Objectives of ADM phase E

A

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

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

Define the overall solution building blocks to finalize the Target Architectures based on the Architecture Building Blocks (ABBs)

12.1 page 132

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
109
Q

Part of Architecture Repository that shows the building blocks that are currently in use within the organisation

A

Architecture Landscape

37.2 page 392

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
110
Q

Responsible for the acceptance and sign-off of an Architecture Compliance review

A

Architecture Board

  1. 2 page 424
  2. 4.3 page 426
  3. 2 page 413
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
111
Q

According to TOGAF, in which page of the ADM should an initial assessment of business transformation readiness occur

A

Phase A

6.2 page 67

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
112
Q

A gap analysis will enable the architect to do:

A

identify building blocks that have been inadvertently ommited
identify building blocks that have been intentionally eliminated
identify building blocks to be carried over
identify new building blocks that are needed

23.1 page 235

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
113
Q

Approach for adapting the ADM in the situation where the business case for doing architecture is not well recognized

A

If the business case for doing architecture at all is not well recognized, then creating an Architecture Vision is almost always essential; and a detailed Business Architecture often needs to come next, in order to underpin the Architecture Vision, detail the business case for remaining architecture work, and secure the active participation of key stakeholders in that work.

4.3 page 42

114
Q

What technique does TOGAF recommend for evaluating the status of an organisation to undergo change?

A

Business Transformation Readiness Assessment

115
Q

Initial Level of Risk in Risk Management

A

The categorization before determining and implementing mitigating actions
27.1 page 257

116
Q

A View is used to describe how the … of a stakeholder are being met

A

Concerns

117
Q

The Architecture Development Method produces content to be stored in the Repository. Which is classified according to the …

A

Enterprise Continuum

118
Q

The state of the architecture artifacts as a project progresses through ADM phases A to D

A

The artifacts evolve from generic architectures to organisation-specific architectures

119
Q

Phase H classification for an incremental change

A

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

155.2 page 162

120
Q

Used as a template to create a View

A

Viewpoint

121
Q

In which sequence should Application Architecture and Data Architecture be developed in Phase C

A

Application Architecture and Data Architecture may be developed in either sequence

122
Q

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

A

Architecture Repository

37.1 page 391

123
Q

A key step in validating a proposed target architecture is to consider what may have been forgotten. What technique does TOGAF recommend to address this issue?

A

Gap Analysis

124
Q

In the Preliminary Phase, preparing the organization to undertake successful architecture

A

defining architecture principles 5.1, 5.3.4
defining relationship between management frameworks 5.5 page 57
defining the enterprise 5.3.1, 5.5
evaluating the enterprise architecture maturity 5.5

125
Q

Which phase of the ADM establishes a set of Principles?

A

Preliminary Phase

126
Q

In which phase of the ADM does the business scenario technique figure most prominently?

A

Architecture Vision

127
Q

Describe Architecture Vision Document

A

A description of how the new capability will address stakeholder concern
somewhat 32.2.8 page 356

128
Q

Describe TOGAF

A

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

129
Q

Which ADM phase establishes the connection between the architecture organization and the implementation organization through the Architecture Contract?

A

Phase G - Architecture Governance

130
Q

Requirements Management Phase

A

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

131
Q

Which section of the TOGAF template for defining principles should highlight the requirements for carrying out the principle?

A

Implications

20.3 page 198

132
Q

Next step in an Architecture Compliance Review once the scope of the review has been determined?

A

Tailor the checklist to address business requirements

42.4.1 page 424

133
Q

During the implementation of an architecture, if the original Architecture Definition and requirements are not suitable, a … may be submitted to initiate further architecture work

A

Change Request

32.2.11 page 388

134
Q

Architecture compliance review purpose

A

determining the technical readiness of a project
ensuring the application of best practices
identifying error in an architecture project
identifying where architecture standards require modification

42.3.1 page 421

135
Q

Step in Phases B, C and D before development of the baseline and target architecture

A

Select reference models, viewpoints and tools

7.3 page 80

136
Q

Which ADM phase is responsible for assessing the performance of the architecture and making recommendations for change

A

Phase H - architecture change management

15.3.5 page 159

137
Q

Which Model within TOGAF is intended to assist with the release management of the TOGAF specification

A

Document Categorization Model

Not in TOGAF 9.2

138
Q

Which ADM phase provides architectural oversight of the implementation?

A

Phase G - Implementation Governance

Chapter 14 - page 149

139
Q

Represents implementations of the architecture at the corresponding levels of the Architecture Continuum

A

Solutions Continuum

35.4.2 page 380

140
Q

Used in organising and developing an architecture to aid communication and understanding between architects

A

Enterprise Continuum

35.1 p375

141
Q

Purpose of Architecture Roadmap

A

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

32.2.7 page 355 (indirect answer)

142
Q

What technique does TOGAF recommend that focuses on achieving business outcomes rather than jut technical deliverables

A

Capability-Based Planning

Chapter 28 page 263

143
Q

Which Model within TOGAF is closely related to the concept of Boundaryless Information Flow?

A

The Integrated Information Infrastructure Model

35.4.1 page 379

144
Q

Which one of the following does TOGAF state is an objective for Phase A: Architecture Vision?

A

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

6.3 page 67

145
Q

In which ADM phase do building blocks become implementation specific

A

Phase E

12.1 page 132

146
Q

Approach for adapting the ADM in the situation where business principles dictate that a packaged solution be used

A

Completion of the Business Architecture should follow the information Systems Architecture

147
Q

Which Architecture domain is recommended to be the first architecture work undertaken in the ADM cycle

A

Business Architecture

148
Q

According to TOGAF, all of the following are responsibilities of an Architecture Board

A

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
41.2 page 413

149
Q

Which section of the TOGAF document contains a structured metamodel for architectural artifacts

A

Part IV: Architecture Content Framework

Chapter 30 page 277

150
Q

Building blocks specification should be loosely coupled to implementation

A

TRUE

33.2.2 page 365

151
Q

Foundation Architecture characteristics

A

Generic building blocks, their inter-relationships with other building blocks, combined with the principles and guidelines that provide a foundation on which more specific architectures can be built.

The ADM is also useful to populate the Foundation Architecture of an enterprise. Business requirements of an enterprise may be used to identify the necessary definitions and selections in the Foundation Architecture. This could be a set of re-usable common models, policy and governance definitions, or even as specific as overriding technology selections (e.g., if mandated by law). Population of the Foundation Architecture follows similar principles as for an Enterprise Architecture, with the difference that requirements for a whole enterprise are restricted to the overall concerns and thus less complete than for a specific enterprise.

It is important to recognize that existing models from these various sources, when integrated, may not necessarily result in a coherent Enterprise Architecture. “Integratability” of Architecture Descriptions is considered in 4.6 Architecture Integration .

Foundation Architecture
A Foundation Architecture consists of generic components, inter-relationships, principles, and guidelines that provide a foundation on which more specific architectures can be built. The TOGAF ADM is a process that would support specialization of such Foundation Architectures in order to create organization-specific models.

The TOGAF TRM is an example of a Foundation Architecture. It is a fundamental architecture upon which other, more specific architectures can be based. See the TOGAF® Series Guide: The TOGAF® Technical Reference Model (TRM) for more details.

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

152
Q

TOGAF covers the development of four architecture domains

A

Business
Data
Technology
Application

153
Q

Objective of Phase G: Implementation Governance

A

Ensure conformance for the target architecture

14.1 page 150

154
Q

Statement of Architecture Work

A

It defines the scope and approach to complete an architecture project

32.2.20 page 363

155
Q

Phase H steps

A

The level of detail addressed in Phase H will depend on the scope and goals of the overall architecture effort.

The order of the steps in Phase H as well as the time at which they are formally started and completed should be adapted to the situation at hand in accordance with the established Architecture Governance.

The steps in Phase H are as follows:

Establish value realization process
Deploy monitoring tools
Manage risks
Provide analysis for architecture change management
Develop change requirements to meet performance targets
Manage governance process
Activate the process to implement change

15.3 page 158

156
Q

Value stream

A

A representation of an end-to-end collection of value-adding activities that create an overall result for a customer, stakeholder, or end user.

157
Q

Objectives of the Preliminary Phase

A

Determine the Architecture Capability desired by the organization:
- Review the organizational context for conducting Enterprise Architecture
- Identify the scope of elements of the enterprise organizations affected by Architecture Capability
- Establish Capability Maturity target
Establish the Architecture Capability:
- Define and establish the Organizational Model for Enterprise Architecture
- Define and establish the detailed process and resources for Architecture Governance
- Select and implement tools that support the Architecture Capability
- Define Architecture Principles

158
Q

In which part of the ADM cycle do building block gaps become associated with work packages that will address the gap?

A

Phase E

159
Q

Responsibility of an Architecture Board

A

Enforcement of architecture compliance

160
Q

Reason why Business Architecture is recommended to be first architecture developed

A

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

161
Q

Integrated Infrastructure Reference Model

A

Application Architecture Reference Model

162
Q

Architecture Governance

A

Practice by which the enterprise architecture is managed and controlled at an enterprise level is known as

41.1.1 page 445

163
Q

Phase H re-architecting change

A

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

15.5.2 page 162

164
Q

The purpose of Business Transformation Readiness Assessment technique

A

To determine if organization is ready to undergo change

165
Q

In which ADM phase is the implementation and Migration Plan coordinated with other frameworks

A

Phase F

13.1 page 142

166
Q

Described by the TOGAF Architecture Content Framework as a type of artifact that shows list of things

A

Catalog

A.4 page 479
31.6 page 326

167
Q

Includes open system standards and general building blocks

A

Foundation Architecture

168
Q

TOGAF uses a version numbering scheme to illustrate the evolution of the Baseline and Target Architecture Definitions. Which version number in this convention indicates a formally reviewed, detailed architecture

A

1.0

169
Q

TOGAF Architecture Development Method

A

A process for developing an organization-specific enterprise architecture

170
Q

The need for the ADM process to be governed

A

To ensure that the method is being applied correctly

171
Q

Objective of Phase A, Architecture Vision

A

Identifying stakeholders and their concerns

172
Q

TOGAF recommends for use in developing of the Architecture Vision

A

Business Scenarios

173
Q

Relevant architecture resource in Phase D

A

Generic technology models relevant to the organization’s industry sector

174
Q

In which section of the TOGAF template for Architecture Principles would a reader find the answer to the question ‘How does this affect me’?

A

Implications

20.3 page 198

175
Q

Key interests crucially important to stakeholders

A

Concerns

31.1 page 319

176
Q

Which Architecture would describe Infrastructure requirements

A

Technology Architecture

11.3.1 page 125

177
Q

Reference Library within Architecture Repository

A 
The  Reference  Library  provides  a  repository  to  hold  reference  materials  that  should  be  used  to develop  architectures.  Reference  materials  held  may  be  obtained  from  a  variety  of  sources, including:
■Standards bodies
■Product and service vendors
■Industry communities or forums
■Standardtemplates
■Enterprise best practice
The Reference Library should contain:
■Reference Architectures
■Reference Models
■Viewpoint Library
■Templates
178
Q

Five Criteria for a good set of principles

A

Understandable, Robust, Complete, Consistent, Stable

179
Q

A … is a representation of a system from the perspective of a related set of …

A

view, stakeholders

?

180
Q

Standards Information Base

A

The Standards Information Base provides a repository area to hold a set of specifications, to which architectures must conform. Establishment of a Standards Information Base provides an unambiguous basis for Architecture Governance because:
■The standards are easily accessible to projects and therefore the obligations of the project can be understood and planned for
■Standards are stated in a clear and unambiguous manner, so that compliance can be objectively assessed

181
Q

Purpose of Gap Analysis technique

A

To identify missing functions

182
Q

How enterprise continuum is used when developing an enterprise architecture

A

To structure re-usable architecture and solution assets

183
Q

A … is used in Phase A to help identify and understand business … that the architecture has to address

A

business scenario, requirements

184
Q

Architecture Pattern

A

A way to put building blocks together into context

Chapter 22 page 229

185
Q

Residual level of risk

A

Risk Categorization after the implementation of mitigating actions.

186
Q

Requirements Management process

A

It is used to manage architecture requirements throughout ADM cycle
16.1 page 166

187
Q

Architecture

A

A formal description of a system, or a detailed plan of the system at component level to guide its implementation

188
Q

Architecture Landscape is divided into three levels:

A

Strategic, Segment and Capability

37.2 page 392

189
Q

In phases B, C, D which is the final step in each phase

A

Create the Architecture Definition Document

  1. 2 page 79
  2. 31 page 99
  3. 3 page 111
  4. 3 page 121
190
Q

Which part of TOGAF describes taxonomies for categorizing the outputs of architecture activity in terms of reuse?

A

Part V. Enterprise Continuum and Tools

191
Q

Purpose of Architecture Compliance Review

A

Identifying errors in the project architecture

42.3.1 page 421

192
Q

TOGAF provides a set of reference materials for establishing an architecture function within an organization known as the

A

Architecture Capability Framework

39.1 page 405

193
Q

Package of functionality defined to meet business needs across an organization

A

A building block

3.23 page 24

194
Q

Which document should incorporate the actions arising from the Business Transformation Readiness Assessment technique

A

Implementation and Migration Plan

2.6.5 page 255

195
Q

Architecture Vision purpose

A

It provides a high-level aspirational view of the end architecture project
6.1 page 66

196
Q

TOGAF Part VI Architecture Capability Framework recommends use of ADM cycle for establishing an architecture practice. In this scenario which architecture would describe the organizational structure for the architecture practice.

A

Business Architecture

40.1 page 407

197
Q

Business Scenario technique purpose

A

To help identify and understand requirements

198
Q

The Requirements Management process is used to

A

Organize architecture requirements throughout the ADM cycle

199
Q

TOGAF Technical Reference Model

A

A Foundation Architecture

200
Q

Preliminary Phase Objective

A

Establish the Organizational Model for enterprise architecture

201
Q

Class of information known as the Architecture Capabillity within the Architecture Repository

A

Processes to support governance of the Architecture Repository

202
Q

An Objective of phase G, Implementation Governance is to

A

Ensure conformance with the defined architecture by the implementation projects

203
Q

Part of the approach in the Preliminary Phase of the ADM

A

Defining a set of Architecture Principles

5.1 page 52

204
Q

Describe TOGAF classification in Phase H for a simplification change

A

A change driven by a requirement to reduce investment

15.5.2 page 162

205
Q

In Phases B, C and D which is the first step in each phase

A

Select reference models, viewpoints and tools

  1. 3 page 80
  2. 3 page 99
206
Q

The ADM can be viewed as process of populating the enterprise’s own … with relevant re-usable building blocks taken from the more generic side of the Enterprise Continuum

A

Architecture Repository

207
Q

Describes concept of Boundaryless Information Flow

A

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

208
Q

describes people who have key roles in, or concerns about a system

A

Stakeholders

3.72 page 31

209
Q

In which phase of the ADM cycle do building blocks become implementation specific

A

Phase E

12.1 page 132

210
Q

Purpose of Architecture Definition Document

A

To act as a deliverable container for artifacts created during a project
32.2.3 page 352

211
Q

Building Blocks that are viewed as being at the left-hand side of the Solutions Continuum are known as …

A

Foundation Solutions

212
Q

An approach to ensure the effectiveness of and organization’s architectures

A

TOGAF Architecture Governance Framework

213
Q

The Enterprise Continuum provides methods for classifying architecture artifacts as they evolve from

A

Generic Architectures to Organization-Specific Architectures

214
Q

Objective of Phase F: Migration Planning Phase

A

The objectives of Phase F are to:

Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
Ensure that the Implementation and Migration Plan is co-ordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio
Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

Coordinate the Implementation and Migration Plan with other frameworks

215
Q

Purpose of Gap Analysis technique

A

To hightlight shortfalls between the baseline and target architectures
Chapter 23 page 235

216
Q

Define general rules and guidelines for the use of assets across the enterprise

A

Architecture principles

20.2 page 198

217
Q

Which ADM Phase includes obtaining approval for the Statement of Architecture Work

A

Phase A: Architecture Vision

6.1 page 66

218
Q

Which section of the TOGAF template for Architecture Principles highlights the requirements for carrying out the principle?

A

Implications

219
Q

TOGAF uses version numbering convention to illustrate evolution of the Baseline and Target Architecture Definitions. Which version number in this convention indicates a high-level outline of the architecture?

A

Version 0.1

220
Q

In which ADM phase is the goal to ensure that the architecture achieves its original target business value

A

Phase H - Enterprise Architecture Capability meets current requirements

15.5 page 159
(Phase G - conformance with target Architecture)

221
Q

Which ADM phase starts with the receipt of a Request for Architecture Work from the sponsoring organization

A

Phase A

  1. 2.2 page 66
  2. 2.17 page 362
222
Q

Described by TOGAF Architecture Content Framework as a type of artifact that shows relationships between things.

A

Matrix

31.6 page 327

223
Q

TOGAF defines 5 criteria for a good set of principles

A

Complete, Consistent, Stable, Understandable, Robust

20.4.1 page 199

224
Q

A review of an architecture project against established criteria and business objectives

A

Architecture Compliance Review

42.3 page 421

225
Q

The Architecture Landscape is divided into three levels

A

Capability, Segment and Strategic

37.2 page 420

226
Q

Reusable artifact used to create architecture models addressing stakeholder concerns

A

Viewpoint
page 321
31.1

227
Q

TOGAF describes the role of an Architecture Contract as

A

An agreement between development partners and sponsors on the architecture deliverables
32.2.2 page 351

228
Q

The structure of components, their inter-relationships and the principles guiding their design and evolution over time

A

Architecture

229
Q

Describes a step-by-step approach to developing an enterprise architecture

A

Architecture Development Method

230
Q

Provides a set of reference materials for establishing an architecture function within an organization

A

Architecture Capability Framework

231
Q

First phase of an architecture development cycle, defines the scope for an engagement and identifies the stakeholders?

A

Architecture Vision

232
Q

Portfolio of guidance material to support practical application of the TOGAF approach.

A

TOGAF Library

233
Q

Library resources are organized into four sections

A

Foundation Documents
Generic Guidance and Techniques
Industry-Specific Guidance and Techniques
Organization-Specific Guidance and Techniques

234
Q

A concepcual structure used to plan, develop, implement, govern, and sustain an architecture

A

Architecture Framework

235
Q

Two key elements of an architecture Framework according to TOGAF 9.2

A

A definition of the deliverables that the architecting activity should produce
A description of the method by which this should be done

2.10 page 20

236
Q

Building Blocks characteristics

A

a package of functionality defined to meet the business needs across an organization
has a type that corresponds to the enterprise’s content metamodel (such as actor, business service, application or data entry)
A building block has a defined boundary and is generally recognizable as “a thing” by domain experts
may interoperate with other, inter-dependent building blocks

33.2.2 page 365

237
Q

A Good Building block characteristics

A

considers implementation and usage, and evolves to exploit technology and standards
may be assembled from other building blocks
may be a subassembly of other building blocks
ideally is re-usable and replaceable, and well specified

33.2.2 page 366

238
Q

Phase A: Architecture Vision steps

A

Establish Architecture Project
Identify Stakeholders, concerns, and business requirements
Confirm and elaborate business goals, business drivers, and constraints
Evaluate Capabilities
Assess readiness for business transformation
Define scope
Confirm and elaborate Architecture Principles, including business principles
Develop Architecture Vision
Define the Target Architecture value proposition and KPIs
Identify the business transformation risks and mitigation activities
Develop Statement of Architecture Work; secure approval

239
Q

Phase B: Business Architecture Steps

A

Select reference models, viewpoints, and tools
Develop Baseline Business Architecture Description
Develop Target Business Architecture Description
Perform Gap Analysis
Define candidate roadmap components
Resolve impacts across the Architecture Landscape
Conduct formal stakeholder review
Finalize the Business Architecture
Create the Architecture Definition Document

240
Q

Phase E: Opportunities & Solutions Steps

A

Determine/confirm key corporate change attributes
Determine business constraints for implementation
Review and consolidate gap analysis results from Phases B to D
Review consolidated requirements across related business functions
Consolidate and reconcile interoperability requirements
Refine and validate dependencies
Confirm readiness and risk for business transformation
Formulate Implementation and Migration Strategy
Identify and group major work packages
Identify Transformation Architectures
Create the Architecture Roadmap & Implementation and Migration Plan

241
Q

provide more detailed operating models
for areas within an enterprise.
can be used at the program or portfolio level to organize and operationally align more detailed change activity.

A

Segment Architectures

242
Q

show in a more detailed fashion how
the enterprise can support a particular unit of capability.
used to provide an overview of current capability, target capability, and capability
increments and allow for individual work packages and projects to be grouped within managed portfolios and programs.

A

Capability Architectures

243
Q

provides a repository to hold reference materials that should be used to
develop architectures.

A

Reference Library

244
Q

Reference Library should contain

A

Reference Architectures
Reference Models
Viewpoint Library
Templates

37.3.1

245
Q

Standards typically fall into three classes:

A

Legal and Regulatory Obligations: these standards are mandated by law and therefore an
enterprise must comply or face serious consequences

Industry Standards: these standards are established by industry bodies, such as The Open
Group, and are then selected by the enterprise for adoption
Industry Standards offer potential for interoperation and sharing across enterprises, but
also fall outside of the control of the enterprise and therefore must be actively monitored.

Organizational Standards: these standards are set within the organization and are based
on business aspiration (e.g., selection of standard applications to support portfolio
consolidation)
Organizational Standards require processes to allow for exemptions and standards
evolution.

37.4.2

246
Q

Standards Lifecycle

A

Proposed Standard, Provisional Standard, Standard (Active), Phasing-Out Standard, Retired Standard

37.4.3

247
Q

Standards Classification within the Standards Information Base

A

Business Standards, Data Standards, Applications Standards, Technology Standards

37.4.4

248
Q

Contents of the Governance Log

A

Decision Log, Compliance Assessments, Capability Assessments, Calendar, Project Portfolio, Performance Measurement

37.5.2

249
Q

This includes the initial mobilization of the architecture activity for a given purpose or
architecture engagement type by establishing or adjusting the architecture approach,
principles, scope, vision, and governance.

A

Architecture Capability iterations support the creation and evolution of the required Architecture Capability

250
Q

allow the creation of architecture content by cycling
through, or integrating, Business, Information Systems, and Technology Architecture
phases

A

Architecture Development iterations
These iterations ensure that the architecture is considered as a whole. In this type of
iteration stakeholder reviews are typically broader. As the iterations converge on a target,
extensions into the Opportunities & Solutions and Migration Planning phases ensure that
the architecture’s implementability is considered as the architecture is finalized

251
Q

support the creation of formal change roadmaps for a

defined architecture

A

Transition Planning iterations

252
Q

support governance of change activity progressing

towards a defined Target Architecture

A

Architecture Governance iterations

253
Q

in this style, an assessment of the baseline landscape is used to identify
problem areas and improvement opportunities
This process is most suitable when the baseline is complex, not clearly understood, or
agreed upon. This approach is common where organizational units have had a high degree
of autonomy.

A

Baseline First

18.4

254
Q

in this style, the target solution is elaborated in detail and then mapped back
to the baseline, in order to identify change activity
This process is suitable when a target state is agreed at a high level and where the
enterprise wishes to effectively transition to the target model.

A

Target First

18.4

255
Q

characteristics typically used to organize the Architecture Landscape

A

Breadth, Depth, Time, Recency

Breadth: the breadth (subject matter) area is generally the primary organizing characteristic for describing an Architecture Landscape
Architectures are functionally decomposed into a hierarchy of specific subject areas or segments.

Depth: with broader subject areas, less detail is needed to ensure that the architecture has a manageable size and complexity
More specific subject matter areas will generally permit (and require) more detailed architectures.

Time: for a specific breadth and depth an enterprise can create a Baseline Architecture and a set of Target Architectures that stretch into the future
Broader and less detailed architectures will generally be valid for longer periods of time and can provide a vision for the enterprise that stretches further into the future.

Recency: finally, each architecture view will progress through a development cycle where it increases in accuracy until finally approved
After approval, an architecture will begin to decrease in accuracy if not actively maintained. In some cases recency may be used as an organizing factor for historic architectures.

256
Q

The steps in Phase H

A

■ Establish value realization process
■ Deploy monitoring tools
■ Manage risks
■ Provide analysis for architecture change management
■ Develop change requirements to meet performance targets
■ Manage governance process
■ Activate the process to implement change

15.3

257
Q

outputs of Phase H

A

may include, but are not restricted to:
■ Architecture updates (for maintenance changes)
■ Changes to architecture framework and principles (for maintenance changes)
■ New Request for Architecture Work, to move to another cycle (for major changes)
■ Statement of Architecture Work, updated if necessary
■ Architecture Contract, updated if necessary
■ Compliance Assessments, updated if necessary

258
Q

The

areas where the Technology Architecture may be impacted in Phase D

A

Performance
Maintainability
Location and Latency
Availability

In the earlier phases of the ADM, certain decisions made around service granularity and service boundaries will have implications on the technology component and the technology service. The areas where the Technology Architecture may be impacted will include the following:

Performance: the granularity of the service will impact on technology service requirements
Coarse-grained services contain several units of functionality with potentially varying non-functional requirements, so platform performance should be considered. In addition, coarse-grained services can sometimes contain more information than actually required by the requesting system.

Maintainability: if service granularity is too coarse, then introducing changes to that service becomes difficult and impacts the maintenance of the service and the platform on which it is delivered

Location and Latency: services might interact with each other over remote links and inter-service communication will have in-built latency
Drawing service boundaries and setting the service granularity should consider platform/location impact of these inter-service communications.

Availability: service invocation is subject to network and/or service failure
So high communication availability is an important consideration during service decomposition and defining service granularity

11.3.1.1

259
Q

Architecture Compliance - levels of conformance

A

Irrelevant: The implementation has no features in common with the architecture specification (so the question of conformance
does not arise).

Consistent: The implementation has some features in common with the
architecture specification, and those common features are
implemented in accordance with the specification. However,
some features in the architecture specification are not
implemented, and the implementation has other features
that are not covered by the specification.

Compliant: Some features in the architecture specification are not
implemented, but all features implemented are covered
by the specification, and in accordance with it.

Conformant: All the features in the architecture specification are
implemented in accordance with the specification, but
some more features are implemented that are not
in accordance with it.

Fully Conformant: There is full correspondence between architecture
specification and implementation. All specified features
are implemented in accordance with the specification,
and there are no features implemented that are not
covered by the specification.

Non-conformant: Any of the above in which some features in the
architecture specification are implemented not in
accordance with the specification.

260
Q

Architecture Compliance Review Process Steps

A

Architecture Review Request

Identify Responsible Organization, (Architecture Review Co-ordinator)
Identify Lead Architect, (Architecture Review Co-ordinator)
Determine Scope of Review (Discovery), (Architecture Review Co-ordinator)
Tailor Checklists, (Lead Architect)
Schedule Architecture Review Meeting, (Architecture Review Co-ordinator)
Interview Project Principals, (Lead Architect, Project Leader, Customers)
Analyze Completed Checklists, (Lead Architect)
Prepare Architecture Review Report (Lead Architect)
Present Review Findings (Lead Architect)
Accept, Review, and Sign off (Architecture Board, Customer)

Assessment Report/Summary

261
Q

Types of standard

A

Legal and Regulatory Obligations: these standards are mandated by law and therefore an enterprise must comply or face serious consequences

Industry Standards: these standards are established by industry bodies, such as The OpenGroup, and are then selected by the enterprise for adoption
Industry Standards offer potential for interoperation and sharing across enterprises, but also fall outside of the control of the enterprise and therefore must be actively monitored.

Organizational Standards: these standards are set within the organization and are based on business aspiration (e.g., selection of standard applications to support portfolio consolidation)
Organizational Standards require processes to allow for exemptions and standards evolution.

262
Q

Standards Lifecycle

A

Typically, standards pass through the following stages:

Proposed Standard: a potential standard has been identified for the organization, but has not yet been evaluated for adoption

Provisional Standard (also known as a Trial Standard): a Provisional Standard has been identified as a potential standard for the organization, but has not been tried and tested to a level where its value is fully understood Projects wishing to adopt Provisional Standards may do so, but under specific pilot conditions, so that the viability of the standard can be examined in more detail.

Standard (also known as an Active Standard): a Standard defines a mainstream solution that should generally be used as the approach of choice

Phasing-Out Standard (also known as Deprecated Standard): a Phasing-Out Standard is approaching the end of its useful lifecycle
Projects  that  are re-using  existing  components  can  generally  continue  to  make  use  of Phasing-Out  Standards.  Deployment  of  new  instances  of  the  Phasing-Out  Standard is generally discouraged.
Retired Standard (also known as an Obsolete Standard): a Retired Standard is no longer accepted as valid within the landscape
In  most  cases,  remedial  action  should  be  taken  to  remove  the  Retired  Standard from the landscape. Change activity on a Retired Standard should only be accepted as a part of an overall decommissioning plan.
263
Q

Architecture Governance Framework

A

Architecture Governance is an approach, a series of processes, a cultural orientation, and set of owned responsibilities that ensure the integrity and effectiveness of the organization’s architectures
page 449

264
Q

Some features in the architecture specification are not
implemented, but all features implemented are covered
by the specification, and in accordance with it.

A

Compliant

265
Q

The implementation has some features in common with the architecture specification, and those common features are implemented in accordance with the specification. However, some features in the architecture specification are not implemented, and the implementation has other features that are not covered by the specification.

A

Consistent

266
Q

The implementation has no features in common with the architecture specification (so the question of conformance does not arise).

A

Irrelevant

267
Q

All the features in the architecture specification are implemented in accordance with the specification, but some more features are implemented that are not in accordance with it.

A

Conformant

268
Q

There is full correspondence between architecture specification and implementation. All specified features are implemented in accordance with the specification, and there are no features implemented that are not covered by the specification.

A

Fully Conformant

269
Q

Any of the above in which some features in the architecture specification are implemented not in accordance with the specification

A

non conformant

270
Q

Risk Effect classification

A

Catastrophic - infers critical financial loss that could result in bankruptcy of the organization
Critical - infers serious financial loss in more than one line of business leading to a loss in productivity and no return on investment on the IT investment
Marginal - infers a minor financial loss in a line of business and a reduced return on investment on the IT investment
Negligible - infers a minimal impact on a line of business’ ability to deliver services and/or products

271
Q

Risk Frequency classification

A

Frequency can be classified as ‘Frequent, Likely, Occasional, Seldom and Unlikely’

272
Q

The Impact of a risk, that is the combination of Effect and Frequency can be classified as

A

‘Extremely High Risk’, ‘High Risk, Moderate Risk and Low Risk’

273
Q

Architecture Governance typically does not operate in isolation, but within a hierarchy of governance structures, which, particularly in the larger enterprise, can include all of the following as distinct domains with their own disciplines and processes:

A

Corporate Governance
Technology Governance
IT Governance
Architecture Governance

274
Q

The Implementation and Migration Plan provides a schedule of the projects that will realize the
Target Architecture. The Implementation and Migration Plan includes executable projects
grouped into managed portfolios and programs. The Implementation and Migration Strategy
identifying the approach to change is a key element of the Implementation and Migration Plan

A

Typical contents of an Implementation and Migration Plan are:
■ Implementation and Migration Strategy:
— Strategic implementation direction
— Implementation sequencing approach
■ Project and portfolio breakdown of implementation:
— Allocation of work packages to project and portfolio
— Capabilities delivered by projects
— Milestones and timing
— Work breakdown structure
— May include impact on existing portfolio, program, and projects

Project charters:
— Included work packages
— Business value
— Risk, issues, assumptions, dependencies
— Resource requirements and costs
— Benefits of migration, determined (including mapping to business requirements)
— Estimated costs of migration options

275
Q

The objectives of Phase H are to:

A

Ensure that the architecture lifecycle is maintained
Ensure that the Architecture Governance Framework is executed
Ensure that the Enterprise Architecture Capability meets current requirements

15.1

276
Q

The objectives of Phase E are to:

A

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
Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
Define the overall solution building blocks to finalize the Target Architecture based on the Architecture Building Blocks (ABBs)

12.1

277
Q

The objectives of Phase G are to:

A

Ensure conformance with the Target Architecture by implementation projects
Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests
15.1

278
Q

The objectives of Phase F are to:

A

Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
Ensure that the Implementation and Migration Plan is co-ordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio
Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

13.1

279
Q

The steps in Phase F:

A

The level of detail addressed in Phase F will depend on the scope and goals of the overall architecture effort.

The order of the steps in Phase F as well as the time at which they are formally started and completed should be adapted to the situation at hand in accordance with the established Architecture Governance.

All activities that have been initiated in these steps must be closed during the “Complete the architecture development cycle and document lessons learned step” (see 13.3.7).

The steps in Phase F are as follows:

  1. 3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
  2. 3.2 Assign a Business Value to Each Work Package
  3. 3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
  4. 3.4 Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation
  5. 3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
  6. 3.6 Complete the Implementation and Migration Plan
  7. 3.7 Complete the Architecture Development Cycle and Document Lessons Learned

13.3

280
Q

The steps in Phase G:

A

The level of detail addressed in Phase G will depend on the scope and goals of the overall architecture effort.

The order of the steps in Phase G as well as the time at which they are formally started and completed should be adapted to the situation at hand in accordance with the established Architecture Governance.

The steps in Phase G are as follows:

  1. 3.1 Confirm Scope and Priorities for Deployment with Development Management
  2. 3.2 Identify Deployment Resources and Skills
  3. 3.3 Guide Development of Solutions Deployment
  4. 3.4 Perform Enterprise Architecture Compliance Reviews
  5. 3.5 Implement Business and IT Operations
  6. 3.6 Perform Post-Implementation Review and Close the Implementation

Togaf (1 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions