Core Concepts Flashcards

1
Q

Phases of the ADM

A
  • Preliminary Phase
  • Phase A: Architecture Vision
  • Phase B: Business Architecture
  • Phase C: Information Systems Architectures
  • Phase D: Technology Architecture
  • Phase E: Opportunities and Solutions
  • Phase F: Migration Planning
  • Phase G: Implementation Governance
  • Phase H: Architecture Change Management
  • Requirements Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Preliminary Phase

A

Describes the preparation and initiation activities required to create an Architecture Capability, including the customization of the TOGAF framework, and the definition of Architecture Principles.

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

Phase A: Architecture Vision

A

Describes the initial phase of an Architecture Development Cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.

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

Phase B: Business Architecture

A

Describes the development of a Business Architecture to support an agreed Architecture Vision.

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

Phase C: Information Systems Architectures

A

Describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.

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

Phase D: Technology Architecture

A

Describes the development of the Technology Architecture for an architecture project.

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

Phase E: Opportunities and Solutions

A

Describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture defined in the previous phases.

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

Phase F: Migration Planning

A

Describes the development of a detailed Implementation and Migration Plan that addresses how to move from the Baseline to the Target Architecture.

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

Phase G: Implementation Governance

A

Provides an architectural oversight of the implementation.

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

Phase H: Architecture Change Management

A

Establishes procedures for managing change to the new architecture.

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

Requirements Management

A

Examines the process of managing architecture requirements throughout the ADM.

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

The Architecture Content Framework uses three categories to describe the type of architectural work product within the context of use.

A
  • Deliverable
  • Artifact
  • Building block
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Deliverable

A

Is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders

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

Artifact

A

Is an architectural work product that describes an aspect of the architecture

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

Building block

A

Represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions

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

The Enterprise Continuum and the Architecture Repository

A

The Enterprise Continuum provides 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.

17
Q

The Enterprise Continuum and the Architecture Repository

A

The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures.

18
Q

Concepts of the Enterprise Continuum

A
  • Architecture Continuum
  • Solutions Continuum
19
Q

Components within an Architecture Repository

A
  • Architecture Metamodel
  • Architecture Capability
  • Architecture Landscape
  • Standards Information Base (SIB)
  • Reference Library
  • Governance Log
  • Architecture Requirements Repository
  • Solutions Landscape
20
Q

Architecture Metamodel

A

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

21
Q

Architecture Capability

A

Defines the parameters, structures, and processes that support governance of the Architecture Repository

22
Q

Architecture Landscape

A

Shows an architectural view of the building blocks that are in use within the organization today (e.g., a list of the live applications); the landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives

23
Q

Standards Information Base (SIB)

A

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

24
Q

Reference Library

A

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

25
Q

Governance Log

A

Provides a record of governance activity across the enterprise

26
Q

Architecture Requirements Repository

A

Provides a view of all authorized architecture requirements which have been agreed with the Architecture Board

27
Q

Solutions Landscape

A

Presents an architectural representation of the SBBs supporting the Architecture Landscape which have been planned or deployed by the enterprise

28
Q

Architecture Capability Framework Contents Summary

A
  • Establishing an Architecture Capability. Guidelines for establishing an Architecture Capability within an organization.
  • Architecture Board. Guidelines for establishing and operating an enterprise Architecture Board.
  • Architecture Compliance. Guidelines for ensuring project compliance with architecture.
  • Architecture Contracts. Guidelines for defining and using Architecture Contracts.
  • Architecture Governance. Framework and guidelines for Architecture Governance.
  • Architecture Maturity Models. Techniques for evaluating and quantifying an organization’s maturity in Enterprise Architecture.
  • Architecture Skills Framework. A set of role, skill, and experience norms for staff undertaking Enterprise Architecture work.
29
Q

The Enterprise Continuum.

A

Provides methods for classifying artifacts

30
Q

Architecture Capability Framework

A

Discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture practice within an enterprise

31
Q

To promote effective architectural activity within the enterprise, the TOGAF standard recommends the establishment of a(n)

A

Enterprise Architecture Capability

32
Q

Architecture Capability

A

A class of architectural information within the Architecture Repository that defines processes supporting the governance of the Architecture Repository

33
Q

Purpose of the TOGAF Library

A

To accelerate the creation of new enterprise architectures

34
Q

Use the Architecture Development Method

A

is recommended to achieve a customer-focused, value-adding, and sustainable architecture practice

35
Q

Preliminary phase

A

Includes the objective of establishing the organizational model for Enterprise Architecture