Togaf 9.1 - Foundations - Level 1

Front 1

What are the phases within the ADM?

Back 1

Preliminary, A through H, Requirements Management

Front 2

Describe the ADM Preliminary Phase

Back 2

" prep & initiation activities required to create an Arch Capability

includes customization of TOGAF and defn of Architecture Principles"

Front 3

Describe ADM Phase A

Back 3

Phase A: - Architecture Vision Describes the initial phase of an architecture development cycle:

-defining the scope of the architecture development initiative,

-identifying the stakeholders,

-creating the Architecture Vision,

-obtaining approval to proceed with the architecture development.

Front 4

Describe ADM Phase B

Back 4

Phase B: describes the development of a Business Architecture to support the agreed Architecture Vision.

develop baseline (bottom up)

develop target (top down)

Front 5

Describe ADM Phase C

Back 5

Phase C: describes the development of Information Systems Architectures to support the agreed Architecture Vision.

Front 6

Describe ADM Phase D

Back 6

Phase D: describes the development of the Technology Architecture to support the agreed Architecture Vision.

Front 7

Describe ADM Phase E

Back 7

Phase E: Opportunities & Solutions conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases.

Front 8

Describe ADM Phase F

Back 8

Phase F: Migration Planning addresses how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan.

Front 9

Describe ADM Phase G

Back 9

Phase G: Implementation Governance provides an architectural oversight of the implementation.

Front 10

Describe ADM Phase H

Back 10

Phase H: Architecture Change Management establishes procedures for managing change to the new architecture.

Front 11

Describe ADM Requirements Management Phase

Back 11

Requirements Management examines the process of managing architecture requirements throughout the ADM.

Front 12

What are the 4 types of architecture in TOGAF (architecture domain)

Back 12

BDAT

Business, Data, Application, Technical

Front 13

What is business architecture domain?

Back 13

The Business Architecture defines the business strategy, governance, organization, and key business processes.

look at business problems irrespective of tech; must be done first

Front 14

What is data architecture domain?

Back 14

The Data Architecture describes the structure of an organization's logical and physical data assets and data management resources.

Front 15

What is application architecture

Back 15

a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization.

Front 16

What is technical architecture domain?

Back 16

logical software and hardware capabilities that are required to support the deployment of business, data, and application services.

This includes IT infrastructure, middleware, networks, communications, processing, standards, etc.

Front 17

What is the TOGAF Architecture Content Framework?

Back 17

A structural model for arch content (from process flows to requirements to assessments and so on)

Front 18

What are the three categories of assets in the Content Framework?

Back 18

Deliverables, artifacts, and building blocks

Front 19

What is a deliverable?

Back 19

a work product that is contractually specified

gets signed off on by stakeholder

output of a project

Front 20

what is an artifact?

Back 20

an architectural work product that describes an aspect of the architecture; may not be in a deliverable!!

Artifacts are generally classified as catalogs, lists, matrices , and diagrams (pictures of things)

NOTE: deliverables may contain artifacts

Front 21

What is a building block?

Back 21

apotentially re-usable component of business, IT, or architectural capability

Front 22

Name the two categories of building blocks.

Back 22

Architectural (ABB)- The requirement - Describe required capability and shape the specification of Solution Building Blocks (SBBs).

Solution (SBB) - the solution - components that will be used to implement the required capability i.e. a network

Front 23

relationships between deliverables, artifacts, and building blocks

Back 23

Front 24

An example of the relationships between deliverable, artifacts, and building blocks

Back 24

Front 25

What is the enterprise continuum?

Back 25

A view of the Architecture Repository that provides a way to classifying architecture and solution artifacts as they evolve from generic Foundation Architectures (left) to Organization-Specific Architectures (right)

"a continuum is a line"; generic on the left, specific on the right

Front 26

What two concepts make up the enterprise continuum?

Back 26

the Architecture Continuum and the Solutions Continuum.

Front 27

Enterprise Continuum

Back 27

Front 28

What is the architectural repository?

Back 28

Architecture Repository is used to store different classes of architectural output at different levels of abstraction, created by the ADM

Think filing cabinet

Front 29

arch repository

Back 29

Front 30

What are the major components of the arch repository?

Back 30

Architecture Metamodel

Architecture Capability

Architecture Landscape

Standards Information Base (SIB)

Reference Library

Governance Log

Front 31

What is the metamodel?

Back 31

Describes the organizationally tailored application of an architecture framework, including a metamodel for architecture content.

THE TEMPLATES

Front 32

What is the capability in the arch repository

Back 32

The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository.

Front 33

What is the arch landscape in the arch repository?

Back 33

architectural representation of assets deployed within the operating enterprise at a particular point in time.

The landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives

Defines as is and to be

Front 34

What is the SIB?

Back 34

Standards Information Base (SIB) captures the standards with which new architectures must comply,

SIB may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization.

Front 35

What is a reference library of the arch repository?

Back 35

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.

Front 36

What is the governance log in the arch repository?

Back 36

The Governance Log provides a record of governance activity across the enterprise.

Front 37

What is the importance of the business capability WRT enterprise arch?

Back 37

It defines the organization structures, roles, responsibilities, skills, and processes

Front 38

Business Capability

Back 38

Front 39

T/F: An enterprise architecture practice must be run like any other operational unit within a business; i.e., it should be treated like a business.

Back 39

TRUE!

Front 40

What are the capabilities that must be established to support an enterprise architecture practice?

Back 40

Financial Management

Performance Management

Service Management

Risk Management

Resource Management

Communications and Stakeholder Management

Quality Management

Supplier Management

Configuration Management

Environment Management

Front 41

Name some business benefits of enterprise governance using TOGAF

Back 41

transparency

controlled risk

Value creation through monitoring, measuring, evaluation, and feedback

Front 42

NOTE: In all cases, it is expected that the architect will adapt and build on the TOGAF framework in order to define a tailored method that is integrated into the processes and organization structures of the enterprise.

Front 43

Define Abstraction

Back 43

The technique of providing summarized or generalized descriptions of detailed and complex content.

Front 44

Actor

Back 44

A person, organization, or system that has a role that initiates or interacts with activities. can be internal or external

Front 45

Application

Back 45

A deployed and operational IT system that supports business functions and services;

Front 46

Application Architecture

Back 46

A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets

Front 47

Application Platform

Back 47

The collection of technology components of hardware and software that provide the services used to support applications.

Front 48

Application Platform Interface (API)

Back 48

The interface, or set of functions, between application software and/or the application platform.

Front 49

Architectural Style

Back 49

The combination of distinctive features in which architecture is performed or expressed.

Front 50

Architecture (2 defns)

Back 50

(1) formal description of a system, or a detailed plan of the system at component level, to guide its implementation (source: ISO/IEC 42010:2007).

(2) The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.

Front 51

Architecture Building Block (ABB)

Back 51

A constituent of the architecture model that describes a single aspect of the overall model.

Front 52

ADM is method used to define arch

9 phases + requirements

Flower Chart

Back 52

heart of togaf

iterative/ never ending

baseline and target architecture

Front 53

What are the classification system or levels of architectures in the Enterprise Continuum (generic to specific)?

Back 53

Foundation arch (most generic)

Common systems arch

Industry arch

Org specific arch (most specific)

Front 54

What is the arch capability of your organization?

Back 54

capability of business to support arch

full time architecture/group and governance

top down and bottom up buy-in

roles and responsibilities defined

skills and processes

Front 55

What is the arch repository?

Back 55

Think filing cabinet

Support enterprise continuum

different levels of abstraction

MetaModel - templates

Front 56

ADM - Arch Dev Method

Back 56

Most important part of TOGAF; Preliminary phase + 8 phases (A-H) with requirements at the center

Phase A-H repeat as necessary; preliminary happens once only

method for developing and managing lifecycle of enterprise arch

Front 57

ADM

Back 57

Front 58

Can you adapt the ADM and change phase order?

Back 58

"One reason for wanting to adapt the ADM ... is that the order of the phases in the ADM is to some extent dependent on the maturity of the architecture discipline within the enterprise"

"it often doesn't make sense to do things out of order - like you can't do migration planning before requirements design"

Intended to be generic and fit most BUT modifiable/tailorable

Front 59

All phases have inputs and outputs

Back 59

--

Front 60

Describe Requirements phase

Back 60

it is continuous

Front 61

Preliminary Phase

Back 61

+Prep and initiation activities:

-->Define what makes up the "enterprise" (could be a business unit, company, or outside partners)

-->Pick your framework

-->Evaluate enterprise maturity/capability

-->Define architectural principles

Front 62

Phase A

Back 62

Vision Phase (PMI-like)

Very business focused

High Level Vision - "0.1 level"

Obtain SOW

-->define scope

-->estimate resources

-->develop roadmap / schedule

-->define KPIs/metrics

-->communication plan

Front 63

Phase B

Back 63

Business Architecture; "B" in BDAT

Develop baseline business arch v1.0 (current; bottom up)

Develop target bus arch v1.0 (top down)

Map gaps between baseline and target

Front 64

Phase C

Back 64

Information Systems Arch ("D" & "A" in BDAT)

data and app done separately

define baseline(s) and target(s) - one for each

Front 65

Phase D

Back 65

Tech Arch; "T" in BDAT

develop baseline and target (v1.0s) and gap

Tech Arch supports BDA

At the end of phase D, have traditional solution defined

Front 66

Phase E

Back 66

Opportunities & Solutions

initial implementation planning

the identification of delivery vehicles for the architecture defined in previous phases

Front 67

Phase F

Back 67

Migration Planning addresses how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan.

Front 68

Phase G

Back 68

Implementation Governance provides an architectural oversight of the implementation.

Front 69

Phase H

Back 69

Architecture Change Management establishes procedures for managing change to the new architecture.

Front 70

Requirements Management

Back 70

Managing architecture requirements throughout the ADM.

Front 71

Objectives of Preliminary Phase

Back 71

1- determine arch capability desired by org

2 - establish arch capability

Front 72

Approach to Preliminary Phase

Back 72

-define enterprise

-identify key drivers / elements

-define requirements for arch work (the arch project)

-define arch principles

-define frameworks

-define relationships between mgmt f/w

-evaluate EA maturity

Front 73

Inputs to Preliminary Phase

Back 73

(not as important)

-reference materials: TOGAF, Other frameworks

- non-arch: strategies, business plans, ITS strategy, business principles

Major frameworks w/in the business

arch capability

partnership / contract agreements

- Arch inputs: pre-existing org models; pre-existing arch F/W

Front 74

Steps of Preliminary Phase

Back 74

1 - scope enterprise orgs impacted

2 - confirm governance and support frameworks

3 - define / establish arch team

4 - identify /est arch principles

5 - Tailor TOGAF & F/Ws

6 - implement arch tools

Front 75

Outputs of Prelim

Back 75

1- organizational model for EA

2 - tailored arch F/W

3 - arch repository (possibly new)

4 - restate/reference business principles

5 - "Requests for arch work" (like an SOW)

6 - arch governance F/W

Front 76

Architecture development is a continuous, cyclical process, and in executing the ADM repeatedly over time, the architect gradually adds more and more content to the organization's Architecture Repository

Back 76

NOTE: In fact, the first execution of the ADM will often be the hardest, since the architecture assets available for re-use will be relatively scarce

Front 77

Which phases are the "arch development phases" and what are the common steps for these phases?

Back 77

Phase B, C, & D

-Select reference models, viewpoints, and tools

-Develop Baseline Architecture Description

-Develop Target Architecture Description

-Perform gap analysis

-Define candidate roadmap components

-Resolve impacts across the Architecture Landscape

-Conduct formal stakeholder review

-Finalize the Architecture

-Create Architecture Definition Document

Front 78

Describe the ADM version # convention

Back 78

Phase A docs are 0.1

Phase B, C, and D are 1.0

Front 79

Does the order of the phases matter?

Back 79

the order is to some extent dependent on the maturity of the architecture discipline within the enterprise.

OR may also be defined by the architecture principles and business principles of an enterprise.

Front 80

Name some reasons for adapting the ADM

Back 80

-ADM is one of many F/Ws in the enterprsie

-ADM is mandated for contractors so need to collaborate

-the enteprise is smaller

-the enterprise is larger

Front 81

What is a product line architecture?

Back 81

In a vendor or production environment, a generic architecture for a family of related products

Front 82

What are the major ADM info areas managed by a governance approach?

Back 82

1 - reference data including external data

2 - process status

3 - audit information including decisions

Front 83

Why Scope the architecture?

Back 83

limits on

1 - organizational authority

2 - objectives and stakeholder concerns

3 - availability of people, resources, and so on

Front 84

What is an architectural partition?

Back 84

mechanism to make sure duplicate work does not happen

Front 85

What are the four dimensions use to limit scope?

Back 85

Breadth

Depth

Time Period

Arch Domains

typically focus is on B/D/T and then determine extent of domains

Front 86

In a complex environment, what/why is an alterntaive to a single ent arch?

Back 86

If thought of as too complex/unwieldy then use a number of different ent architectures

"Federated Ent Arch"

Front 87

Define the publish/subscribe model for ent arch scope

Back 87

a way to roll out arch governance

agreed on quality of materials

use of materials monitored

Front 88

SCOPE DEPTH - needs to be sufficient to express future tailoring/re-use/ extention

Back 88

--

Front 89

Architecture Integration

Back 89

Architectures to address a set of enterprise issues need a consistent frame of reference

Front 90

What is EA?

Back 90

EA is a management discipline that provides a clear line-of-sight from strategicbusiness objectives to underlying business and technology enablers

EA aim: facilitate and improve thebusiness decision making process byrevealing how complex organizations

EA is: description of the current and/orfuture structure

Front 91

What are common drivers for EA

Back 91

business, technical, and financial challenges

-Business Challenges‒ Redundant processes‒ Increasing customer demands‒ Multiple customers, stakeholders & partners

-Technical Challenges‒ Redundant data & applications‒ Heterogeneous technologies (old & new)‒ Stove-piped systems‒ No standardization

-Financial Challenges‒ Increasing costs (Internal & External)‒ Budget shortfalls

Front 92

What are some questions that EA focuses on to enable decision making?

Back 92

What does the existing enterprise look like?

What are oppty to increase performance?

Are resources sufficiently allocated?

Can solutions be streamlined or shared?

What standards should be enforced?

What costs can be reduced?

Front 93

When is EA relevant on a consulting project?

Back 93

for consulting projects aimed atoptimizing the often fragmented legacy of processes (both manual and automated), transformingbusinesses into integrated environments responsive to change, or supporting the delivery of thebusiness strategy.

Front 94

What are the components of a successful EA program?

Back 94

Governance

An EA methodology•

EA descriptive layers (e.g. framework)

Program management plans

Principles and standards

These form the as-is, to-be, and transition

Front 95

Define Framework

Back 95

Comprehensive classification scheme for organizing modeling approach, policies,standards, methods and tools into a synergistic infrastructure

Front 96

Define Policy

Back 96

Formal ground rules for managing & utilizing information resources

Front 97

Define Standards

Back 97

Formal measures to manage & control the quality of IT resources; addressing form, contentand quality

Front 98

Define Method

Back 98

Specified procedures for development, maintenance and control of information outputs;data & process modeling and testing methods

Front 99

Define Tools

Back 99

Comprehensive set of tools to assist the development, management & control of theinformation resources; architecture modeling, dictionary/repository, CASE and modelingtools

Front 100

What is an EA methodology including some examples

Back 100

Describes the process (how) the EnterpriseArchitecture is implemented including:‒ Who‒ How‒ When

Examples: • Centralized Approach

• Federated/Hybrid Approach

• Mission Based Approach

• Pattern Based Approach

• Hypothesis-drivenApproach

Front 101

What is an EA framework and include examples

Back 101

Describes the deliverables & products used torecord information about each layer of theorganization

Examples :• FEAF (Federal EnterpriseArch. Framework)

• Zachman Framework• DoDAF

• TEAF (Treasury Ent. Arch.Framework)

Front 102

T/F: Togaf is methodology AND framework

Back 102

True dat!

Front 103

Phase B = which domain?

And why does it matter?

Back 103

Business Arch (B in BDAT)

foundation on which all other domain architectures are built

Front 104

What are inputs to business?

Back 104

LOOK up all 11

Front 105

What are the steps to Bus Arch?

Back 105

1. select reference model/'view point, tools

2. develop baseline

3. develop target - builds on the vision v0.1

4. gap analysis

5. define candidate roadmap

6. resolve impacts across landscape

7. stakeholder review

8. finalize

9. arch definition document

Front 106

outputs to Bus Arch?

Back 106

1. refined phase A deliverables

2. draft arch defn doc (baseline & target) v1.0

3. draft arch requirements spec and gap analysis

4. business arch components of arch roadmap

Front 107

names some business artifacts

Back 107

catalogs - org, actor, driver, business serivce, role, location, events

matrices - business interaction, actor/role

diagrams - business footprint, product lifecycle., use-case diag, process flow diag

words

Front 108

What are some of the processes/domains to be identified and understood during the preliminary phase?

Back 108

current methods for architecture description

Current project management frameworks and methods

Current systems management frameworks and methods

Current project portfolio management processes and methods

Current application portfolio management processes and methods

Current technology portfolio management processes and methods

Current information portfolio management processes and methods

Current systems design and development frameworks and methods

Front 109

When you are in prelim phase and are trying to understand organizational context, what are some areas to tailor for the selected F/W?

Back 109

-level of formality and rigor applied

-level of sophistication/expenditure required

touch points w/ other -organizations/process/roles/responsibilities

-focus of content coverage

Front 110

list some examples of imperatives that drive requirements for architectural work

Back 110

Business requirements

Cultural aspirations

Organization intents

Strategic intent

Forecast financial requirements

Front 111

Are architectural principles based on business principles?

Back 111

Yes, in part, though business principles are defined outside the scope of arch function.

Front 112

What other F/W much coexist with TOGAF?

Back 112

Business capability mgmt

Project/portfolio mgmt

ops mgmt

solution development mgmt

Front 113

describe the interoperabilty between f/w for an enterprise

Back 113

Front 114

The enterprise is a system of systems

Back 114

The enterprise is a system of systems

Front 115

Why do you use an capability maturity model?

Back 115

to assess the ability of the enterprise to exercise different capabilities

examples: NASCIA and US Dept of Commerce ACMM

Front 116

in the prelim phase, how to you scope the enterprise org impacts?

Back 116

Identify:

-core enterprise units - most affected and achieve most value from the work

-soft enterprise units - will see changes as result of working with core

-extended enterprise - outside scope

-communities involved

-governance involved (legal frameworks / geographies

Front 117

in Prelim phase, describe how/why confirm governance / FW

Back 117

need to understand how arch material is brought under governance (what type of repository, what are mandates for repository, what are relationships and who reports on status, ownership

Front 118

What aspects of TOGAF do you tailore during prelim?

Back 118

-terminology tailoring

-process tailoring

-content tailoring

Front 119

What are the outputs of prelim?

Back 119

-Org Model

-Tailored Arch F/W

-Initial arch repository

-restatement of business principles, goals and drivers

-request for arch work

-governance F/W

Front 120

When does phase A start?

Back 120

With receipt of request for arch work from sponsor

Front 121

What is the key activity of Phase A

Back 121

-ensuring that existing definitions are current, and clarifying any areas of ambiguity

-ensuring that the existing principles definitions are current, and clarifying any areas of ambiguity.

Front 122

What benefit does the sponsor get from the architectural vision?

Back 122

provides key tool to sell the benefits of the proposed capability to stakeholders

describes now new capability meets business goals/ strategic objectives

Front 123

what are key elements of the arch vision

Back 123

enterprise mission, vision, strategy, and goals

Front 124

NOTE: if there is little existing EA assets, during Phase A , may need to establish

Back 124

OR during prelim... much latitude on when things happen

Front 125

What is the ADM approach for creating business scenarios?

Back 125

it is a "method w/in a method"...

Front 126

What are the inputs to Phase A

Back 126

-reference materials: organizational model

-non-arch: request for arch work; principles, goals, drivers

-Arch inputs: org model, maturity model, tailored arch framework

populated repository

NOTE: These are tied to outcomes of prelim

Front 127

Level of detail for Phase A depends on ??

Back 127

scope and goals of request for arch work

Front 128

What are the steps in Phase A?

Back 128

11 Steps

7.4.1 Establish the Architecture Project

7.4.2 Identify Stakeholders, Concerns, and Business Requirements

7.4.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints

7.4.4 Evaluate Business Capabilities

7.4.5 Assess Readiness for Business Transformation

7.4.6 Define Scope

7.4.7 Confirm and Elaborate Architecture Principles, including Business Principles

7.4.8 Develop Architecture Vision

7.4.9 Define the Target Architecture Value Propositions and KPIs

7.4.10 Identify the Business Transformation Risks and Mitigation Activities

7.4.11 Develop Statement of Architecture Work; Secure Approval

Front 129

Describe establishing the arch project (phase A)

Back 129

keep P< f/w in mind

secure recongnition of the porject and endorsement

Front 130

What are the 3 key objectives during phase A WRT stakeholder/concern identification and what is the primary product?

Back 130

Identify candidate vision components and requirements to be tested

identify candidate scope boundaries for the engagement

identify stakeholder concerns, issues, and cultural factors

PRODUCT: stakeholder map

Front 131

What is included in the stakeholder map?

Back 131

concerns, viewpoints, some aspects of communications plan

key roles/responsibilities

Front 132

T/F - during arch vision, new requirements may be generated

Back 132

yes and they must be managed and scoped appropriately

Front 133

why assess readiness for business transformation

Back 133

augment capability assessment used to shape scope of architecture

Front 134

What are the key steps to defining target arch value proposition/KPI?

What is the output?

Back 134

Develop the business case for the architectures and changes required

Produce the value proposition for each of the stakeholder groupings

Assess and define the procurement requirements

Review and agree the value propositions with the sponsors and stakeholders concerned

Define the performance metrics and measures to be built into the enterprise architecture to meet the business needs

Assess the business risk

outputs are incorporated into statement of work

Front 135

What are the two levels of risk?

Back 135

initial level of risk

residual level of risk

Front 136

during Phase A - develop statement of arch work, you will need to assess work products. what are two items you need to ensure in order to assess the work products

Back 136

performance metrics are built in

specific performance work products are available.

Front 137

What are outputs of Phase A?

Back 137

approved statement of arch work

refined business principles, goals and drivers

arch principles

capability assessment

arch vision

tailored arch framework (method, content, tools)

communications plan

Front 138

what are the objectives of Phase B?

Back 138

develop target business arch

identify candidate arch roadmap components to fill gaps

Front 139

T/F - Business arch is prerequisite for any other arch domain (B-D-A-T)

Back 139

True - it also demonstrates value

Front 140

Name some business models used during Phase B

Back 140

-activity models/ business process models

-use case models

-class models (similar to logical data models, describe static information and relationships)

-node connectivity diagram

-info exchange matrix ( includes performance/security and ownership)

NOTE: All can be represented using UML

Front 141

Name inputs to Phase B

Back 141

org model

tailored F/W

approved stateme of arch work

arch principles

enterprise continuum

arch repository

arch vision

draft arch defn doc (0.1 versions)

Front 142

What are the steps in Phase B?

Back 142

8.4.1 Select Reference Models, Viewpoints, and Tools

8.4.2 Develop Baseline Business Architecture Description

8.4.3 Develop Target Business Architecture Description

8.4.4 Perform Gap Analysis

8.4.5 Define Candidate Roadmap Components

8.4.6 Resolve Impacts Across the Architecture Landscape

8.4.7 Conduct Formal Stakeholder Review

8.4.8 Finalize the Business Architecture

8.4.9 Create Architecture Definition Document

Front 143

What are some modeling processes used to support view points during Phase B?

Back 143

structured analysis

use-case analysis

process modeling

Front 144

What are sub-steps for selecting reference models/viewpoints/tools in Phase B?

Back 144

-determine overall modeling process

-identify service granularity level, boundary/contracts

-identify catalogs of business building blocks (generally based on attributes of metamodel entities)

-identify matrices & diagrams

identify requirements to be collected

Front 145

What are outputs of Business Arch Phase B?

Back 145

refined arch vision

draft arch defn doc

draft requirements spec

busines arch components

catalogs/matrices/diagrams

Front 146

What are the objectives of Phase C?

Back 146

-develop target info system arch (data and app)

-identify arch roadmap

Front 147

What are inputs to Phase C?

Back 147

org model,

tailored F/W

**Application principles

**Data principles

statement of arch work

arch vision

repository

draft arch defn doc

draft requirements spec

business arch components of arch roadmap

Front 148

What are outputs of Phase C?

Back 148

refined arch vision

draft arch defn doc V1.0

draft requiremenst spec

info system components of an arch roadmap

Front 149

What are the objectives of the data arch of Phase?

Back 149

develop target data arch

identify candidate arch roadmap

Front 150

What are key considerations for data architecture?

Back 150

data management

data migration

data governance

repository - there are data standards based on industry

Front 151

During Phase C, what are key considerations for data management

Back 151

-which components are system of record or reference for master data

-is there enterprise-wide standard for all app components

-what are data entries used by business processes/functions/services

-software needs for data integration

Think backups!

Front 152

Name 3 types of data migration?

Back 152

master, transnational and reference

Front 153

During Phase C- Data arch, what are 3 dimensions of data governance

Back 153

structure, management system, people

Front 154

What are the steps for addressing Phase C- Data Arch

Back 154

NOTE: all steps must be closed during finalize data arch step and outputs published.

-Select Reference Models, Viewpoints, and Tools

-Develop Baseline Data Architecture Description -(should be able to leverage existing standards)

-Develop Target Data Architecture Description

-Perform Gap Analysis

-Define Candidate Roadmap Components

-Resolve Impacts Across the Architecture Landscape

-Conduct Formal Stakeholder Review

-Finalize the Data Architecture

-Create Architecture Definition Document

Front 155

During Phase C - data arch, what are key sub-steps for modeling?

Back 155

Collect data-related models

Rationalize data requirements and align with any existing enterprise data catalogs and models;

Update and develop matrices by relating data to business service, business function, access rights, and application

**Elaborate Data Architecture views by examining how data is created, distributed, migrated, secured, and archived

Front 156

What catalog should be created for data architecture and housed in the repository?

Back 156

data entity/data component

Front 157

Name a few Data Arch matrices.

Back 157

- Data Entity/Business Function

-Business Service/Information

-Application/Data

Front 158

Name a few diagrams to develop for data architecture.

Back 158

Conceptual Data diagram

Logical Data diagram

Data Dissemination diagram

Data Lifecycle diagram

Data Security diagram

Data Migration diagram

Front 159

Once data arch is finalized, the impacts on the arch landscape need to be resolved. explain

Back 159

impact on pre-existing arch?

opportunities to leverage this work in other places in the enterprise

will this be impacted by other projects

Front 160

Name some data arch items in the arch defn doc...

Back 160

-Business data model

-Logical data model-

-Data management process model

-Data Entity/Business Function matrix

-Data interoperability requirements (e.g., XML schema, security policies)

Front 161

What are the objectives of the app arch or Phase C?

Back 161

-develop target app arch

-identify candidate arch roadmap to fill taps

Front 162

During Phase C - App Arch - what are some inputs from the arch repository?

Back 162

-Re-usable building blocks

-Publicly available reference models

-Organization-specific reference models

-Organization standards

III-RM from TOGAF

Front 163

What are the steps for Phase C App Arch?

Back 163

11.4.1 Select Reference Models, Viewpoints, and Tools

11.4.2 Develop Baseline Application Architecture Description

11.4.3 Develop Target Application Architecture Description

11.4.4 Perform Gap Analysis

11.4.5 Define Candidate Roadmap Components

11.4.6 Resolve Impacts Across the Architecture Landscape

11.4.7 Conduct Formal Stakeholder Review

11.4.8 Finalize the Application Architecture

11.4.9 Create Architecture Definition Document

Front 164

Identify required catalogs for Phase C - App Arch?

Back 164

-Application Portfolio catalog

-Interface catalog

Front 165

Identify some matrices of the Phase C - App Arch...

Back 165

-Application/Organization matrix

-Role/Application matrix

-Application Interaction matrix

-Application/Function matrix

Front 166

Name a few app arch diagrams to develop during Phase C - App Arch

Back 166

-Application Communication diagram

-Application and User Location diagram

-Enterprise Manageability diagram

-Process/Application Realization diagram

-Application Migration diagram

-Software Distribution diagram

-Software Engineering diagram

-Application Use-Case diagram

Front 167

NOTE: INPUTS for PHASE C are outputs of Prelim, A and B

Back 167

Always leverage the repository

Front 168

Does the TOGAF offer templates?

Back 168

Yes - https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp?catalogno=i093

Front 169

NAme a few App Arch Artifacts

Back 169

catalogs: app portfolio, interface

matrices - app/ org matrix, role/app

Diagrams - app communication, app use location, enterprise manageability diagram

Key words: application, interface, software

Front 170

Phase D - Tech arch - what is key purpose?

Back 170

identify baseline and target tech arch V1.0

Front 171

What is the approach for Phase D?

Back 171

go to Arch repository and check for

-existing IT services

-TOGAF Tech Reference Model (TRM)

-Generic industry tech models

Front 172

What are some Phase D artifacts?

Back 172

Catalogs - tech standards

Matrices - app/tech matrix

Diagrams - environment/locations diagram, decomposition diagram, communications engineering diagrams

Key words: technology, network, hardware, environment, platform, communication

Front 173

Objectives of Phase E

Back 173

-complete initial version of arch roadmap based on gap analysis of BDAT

-determine if incremental approach

-formulate implementation and migration strategy (is a transitional arch needed)

-identify and group work packages

Front 174

What is the approach to Phase E (opportunities and solutions)?

Back 174

Figure out how to deliver target arch:

-arch roadmap

-work packages

-transitional arch

-implementation and migration plan

Front 175

Inputs are the same for Phase E with exception of what?

Back 175

product information (COTS)

change requests for business programs/projects

Front 176

What are the steps for Phase E??

Back 176

-determine key corporate change attributes

-determine business constraints

-review and consolidate gap analysis of Phase B-D

-consolidate requirements

-validate dependencies

-consolidate inter-operability requirements

-confirm readiness/risk

-formulate impl/migration strategy

-work package grouping

-identify transition arch

***Create arch roadmap & the implementation/migration plan

Front 177

Unique Phase E outputs?

Back 177

baseline/target V1.0

arch roadmap V0.1

Implementation and migration plan v0.1

Front 178

Only two artifacts of Phase E, what are they?

Back 178

Product context diagram, benefits diagram

Key Word: "Benefits"

Front 179

Phase E concentrates on HOW to deliver architecture

Back 179

NOTE: the roadmap should be best-fit

Front 180

Phase E is the first step for the creation of what?

Back 180

implementation and migration strategy

Front 181

What are some migration strategies?

Back 181

greenfield

revolutionary

evolutionary

Front 182

What are a few common migration methodologies?

Back 182

quick win

achievable target

value chain

Front 183

What is Phase F?

Back 183

Migration Planning

Front 184

What are Phase F objectives?

Back 184

-Finalize arch roadmap and implemmentation plan

-ensure plan coordinated with enterprise change approach

-ensure business value understood by stakeholders

-think through implementation costs, resources, timing

-Transition from developing arch to implementing

Front 185

What is the approach for Phase F?

Back 185

create implementation and migration plan

Front 186

what are inputs for Phase F?

Back 186

reference: arch repository

non-arch: request for arch, capability assessment, comms plan

arch: org models, governance models, tailored F/W, SOAW, Arch vision, arch repository, draft arch defn doc; draft requirements spec, CRs, V0.1 roadmap, Business and IT capability assessment

Front 187

What are Phase F Steps?

Back 187

-confirm mgmt f/w interactions

-assign business values to each work package

-estimate resource requirements/timings

-prioritize

-confirm arch roadmap and update arch defn doc

-generate impl and migration plan

-complete arch development and lessons learned

-

Front 188

What are document outputs of Phase F?

Back 188

-implementation plan V1.0

-finalized: arch defn doc; arch requirements, and arch roadmap

-reuseable ABBs

-gather requests for arch work for next cycle of ADM

-implement governance model

-change requests for arch capabilities

-project charters

Front 189

What is an ABB?

Back 189

Arch building block (non-tech per se)

Front 190

For Phase F, one step is confirming mgmt F/W interactions... explain

Back 190

4 frameworks typically involved:

-Business planning

-EA

-PPM

-Ops MGMS

Front 191

During Phase F, business value is assigned to work packages. What are some issues to address during this process?

Back 191

-performance evaluation criteria to monitor transformation

-ROI Criteria

-Business value defn

-Critical Success Factors

-Measures of Effectiveness (MOE_

-Strategic Fit

Front 192

How are SBBs used for migration planning?

Back 192

Used during prioritization

determine net benefit of SBB delivered and validate risks effectively mitigated

Front 193

What is involved in Phase G?

Back 193

ensure conformance with target arch

governance duties

handling CRs for implementation team

update baseline arch as changes implemented

Front 194

When does Phase G end?

Back 194

When solutions are fully deployed

NOTE: can be long phase

Front 195

What are the objectives of Phase G?

Back 195

1- Ensure implemetation conforms with target arch

2- perform appropriate arch governance functionsl

Front 196

What is the approach for Phase G?

Back 196

-establish implementation program for transition arch

-phased deployment schedule that reflects arch roadmap

-follow standards for governance

-use project/portfolio mgmt approach

-define operations F/W

Front 197

Inputs (documents)

Back 197

All existing docs to date

Front 198

What are Phase G steps?

Back 198

-Confirm scope and priority

-Identify deployment resources/skills

-Guide development of solutions deployment

-Perform EA compliance reviews

-Implement business and IT Ops

- Post Imp review and closure

Front 199

What are outputs of Phase G?

Back 199

-Architecture contract - agreements between development partners and sponsors on

(chapter 49)

-Compliance Assessments

-CRs

-Arch compliant solutions deployed

Front 200

Name key aspects of deploying an arch compliant solution

Back 200

-populated arch repository

arch compliance recommendations

recommendations on service delivery requirements

recommendations on performance metrics

SLAs

update Arch Vision

Arch defn doc up[dated

ops models updated

Front 201

Where does Phase H generally occur?

Back 201

Last Phase of ADM

Front 202

What's involved in Phase H?

Back 202

-keep arch alive

-ensure arch governance happening

-ensure arch capability maintained

monitoring and track changes

Front 203

Objectives of Phase H (change mgmt)

Back 203

-ensure arch livecycle maintained

-ensure arch governance F/W executed

-ensure arch capability meets requirements

Front 204

Describe the approach to Phase H

Back 204

-drivers for change - react to reality

-Change mgmt process determines how changes handled

-how to determine simple maintenance versus ADM cycle

Front 205

Phase H inputs?

Back 205

all same + Change Requests - tech changes, business changes, lessons learned

Governance model

Front 206

What are Phase H steps??

Back 206

-establish value realization process

-deploy monitoring tools

-manage risk

-provide analysis for arch change mgmt

-develop change requirements to meet performance targets

-manage governance process

-activate process to implement changes

Front 207

Outputs of Phase H?

Back 207

arch updates

changes to arch F/W

changes to arch principles

new request for arch work

update SOaW

Update arch contract

update compliance assessments

Front 208

Monitoring business growth/decline is an aspect of Phase H - change management - why?

Back 208

need to understand if EA continues to work for tomorrow

Front 209

What role does capacity measurement have in EA and in what phase is it monitored?

Back 209

Monitored in phase H - used to determine if EA still bringing maximum business value

Front 210

What is an arch compliance report and when is it created?

Back 210

created during phase H

states if change is compliant to current arch and if non-compliant, why exempt and what future plan is

Front 211

What are the three ways to change existing infrastructure?

Back 211

strategic - top down (capital)

bottom up - operations and maint)

experience based incremented by ops mgmt

Front 212

What is an RFC?

Back 212

request for change

Front 213

What are tech related drivers for arch CRs?

Back 213

new tech reports

asset mgmt cost reduction

tech withdrawal

standards initiatives

Front 214

What are business drivers for arch CRs?

Back 214

business-as-usual development

business exceptions

business innovations

business tech innovation

strategic change

Front 215

What are the three categories of changes?

Back 215

simplification change - reduce investment

incremental change - get additional value

re-architecting change - increase investment for new value

Front 216

What are activities are undertaken to determine the category of change?

Back 216

-Registration of all events that may impact the architecture

-Resource allocation and management for architecture tasks

-The process or role responsible for architecture resources has to make assessment of what should be done

-Evaluation of impacts

Front 217

Describe rules-of-thumb for maintenance over redesign WRT CRs.

Back 217

-If change impacts two stakeholders or more, architecture redesign

If impacts only one stakeholder, change management.

If the change can be allowed under a dispensation, then change management.

Front 218

What are inputs to Phase H - Change Management?

Back 218

Everything to date!

Front 219

During Phase H, what things could you monitor with tools?

Back 219

-technology changes --> impact the Baseline Architecture

-business changes --> Baseline Architecture

-Business value tracking

-enterprise Architecture Capability maturity

-asset management programs

-QoS performances and usage

-business continuity requirements

Front 220

When does requirements management occur during ADM?

Back 220

continuously

all the time for all phases

in response to many things including new competitor, new legislation, disproven assumptions, no company policy or missed requirement

Front 221

What are the objectives of requirements management

Back 221

ensure sustained req. mgmt process operates for entire ADM and are available for each phase when needed

Front 222

Describe the Approach to requirements mgmt...

Back 222

-center of hub

-architecture should identify which requirements relevant to which phase

-no specific tool recommended by TOGAF

Front 223

What is different about the steps steps involved in requirements management?

Back 223

-manage interactions between requirements and phases

-steps are continuous

-steps are assigned to either req. mgmt or adm phase

Front 224

What are the requirements management steps?

Back 224

-identify/document (from ADM)

-base on baseline req, determine priorities.

-confirm stakeholder buy-in

-monitor baseline

-identify Change requirements (from ADM)

-identify Change requirements (non-ADM)

-Assess impact

-implement Phase H outcomes

-update requirements repository

-implement change in current ADM phase

-revise gap analysis

Front 225

name the outputs of requirements management

Back 225

requirement impact assessment

arch requirement spec

Front 226

what are the artifacts of requirements management

Back 226

there are none

Front 227

Can the requirements repository hold requirements from multiple ADM cycles?

Back 227

Yes

Front 228

When are high level requirements gathered?

Back 228

during architectural vision - phase A

Front 229

What are the two kinds of requirements?

Back 229

functional and non-functional

Front 230

when defining requirements, what other aspects should be taken into account?

Back 230

-Assumptions for requirements

-Constraints for requirements

-Domain-specific principles that drive requirements

-Policies affecting requirements

-Standards that requirements must meet

-Organization guidelines for requirements

-Specifications for requirements

Front 231

Know the requirements steps in 17.4 of the TOIGAF

Back 231

requirements management steps versus ADM Phase steps

Front 232

Which phase is recognized as the "final phase" of defining enterprise arch?

Back 232

Phase F - when switch from arch to implementation governance

Front 233

What is the enterprise continuum?

Back 233

-a view of the arch repository

-classifying arch and solution artifacts

-from generic to specific

-contains arch continuum and solutions continuum

"[...] a view of the Architecture Repository that shows the evolution of these related architectures from generic to specific, from abstract to concrete, and from logical to physical"

"Enterprise Continuum is as a view of the repository of all the architecture assets"

Front 234

What is the arch repository?

Back 234

contains all building blocks that go into architecture

"empty box you fill with arch outputs"

tool that allows you to classify artifacts

a matrix with generic to specific (left to right)

from arch to solutions (AAB on top, SBB on bottom)
(

Front 235

What is foundation architecture?

Back 235

generic / arch continuum

like TFM or SIB

Front 236

What is common systems arch?

Back 236

less generic / arch continuum

Front 237

What is industry arch?

Back 237

more specific/ arch continuum

managed by industry group

e.g. credit card processing

Front 238

What is org specific arch?

Back 238

most specific/ arch continuum

your business services and function

only for your business

Front 239

what are the 4 levels of specificity of arch continuum?

Back 239

Foundation arch --> common Systems arch --> Industry arch --> Org Specific arch

Front 240

what are the 4 levels of specificity of solutions continuum?

Back 240

Foundation solutions--> common Systems arch --> Industry arch --> Org Specific arch

Front 241

what is a foundational solution

Back 241

generic/solutions continuum

generic solutions

e.g. programming languages, ITIL, operating systems

Front 242

what is a common systems solution

Back 242

product on top of foundational

generic but with some details

e.g. MS Office, firewall software

applicable across industry

Front 243

what is an industry solution?

Back 243

solutions continuum/more specific

the solution is industry specific like a COTS credit card processing software

Front 244

what is an org specific solution?

Back 244

your customization

specific to your business

Front 245

What are the two primary TOGAF reference models?

Back 245

Technical Reference Model (TRM) and the Integrated InformationInfrastructure Model (III-RM)

Front 246

What is contained in the enterprise continuum?

Back 246

it can contain architecture descriptions, models, building blocks, patterns, viewpoints, and other artifacts - that exist both within the enterprise and in the IT industry at large,

Front 247

Back 247

Front 248

What are the three distinct continua in the enterprise continuum?

Back 248

enterprise continuum

architectural continuum

solutions continuum

Front 249

Describe the Overarching Enterprise Continuum

Back 249

-outermost

-contains assets that may influence arch but not directly used by ADM

-policies, standards, strategic initiatives, org structures

- contextual factors: regulatory change, tech advances, competitor activity

contains two specializations: arch and solution

Front 250

Describe the architectural continuum.

Back 250

-a consistent way to describe the generic -rules/relationships.

-includes reusable assets (AABs)

shows relationships among foundational frameworks like TOGAF

useful for discovery to uncover commonality

Front 251

describe the solutions continuum

Back 251

-describes the implementation of what is described in the arch continuum

-contains SSBs

Front 252

what is the difference between ABB and SBB

Back 252

ABBs are defined in relation to a set of contextual factors and then realized through SBBs.

Front 253

Where does the TRM fall on the architectural continuum?

Back 253

foundational architecture

Front 254

describe common system arch

Back 254

Common Systems Architectures guide the selection and integration of specific services from the Foundation Architecture to create an architecture useful for building common (i.e., highly re-usable) solutions across a wide number of relevant domains.

Front 255

give examples of common systems arch

Back 255

a security architecture, a management architecture, a network architecture, an operations architecture, etc.

Each is incomplete in terms of overall system functionality, but is complete in terms of a particular problem domain

TOGAF III-RM is a common sys

Front 256

What are characteristics of common systems arch?

Back 256

-Reflects requirements specific to a generic problem domain

-Defines building blocks specific to a generic problem domain

-Defines business, data, application, or technology standards for implementing these building blocks

-Provides building blocks for easy re-use and lower costs

Front 257

Describe industry architectures

Back 257

-integration of common architectures...

-guides the creation of industry solutions for targeted customer problems within a particular industry.

Front 258

what are some characteristics of an industry architecture?

Back 258

-Reflects requirements and standards specific to a vertical industry

-Defines building blocks specific to a generic problem domain

-Contains industry-specific logical data and process models

-Contains industry-specific applications and process models, as well as industry-specific business rules

-Provides guidelines for testing collections of systems

-Encourages levels of interoperability throughout the industry

Front 259

Describe an org specific architecture.

Back 259

-describes and guides the final deployment of solution components for an enterprise

provides a way to communicate and manage business across all 4 arch domains

Front 260

What is the solutions continuum?

Back 260

the detailed specification and construction of the architectures at the corresponding levels of the Architecture Continuum

- A populated repository based on the Solutions Continuum can be regarded as a solutions inventory or re-use library,

Front 261

Back 261

Front 262

describe the relationship between the solutions and arch continuum

Back 262

guidance, direction, and support.

Front 263

The Enterprise Continuum presents mechanisms to help improve productivity through leverage. The Architecture Continuum offers a consistent way to understand the different architectures and their components. The Solutions Continuum offers a consistent way to understand the different products, systems, services, and solutions required.

Back 263

The Enterprise Continuum presents mechanisms to help improve productivity through leverage. The Architecture Continuum offers a consistent way to understand the different architectures and their components. The Solutions Continuum offers a consistent way to understand the different products, systems, services, and solutions required.

Front 264

what are the 4 areas included in an architectural capability assessment

Back 264

business

IT

arch maturity

business transformation

created in phase A; updated in Phase E

Front 265

Where are results of arch capability assesment stored?

Back 265

in governance log

Front 266

What is stored in the governance log?

Back 266

decisions

compliance assessments

capability assessments

calendar

project portfolio

performance measurements

Front 267

Describe Business Capability Assessment

Back 267

capabilities of business

baseline state assessment of performance

future state aspiration

how capability is realized (baseline or future)

likely impacts to business if target arch is realized

Front 268

describe IT capability

Back 268

baseline / target maturity of change process

baseline/target maturity of operational process

capability and capacity assessment

likely impacts if target arch realized

Front 269

Arch Maturity Assessment

Back 269

-arch governance processes/org/roles/responsibilities

-arch skills assessment

-breadth/depth/quality of landscape defn

-breadth/depth/quality of standards defn

-breadth/depth/quality of reference models

assessment of re-use potential

Front 270

Business Transformation Readiness Assessment

Back 270

-readiness factors

-vision for readiness factors

-current/target readiness ratings

-readiness risks

think "organizational change mgmt"

Front 271

define Stakeholders

Back 271

an individual, team or organization with interests or concerns with the outcomes of the architecture

Front 272

define view

Back 272

representation of a related set of concerns

may be represented by a model

does not need to be visual/graphic in nature

demonstrates area of interest to stakeholders

Front 273

provide examples of views

Back 273

people

workflow view

business objects view

data entity view

cost view

hardware view

Front 274

define viewpoint

Back 274

a generic way to create a view

a view is what you see; a viewpoint is where you are looking from

"the vantage point or perspective that determines what you see"

Front 275

name some benefits of stakeholder mgmt

Back 275

-identify key players and get support

-help win more resources

-better communication / transparency

-better anticipate reactions

-identify competing

Front 276

what are the steps in stakeholder management?

Back 276

identify stakeholders

classify stakeholder positions

determine stakeholder mgmt approach

tailor engagement deliverables

Front 277

what are the most important stakeholders to identify

Back 277

influencers - well respected and moving up

Front 278

what a a few sample questions you would ask to assess stakeholder readiness to behave in a supportive manner?

Back 278

-Is that person ready to change direction and begin moving towards the Target Architecture? If so, how ready?

- Is that person capable of being a credible advocate or agent of the proposed enterprise architecture initiative? If so, how capable?

Front 279

What is the power matrix/grid for stakeholders?

Back 279

Front 280

what are 4 columns of a stakeholder map?

Back 280

stakeholder position

key concerns

class

catalogs/matrices/diagrams

Front 281

define governance

Back 281

practice why which architectures are controllled

"Governance is essentially about ensuring that business is conducted properly. "

Front 282

What is the hierarchy of governance?

Back 282

Corporate (Exec)

tech (CIT/CTO)

IT (linked to business goals)

Arch

NOTE: each can exist in multiple geographic levels as well

Front 283

what are the characteristics of governance?

Back 283

-discipline

-transparency

-independence

-accountability

-responsibility

-fairness

Front 284

What occurs during architectural governance

Back 284

-systems of controls over components/activities

-system to ensure compliance with standards and legal obligations

-process to support management of the controls/compliance

-accountability practices

Front 285

When does implementation governance occur? how does that differ from overall arch governance

Back 285

implementation governance happens in Phase G

arch governance is overarching

Front 286

What are the 6 processes of architectural governance?

Back 286

-policy management/take-on

-compliance

-dispensation (exceptions/waivers)

-monitoring/reporting

-business control

-env mgmt

NOTE: there are many layers of governance

Front 287

describe technology governance

Back 287

how an organization utilizes technology in the research, development, and production of its goods and services.

Front 288

What is IT Governance

Back 288

the framework and structure that links IT resources and information to enterprise goals and strategies

Institutionalizes best practices for planning, acquiring, implementing, and monitoring IT performance

NOTE: example IT F/W = COBIT

there is mapping of TOGAF to COBIT

Front 289

Is arch governance a board level responsibility?

Back 289

YES

Front 290

conceptual arch governance F/W

Back 290

Front 291

What is Policy Management and Take-on?

Back 291

"architecture amendments, contracts, and supporting information must come under governance through a formal process in order to register, validate, ratify, manage, and publish new or updated content"

Front 292

Describe Arch governance

Back 292

"Architecture governance is the practice and orientation by which enterprise architectures and other architectures are managed and controlled."

Front 293

What groups are typically invovled in arch governance org structure?

Back 293

-Global governance board

-Local governance board

-Design authorities

-Working parties

Front 294

Back 294

Front 295

What are the three key areas of architectural management?

Back 295

Develop, Implement, and Deploy

Front 296

What are some of the operational benefits of arch governance?

Back 296

-Integrates and institutionalizes IT best practices

-Aligns with industry frameworks such as COBIT

-Protects the underlying digital assets of the organization

-Promotes visible risk management

Front 297

What are key success factors of Arch Governance?

Back 297

-Best practices for the submission, adoption, re-use, reporting, and retirement of architecture policies, procedures, roles, skills, organizational structures, and support services

-Organizational responsibilities and structures to support the architecture governance processes and reporting requirements

-Integration of tools and processes to facilitate the take-up of the processes, both procedurally and culturally

-Control Criteria of the architecture governance processes, dispensations, compliance assessments, SLAs, and OLAs

-Internal and external requirements for the effectiveness, efficiency, confidentiality, integrity, availability, compliance, and reliability of all architecture governance-related information, services, and processes

Front 298

Reference Models --> not much on TOGAF L1 test aside from where they fit on continuum

Back 298

Reference Models --> not much on TOGAF test aside from where they fit on continuum

Front 299

What does III-RM stand for

Back 299

Integrated information infrastructure reference model

Front 300

What does TRM stand for

Back 300

technical reference model

universally applicable and can be used for any system arch (sooo generic)

Front 301

What are the three levels of the TRM

Back 301

applications --> app platforms --> communications infrastructure

Front 302

TRM details

Back 302

TRM is this graphic plus definitions of the terms here

Front 303

Where is TRM on arch continuum

Back 303

foundational

Front 304

Where is III-RM on arch continuum

Back 304

common systems arch

Front 305

III-RM

Back 305

Front 306

Describe Prelim Phase - Step 5 - Tailor TOGAF

Back 306

- TOGAF designed to be modified including terminology

- modify ADM to complement your enterprise

- update the arch content F/W templates as needed

Front 307

Describe Prelim Phase - Step 6 - Implement Arch tools

Back 307

-tools selected based on scale & arch maturity

-possible tool for arch repository

-anywhere from simple MS office to specialty tools

Front 308

Describe Prelim Phase - Step 1 - Scope

Back 308

figure out who is impacted:

-Core Ent/Units - direct

-Soft Enterprise - see change but not direct impact

-Extended enterprise - outside scoped enterprise that will see the changes

-Communities - groups of stakeholders

-Governance

Front 309

Describe Prelim Phase - Step 2 - Confirm Governance/FWs

Back 309

-assess current governance model

-figure out how arch docs will be brought under governance

-determine if governance changes needed

Front 310

Describe Prelim Phase - Step 3 - est Arch Team

Back 310

-Look @ existing enterprise and business capabilities

- Do a maturity assessment and id the gap -

key roles

-request process changes

-are there constraints on the arch work

-review w/ sponsors and AAB

- assess budget for arch team

Front 311

Describe Prelim Phase - Step 4 - arch principles

Back 311

-rules for designing arch

-don't change often

-foundation for governance

-gives way to say "no" for things that fall outside principles

Front 312

Describe the Phase A - Arch Vision Steps

Back 312

1 - establish arch proj

2 - id stakeholders/concerns/bus req

Front 313

Describe Phase A - Step 1 - establish arch project

Back 313

-create the project (same as other PM efforts)

-plan and manage using acceptable practices

secure recognition

Front 314

Describe Phase A - Step 2 - Identify Stakeholders/concerns

Back 314

- id the stakeholders & concerns (use matrix)

- gather business requirements

- figure out which view and viewpoints need to be dev'd

Front 315

Describe Phase A - Step 3 - confirm business goals/drivers/constraints

Back 315

-what are business goals and strategic drivers

- make sure definitions up to date and clear

defined constraints (time/budget/resources)

Front 316

Describe Phase A - Step 4 - business capabilities

Back 316

two bus capabilities -

1- ability of enterprise to develop and use arch

2 - baseline and target capabilities of the enterprise itself

- address any gaps in arch capability / go back to prelim phase if you need to

- include gaps/limitations into arch

Front 317

Describe Phase A - Step 5 - assess readiness

Back 317

- use TOGAF bus trans readiness assessment to figure out if can adapt to change

- results are inputs to defining target arch

Front 318

Describe Phase A - Step 6 - define scope

Back 318

-scope for arch itself (what's in and out)

-baseline & target often different detail levels; target needs to be more detailed

-include the breadth of the enterprise, lev of detail needed, address partitioning and arch domains as well as existing assets

Front 319

Define Phase A - Step 7 - confirm principles

Back 319

- make sure defns current

- secure endorsement for new itesm

Front 320

in Define Phase A ... which step is biggest

Back 320

Step 8!! - develop arch vision

Front 321

Define Phase A - Step 8 - Develop arch vision

Back 321

- based on inputs to date

- create high level (version 0.1) of baseline and target system (can be simple conceptual diagrams)

Front 322

Define Phase A - Step 9 - define arch value and KPIs

Back 322

- Develop business case

- Review value with stakeholders

-Define performance metric and measures to build in

-accept risk(s)

Front 323

Define Phase A - Step 10 - id transformation risks/mitigation

Back 323

identify risks of the arch vision

Two levels of risk:

1 - initial level of risk - prior to implementing mitigation

2- residual risk - after mitigation

*May include in SOW

Front 324

in Phase A - what is the most important step??

Back 324

Step 11 - develop SOarchW & get approvals

Front 325

Define Phase A - Step 11 - develop SOarchW & get approvals

Back 325

- Assess work products required (make sure metrics built in, make sure

- ?

- new work products?

- work products to changed?

- which domains to develop? (BDAT), views and level of detail

- assess resource requirements

- communications plan

- review and agree w/ sponsors; get approval

Front 326

Define Phase B - Step 1 - select reference models/viewpoints/tools

Back 326

-select reference models/viewpoints/tools from the repository

- select relevant viewpoint

- ID tools for modeling/analyzing/documenting

Step 1.1 - determine modeling process

Front 327

What are the different substeps for Phase B- Step 1.... select reference modes/VPs/tools

Back 327

Step 1.1 - determine modeling process

Step 1.2 - identify service granularity levels, boundaries

Step 1.3 Id catalogs

Step 1.4 Id matrices

Step 1.5 - Id diagrams

Step 1.6 - Id which type of requirements to collect

Front 328

What are the business Service granularity lkeveles

Back 328

-micro-level functions -boundaries no governance

-services- boundaries and governance

-macro-functions - no boundaries but governance

Front 329

Define requirements from a TOGAF POV?

Back 329

what does the target arch need to do to satisfy stakeholder concerns

Front 330

Describe Phase B- Step 2 - Develop Baseline Bus Arch

Back 330

baseline existing business architecture using models from step 1 to defined new baseline content

Front 331

Describe Phase B- Step 3 - Develop TARGET Bus Arch

Back 331

figure out level of detail and make sure the future arch supports the arch vision

use models as appropriate

Front 332

What is Phase B - Step 4 - gap analysis

Back 332

gap analysis of the business arch and make sure it supports principles/concerns/constraints

you also want to test models for completeness against the requirements

Front 333

What is included in Phase B - Step 5 - candidate roadmap?

Back 333

-extract differences from gap and make those features of the target

-need to prioritize activities

Front 334

What is included in Phase B - Step 6 - resolve impacts

Back 334

-understand wider impact even outside scope

- are there recent changes outside that need to be accounted for?

- is there an opportunity to share outside?

- is there impact on in-flight work?

Front 335

What is in Phase B - Step 7 - stakeholder review

Back 335

check and see if architecture conforms to the original SOaW then present to stakeholders

Front 336

What is in Phase B - Step 9 - finalize bus arch

Back 336

- check repository if there are standards for new ABB

-complete documentation and cross-check against the bus goals

- finalize products to date

Front 337

What is in Phase B - Step 10 - Create Arch def doc

Back 337

- document business block rationale

- create bus arch section of arch defn doc

including

--- business footprint

---description of bus functions

---mgmt footprint

---standards/rules/guidelines

---skills matrix and JDs

Front 338

Describe Phase C - Data Arch & Info Systems Arch

Back 338

Develop Baseline Data Arch

Same 9 steps as BArch

1- reference models/VPs/Tools

Front 339

What is involved in Data modeling? (Phase c- Step 1)

Back 339

1.1 - Determining overall modeling process

1.2 - identify catalogs of data building blocks (track from apps to business function to entities and create the data catalog)

1.3 - Identify matrices

1.4 - ID data diagrams (conceptual, logical, security )

1.5 - Data requirements

Front 340

NOTE: data arch & requirements are inputs to appl arch and so it comes first in phase c

Back 340

NOTE: data arch & requirements are inputs to appl arch and so it comes first in phase c

Front 341

Describe Phase C - Step 2 (Data)- Baseline data arch

Back 341

- Baseline existing to the level needed; much could carry forward

- use inputs from Step 1

Front 342

Describe Phase C - Step 3 (Data)- Target arch

Back 342

should support the arch vision

identify building blocks and use inputs from Step 1

Front 343

Describe Phase C - Step 4 (Data)- Define Gaps

Back 343

-Validate target and baseline including different views against one another

-make sure support principles/objectives

- test models for completeness

-ID the gaps

Front 344

Explain Phase C - Step 5 (Data)- Candidate Roadmap

Back 344

extract exact differences from the gap analysis

make them into features

use roadmap to prioritize activities

use to feed opportunities and solutions

Front 345

Explain Phase C - Step 6 (Data)- Resolve impacts

Back 345

- understand wider implications

- are there outside changes that need to be accounted for

-opportunity to share work with others outside our scope?

Front 346

Explain Phase C - Step 7 (Data) - stakeholder review

Back 346

- make sure the data arch conforms to original purpose and the SOarchW

- present to stakeholders

Front 347

Explain Phase C - Step 8 (Data) - finalize arch

Back 347

-check repository for standards for new building blocks

-complete documents

-cross check against business requirements

-finalize work products

Front 348

Explain Phase C - Step 9 (Data) - arch defn doc

Back 348

- document rationale

- prep data arch section of arch dfn doc

---business data model

---logical data model

---data management process

-- data entity/business function matrix

Front 349

Explain Phase C - Step 1 (App Arch) - select ref models/VP/Tools

Back 349

-select reference models/viewpoints/tools from the repository

- select relevant viewpoint

- ID tools for modeling/analyzing/documenting

Front 350

Describe the modeling steps for Phase C - Step 1 (app arch)

Back 350

1.1 - Determining overall modeling process

1.2 - identify catalogs of building blocks

NOTE: hierarchies of catalogs:

logical --> Physical --> service

1.3 - Identify matrices

1.4 - ID diagrams (conceptual, logical, security )

1.5 - define the types of app arch requirements needed (impacts data and tech arch)

Front 351

explain step 2 of Phase C app arch - baseline app arch

Back 351

- develop baseline app arch description

- may include existing assets that will carry over

- model step 1 models as necessary

Front 352

explain step 3 of Phase C app arch - define target arch

Back 352

-describe target arch v1.0

-make sure it supports the vision and target business and data arch

-leverage building blocks where you can

user models from Step 1

NOTE: APP And DATA are done side by side

Front 353

What's involved in Step 4 - gap analysis of app arch phase C?

Back 353

-Validate architectures including different views

-validate against principles/objectives/constraints

-test models for completeness

-ID gaps between target and baseline arch

Front 354

Explain Phase C - app arch - step 5 - roadmap

Back 354

-extract differences from gap and make those features of the target-need to prioritize activities

Front 355

Phase C (app arch) - step 6 includes what steps to resolve impacts

Back 355

-understand implications

-check if impacts outside your scope

-outside changes that impact your work?

-identify opportunities to share

-check other projects and know impacts

Front 356

Explain Phase c - step 7 for app arch - formal review

Back 356

- make sure conform to SOarchW

- business or data arch need to change?

Front 357

Explain Phase c - step 8 for app arch - finalize arch

Back 357

-check repository for standards for new building blocks

-complete documentation

-cross check with business requirements

Front 358

Explain Phase c - step 9 for app arch - arch defn doc

Back 358

document rationale

prep app arch section of arch dfn doc

Front 359

Explain Phase D - Technical Architecture... which letter in the BDAT acronym?

Back 359

T in the BDAT

Develop baseline tech arch v1.0

Develop target tech arch v1.0

identify gaps between baseline and target

Front 360

What is step 1 of Phase D - Technical arch?

Back 360

Select reference Models, viewpoints and tools

Front 361

Specific to step 1 of Phase D, what are the sub steps?

Back 361

1.1 determine modeling process

1.2 identify catalogs of tech building blocks

1.3 identity the required matrix: the application/technology matrix

1.4 ID diagrams (topology)

1.5 ID types of requirements to collect

1.6 select services needed

Front 362

Explain Phase D Step 2.... develop baseline tech arch

Back 362

describe the existing tech arch

pull out existing building blocks

much should exist... this is "physical stuff" that exists

Front 363

Explain Phase D Step 3.... develop target tech arch

Back 363

describe the target tech arch

make sure it supports the arch vision and the business/data arch

identify relevant building block ( if pre-existing)

use models from step 1 to develop the new tech arch

Front 364

Explain Phase D Step 4.... tech arch GAP analysis

Back 364

-look at baseline and compare to target state

-compare using principles, objectives, and constraints

-test for completeness against requirements

Front 365

Explain Phase D Step 5.... build candidate roadmap

Back 365

extract key differences from teh gap analysis and the features needed shoudl be on the roadmap

a tech roadway is needed to prioritize activities over the coming phases

Front 366

Explain Phase D Step 6.... resolve impacts for the tech arch

Back 366

-evaluate the wider implications

-check with architectures outside direct scope

-are there any additional outside changes that need to be considered

-can this work be shared?

-will this impact others?

Front 367

Explain Phase D Step 7... stakeholder review of the tech arch

Back 367

-make sure the tech arch conforms to the original purpose of teh project and the SOarchW

Front 368

Explain Phase D Step 8 , Finalize Tech Arch

Back 368

-select standards for the tech arch building blocks

-complete the documentation is finished

-cross check everything against business requirements

-final work products

Front 369

what is involved in Phase D Tech Arch Step 9 - create arch defn document

Back 369

- need to document the rationale

- prep the tech arch section of the comprehensive arch defn doc

Front 370

Phase E is called what?

Back 370

the opportunities and solutions step

Front 371

What is the purpose of Phase E?

Back 371

to get you to the first full a complete version of the arch roadmap (v1.

Front 372

What is included in step 1 of Phase E - confirm corporate change

Back 372

essentially, how can the architecture best be implemented to take advantage of the corporate culture... are they slow and need incremental rollout?

-Execute the business readiness transformation analysis

-then fill out the implementation factor assessment and deduction matrix

Front 373

What is the focus of Phase E Step 2 - Business Constraint?

Back 373

this is the step where you identify business drivers that could constrain rollout?

think about season rushes, budget issues and so on

Front 374

What is the focus of Phase E Step 3 - review and consolidate gap analysis results

Back 374

-create the gap/solution/dependency matrix

-identify potential solution building blocks and arch building blocks

-

Front 375

What are the activities during Phase E Step 4 - consolidate requirements

Back 375

-identify the minimal requirements that can lead to most effective target architecture

-figure out if the solution you are solving can be used by different LOBs

Front 376

Phase E Step 5 for the opportunity/solution phase is what focus area?

Back 376

-consolidate and reconcile Interoperability requirements

-identify any conflicts via two approaches: new building block or modify existing

Front 377

What is included in Phase e Step 6 of the opportunity/solution phase: refine/validate dependencies?

Back 377

identifying tasks that directly impact you such as a mandatory OS upgrade

Front 378

What is the complete list of steps for Phase E (there are 11!!)

Back 378

1

2

3

4

5 -

6 - refine and validate dependencies

7 - confirm readiness

Front 379

What is included in Phase E Step 7 - confirm readiness?

Back 379

review the transformation readiness assessment and figure out if it impacts the roadmap... if so, you need a risk mitigation plan

Front 380

What is included in Phase E Step 8 - formulate implementation/migration strategy

Back 380

3 implementation approaches: greenfield, revolutionary, evolutionary

revolutionary -- replace old with new (big bang)

3 mitigation approaches:

a. quick wins

b. achievable targets

c. value chain approach

Front 381

what are 3 implementation/migration mitigation strategies in Phase e?

Back 381

3 mitigation approaches: a. quick wins - what is the easiest item to deploy with most benefitb. achievable targetsc. value chain approach

Front 382

During Phase E - step 9 - what outputs are defined?

Back 382

Work packages, that is , groups of activities

to do this, fill in th esolution column of the consolidated gaps/solutions/dependencies matrix then classify each system: mainstream, contain, replace

Front 383

What are the classifications you apply when identifying work packages in Phase E?

Back 383

mainstream - part of the target future

contain - expect to replace in 3 years +/-

replace - new work package will replace old

Front 384

Phase 3 - Step 10: Identify transition architectures

Back 384

schedule work packages

figure out if there is an incremental approach... and if so, you will have transitional architectures (that is it brings an incremental business value)

an implement the easier activities first (the quick wins)

Front 385

what is included in Phase 3 - Step 11 - create arch Roadmap and implementation/migration plan

Back 385

consolidate workpackages and transition architectures into the roadmap V0.1

layout timelines fro baseline to Target

make sure each transition architecture has a clear set of outcomes.

Make sure you are always working to realize the roadmap.

Front 386

What is the name of Phase F?

Back 386

Migration Planning

Front 387

What are the key aspects of migration planning ?

Back 387

Finalizing the arch road map and implementation and migration plan

Ensuing plan is coordinated with the enterprise's change management approach

ensure business value of the approach is understood

transition from development of arch to implementing

Front 388

What is step 1 of Phase f - Migration Planning?

Back 388

confirm management f/w interactions... this means to make sure it fits well with the management approach (pm plan)

-business plan, ent arch f/w, ppm, ops management,

Front 389

Explain Phase F - Step 2 - assign business value

Back 389

establish and assign business values to work packages

address issues such as (1) performance evaluation (2) ROI (3) business value, (4) CSF - critical success factors, (%) measures of effectiveness, (6) strategic fit

Assign risk to projects

Front 390

Explain Phase f - Step 3 - estimate resource requirements (costs & timing)

Back 390

determine resources, timing and then identify the costs...

for costs, there are two types: capital cost and ongoing operational cost

Front 391

describe Phase f Step 4 - Prioritize migration projects

Back 391

prioritize projects with most business value and low cost (quick win)

review the risks and ensure they are mitigated (to the extent possible)

get stakeholder agreement

review the risk and revise; residual risk

Front 392

What is residual risk?

Back 392

once you have executed risk mitigation, there is often left over risk... called residual risk

Front 393

Describe Phase f - Step 5 - confirm arch roadmap

Back 393

update architecture roadmap including transition architecture

create transition architecture state evolution table...

if the approach ever changes, update the arch definition document

Front 394

What is included in Phase f Step 6 - generate imp&migration plan

Back 394

generate the completed imp and migration plan

capture external dependencies

Front 395

For Phase f - migration, what are all teh steps?

Back 395

6- generate implementation & migration plan

7 - complete arch dev

Front 396

Describe Phase f - Step 7 - complete arch dev

Back 396

complete the arch dev and transition to implementation

identify lessons learned

revisit phase B if required for deeper details

Front 397

Phase G is concerned with what?

Back 397

Implementation governance

Front 398

What are the key activities of Phase G

Back 398

-ensure conformance with target arch

-execute governance duties

-handle change requested

-update baseline arch as changes implemented

Front 399

What is included in Phase G Step 1 - confirm scope and priorities?

Back 399

produce recommendations for deployment

identify ea priorities for dev team

identify deployment issues

identify building blocks that need replace,ment

Front 400

What activities are involved in Phase G Step 2 - identify development resources

Back 400

identify system dev methods (SDM)

ensure system dev method enable feedback to arch team on design

Front 401

What are all the steps in Phase G - Execute implementation governance

Back 401

1

2

3 - guid3 development

Front 402

How do you execute step 3 of phase g - guide development

Back 402

1 - formulate project recommendations

2 - create arch contract/obtain signature

3 - update the enterprise continuum

4 - guide service development

5 - implementation plan

Front 403

Describe Phase G step 4 - compliance reviews

Back 403

review ongoing implementation governance and arch compliance

conduct post dev reviews

close out development

Front 404

Describe Phase G Step 5 - Implement business and IT operations

Back 404

This is where you actualy carry out the final aspects of the deployment and publish baseline

Front 405

Describe Phase G step 6 - Post-Imp Review

Back 405

Conduct a review to make sure the implementation was executed as expected then publish a review

Finally, you'll close the project out after talking to the stakeholders.

Front 406

So what is Phase H all about??

Back 406

after the project is live, it is the last phase where change management of the architecture is conducted....

this is where you wait for changes that will kick off new ADM cycles

You also monitor

Front 407

What are the key items includes in Phase H Step 1 - Establish Value Realization Process

Back 407

- influence business projects to exploit the EA for value realization (push folks to use the enterprise assets)

Front 408

What are the Steps in Phase H

Back 408

1- establish value realization process

2 - deploy monitoring tools

3 - manage risks

4 -analyse change management

5 - develop change requirements

6 - manage the governance process

7 - activate process to implement change!

Front 409

During Phase H Step 2 - Deploy Monitoring tools, what are some of the different dimensions that you will monitor?

Back 409

-tech changes

-business changes

-business value

-arch capability maturity

-asset management

-QoS

Front 410

There are many different ways and times that you address risk in TOGAF, in Phase H Step 3, you will _______ risk

Back 410

Manage risk and provide recommendations for IT Strategy

Front 411

Phase H Step 4 includes analyzing for change management , what type of activities will you do?

Back 411

analyze performance

EA performance reviews

assess change requests

take on any gap analysis needed

make sure governance is being followed

Front 412

Phase H Step 5 is focused on developing change requirements if you are not meeting performance targets

Back 412

the steps are in the title... if you are not meeting targets, then you make recommendations to change

Front 413

Phase H Step 6 is all about the governance process.... who is involved?

Back 413

the architecture review board

Front 414

Phase H has a final step, step 7, that include activating the process to implement change... what's included?

Back 414

-producing new requests for work

-ensuring changes that get implemented are documented in the arch repository

Front 415

What is at the center of the ADM cycle?

Back 415

requirements management

Front 416

How does Req Management differ from other phases?

Back 416

Requirements management is more like a centralized hub instead of a phase w/ separate steps... it provides the process used by each of the outer phases

Front 417

For requirements management, what is step 1?

Back 417

Identify/document requirements

Front 418

What are the steps 1-5 of requirements management and where does it actually happen?

Back 418

1 - identify requirements (ADM)

2 - prioritize requirements (RM)

3 - monitor baseline requirements (RM)

4 - identify changed requirements (ADM)

5 - identify changed requirements (RM)

Front 419

What are the steps 6 - 10 of requirements management and where does it actually happen?

Back 419

6 - assess impact of the requirements (ADM)

7 - implement requirements for phase H (ADM)

8 - update requirements repository (RM)

9 - implement the change in the current ADM phase (ADM)

10 - assess and revise gap analysis of PRIOR phases