Brainscape's Knowledge GenomeTM

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


See full index

TOGAF9.2 > The ADM Phases > Flashcards

The ADM Phases Flashcards

1
Q

Preliminary Phase

A

The Preliminary Phase includes the preparation and initiation activities to create an Architecture Capability. Key activities are as follows:
- Understand the business environment
- Ensure high-level management commitment
- Obtain agreement on the scope
- Establish Architecture Principles
- Establish a governance structure
- Customization of the TOGAF framework

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

Preliminary Phase - Objectives

A
  • Determine the Architecture Capability desired by the organization:
    • Review the organizational context for conducting Enterprise Architecture
    • Identify and scope the elements of the enterprise organizations affected by the Architecture Capability
    • Identify the established frameworks, methods, and processes that intersect with the Architecture Capability
    • Establish a Capability Maturity target
  • Establish the Architecture Capability:
    • Define and establish the Organizational Model for Enterprise Architecture
    • Define and establish the detailed process and resources for Architecture Governance
    • Select and implement tools that support the Architecture Capability
    • Define the Architecture Principles
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Preliminary Phase - Approach

A

The main aspects are as follows:
- Defining the Enterprise
- It is imperative to appoint a sponsor at this stage to ensure that the resultant activity has resources to proceed and the clear support of the business management
- Identifying Key Drivers and elements in the Organizational Context. Considerations include:
- The commercial models and budget for the Enterprise Architecture
- The stakeholders
- The intentions and culture of the organization
- Current processes that support the execution of change and operation of the enterprise
- The Baseline Architecture Landscape
- The skills and capabilities of the enterprise
- Defining the Requirements for Architecture Work
- Business requirements
- Cultural aspirations
- Organization intents
- Strategic intent
- Forecast financial requirements
- Defining the Architecture Principles that will inform any Architecture Work
- Defining the Framework to be used.
The TOGAF framework has to co-exist with and enhance the operational capabilities of other frameworks in use within an organization. The main frameworks that may need to be coordinated with the TOGAF framework are:
- Business Capability Management (Business Direction and Planning) which determines what business capabilities are required
- Portfolio/Project Management Methods that determine how a company manages its change initiatives
- Operations Management Methods which describe how a company runs its day-to-day operations, including IT
- Solution Development Methods which formalize the way that business systems are delivered
- Defining the relationships between management frameworks
- Evaluating the Enterprise Architecture’s maturity

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

Phase A: Architecture Vision

A

Phase A is about project establishment and initiates an iteration of the Architecture Development Cycle, setting the scope, constraints, and expectations for the iteration.

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

Phase A - Objectives

A
  • Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture
  • Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Phase A - Approach

A
  • Starts with receipt of a Request for Architecture Work from the sponsoring organization to the architecture organization.
  • A key objective is to ensure proper recognition and endorsement from corporate management, and the support and commitment of line management for this evolution of the ADM cycle.
  • Creating the Architecture Vision is a key activity in this phase.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Phase A - Approach: Creating the Architecture Vision

A

The Architecture Vision
- Provides the sponsor with a key tool to sell the benefits of the proposed capability to stakeholders and decision-makers within the enterprise.
- Describes how the new capability will meet the business goals and strategic objectives and address the stakeholder concerns when implemented.
- Provides a first-cut, high-level description of the Baseline and Target Architectures, covering the Business, Data, Application, and Technology domains
- Defined and Documented in the Statement of Architecture Work

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

Phase A - Approach: Business Scenarios

A

The business scenarios technique can be used for identifying and articulating the business requirements implied, and the implied architecture requirements

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

Phase B: Business Architecture

A

Phase B is about the development of a Business Architecture to support an agreed Architecture Vision.
This describes the fundamental organization of a business embodied in:
- Its business process and people
- Their relationships to each other and the people
- The principles governing its design and evolution
and shows how an organization meets its business goals.

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

Phase B - Objectives

A
  • Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns
  • Identify candidate Architecture Roadmap components based on gaps between the Baseline and Target Business Architectures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Phase B - Approach

A

Business Architecture is a representation of holistic, multi-dimensional business views of:
- capabilities
- end-to-end value delivery
- information and organizational structure
- and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.
In summary, Business Architecture relates business elements to business goals and elements of other domains.

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

Phase B - Approach: Developing the Baseline Description

A
  • Applying Business Capabilities
  • Applying Value Streams
  • Applying the Organization Map
    While capability mapping exposes what a business does and value stream mapping exposes how it delivers value to specific stakeholders, the Organization Map identifies the business units or third parties that possess or use those capabilities and which participate in the value streams. Together with capability maps and value streams, the Organization Map provides an understanding of which business units to involve in the architecture effort, who and when to talk about a given requirement, and how to measure the impact of various decisions.
  • Applying Business Modeling
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Phase C: Information Systems Architectures

A

Phase C is about documenting the 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
14
Q

Phase C - Objectives

A
  • Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns
  • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Phase C - Approach: Key Considerations for the Data Architecture

A
  • Data Management
  • Data Migration
  • Data Governance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Phase C - Approach: Data Management

A
  • Define application components that will serve as the system of record or reference for enterprise master data
  • Define enterprise-wide standards that all application components, including software packages, need to adopt
  • Understand how data entities are utilized by business functions, processes, and services
  • Understand how and where enterprise data entities are created, stored, transported, and reported
  • Understand the level and complexity of data transformations required to support the information exchange needs between applications
  • Define the requirement for software in supporting data integration with the enterprise’s customers and suppliers (e.g., use of ETL tools during the data migration, data profiling tools to evaluate data quality, etc.)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Phase C - Approach: Data Migration

A

The Data Architecture should identify data migration requirements and also provide indicators as to the level of transformation, weeding, and cleansing that will be required to present data in a format that meets the requirements and constraints of the target application. The objective is to ensure that the target application has quality data when it is populated. Another key consideration is to ensure that an enterprise-wide common data definition is established to support the transformation.

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

Phase C - Approach: Data Governance

A

Ensure that the enterprise has the necessary dimensions in place to enable the transformation:
- Structure. Does the enterprise have the necessary organizational structure and the standards bodies to manage data entity aspects of the transformation?
- Management System. Does the enterprise have the necessary management system and data-related programs to manage the governance aspects of data entities throughout its lifecycle?
- People. What data-related skills and roles does the enterprise require for the transformation?

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

Phase D: Technology Architecture

A

Phase D is about documenting the Technology Architecture for an architecture project, in the form of the fundamental organization of the IT systems:
- Embodied in the hardware, software, and communications technology
- Their relationships to each other and the environment
- The principles governing its design and evolution

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

Phase D - Objectives

A
  • Develop the Target Technology Architecture that enables the Architecture Vision, target business, data, and application building blocks to be delivered through technology components and technology services, in a way that addresses the Statement of Architecture Work and stakeholder concerns
  • Identify candidate Architecture Roadmap components based on gaps between the Baseline and Target Technology Architectures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Phase D - Approach: Emerging Technologies – A Driver for Change

A

The evolution of new technologies is a major driver for change in enterprises looking for new innovative ways of operating and improving their business.
While the Enterprise Architecture is led by business concerns, drivers for change are often found within evolving technology capabilities

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

Phase E: Opportunities and Solutions

A
  • The first phase which is directly concerned with implementation.
  • Describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture identified in previous phases.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Phase E - Key Activities

A
  • Perform initial implementation planning
  • Identify the major implementation projects
  • Group changes into work packages
  • Decide on approach:
    • Make versus buy versus re-use
    • Outsource
    • COTS
    • Open Source
  • Assess priorities
  • Identify dependencies
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Phase E - Objectives

A
  • Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
  • Determine whether an incremental approach is required and if so identify Transition Architectures that will deliver continuous business value
  • Define the overall Solution Building Blocks (SBBs) to finalize the Target Architecture based on the Architecture Building Blocks (ABBs)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Phase E - Approach

A
  • Concentrates on how to deliver the architecture, taking into account the complete set of gaps between the Target and Baseline Architectures in all architecture domains, and logically grouping changes into work packages within the enterprise’s portfolios.
  • Phase E is the initial step in the creation of a well-considered Implementation and Migration Plan that is integrated into the enterprise’s portfolio in Phase F.
26
Q

Phase E - Approach: Key Concepts

A

There are four key concepts in the transition from developing to delivering a Target Architecture:
- Architecture Roadmap. Lists individual work packages in a timeline that will realize the Target Architecture.
- Work Packages. Identify a logical group of changes necessary to realize the Target Architecture.
- Transition Architectures. Describes the enterprise at an architecturally significant state between the Baseline and Target Architectures. Transition Architectures provide interim Target Architectures upon which the organization can converge.
- Implementation and Migration Plan. Provides a schedule of the projects that will realize the Target Architecture

27
Q

Phase F: Migration Planning

A

Addresses detailed migration planning; that is, how to move from the Baseline to the Target Architectures.

28
Q

Phase F - Key Activities

A
  • For work packages and projects identified, perform a cost/benefit analysis and a risk assessment
  • Finalize a detailed Implementation and Migration Plan
29
Q

Phase F - Objectives

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

Phase F - Approach

A

The focus - is the creation of an Implementation and Migration Plan in cooperation with the portfolio and project managers.
Activities include assessing the dependencies, costs, and benefits of the various migration projects.

31
Q

Phase G: Implementation Governance

A

Defines how the architecture constrains the implementation projects, monitors it while building it, and produces a signed Architecture Contract.

32
Q

Phase G - Key Activities

A
  • Provide architectural oversight for the implementation
  • Define architecture constraints on implementation projects
  • Govern and manage an Architecture Contract
  • Monitor implementation work for conformance
33
Q

Phase G - Objectives

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

Phase G - Approach

A
  • Establish an implementation program that will enable the delivery of the agreed Transition Architectures
  • Adopt a phased deployment schedule that reflects the business priorities embodied in the Architecture Roadmap
  • Follow the organization’s standard for corporate, IT, and Architecture Governance
  • Use the organization’s established portfolio/program management approach, where this exists
  • Define an operations framework to ensure the effective long life of the deployed solution
    A key aspect of Phase G is ensuring compliance with the defined architecture(s), not only by the implementation projects but also by other ongoing projects.
35
Q

Phase H: Architecture Change Management

A

Ensures that changes to the architecture are managed in a controlled manner.

36
Q

Phase H - Key Activities

A
  • Provide continual monitoring and a change management process
  • Ensure that changes to the architecture are managed in a cohesive and architected way
  • Provide flexibility to evolve rapidly in response to changes in the technology or business environment
  • Monitor the business and capacity management
37
Q

Phase H - Objectives

A
  • Ensure that the architecture lifecycle is maintained
  • Ensure that the Architecture Governance Framework is executed
  • Ensure that the enterprise’s Architecture Capability meets current requirements
38
Q

Phase H - Approach

A

The goal is to ensure that the architecture achieves its original target business value. Monitoring business growth and decline is a critical aspect of this phase.
The value and change management process, once established, will determine:
- The circumstances under which the Enterprise Architecture, or parts of it, will be permitted to change after deployment, and the process by which that will happen
- The circumstances under which the Architecture Development Cycle will be initiated to develop a new architecture

39
Q

Phase H - Approach: Enterprise Architecture Change Management Process

A

The TOGAF standard recommends the following approach based on classifying the required architectural changes into one of three categories:
- Simplification change. Can normally be handled via change management techniques; is often driven by a requirement to reduce investment
- Incremental change. May be capable of being handled via change management techniques, or it may require partial re-architecting, depending on the nature of the change; is driven by a requirement to derive additional value from existing investment
- Re-architecting change. A re-architecting change requires putting the whole architecture through the Architecture Development Cycle again; is driven by a requirement to increase investment in order to create new value for exploitation

40
Q

Phase H - Approach: Maintenance vs Architecture Redesign

A
  • If the change impacts two stakeholders or more, then it is likely to require an architecture redesign and re-entry to the ADM
  • If the change impacts only one stakeholder, then it is more likely to be a candidate for change management
  • If the change can be allowed under a dispensation, then it is more likely to be a candidate for change management
41
Q

Phase H - Approach: A refreshment cycle may be required if

A
  • The Foundation Architecture needs to be re-aligned with the business strategy
  • Substantial change is required to components and guidelines for use in the deployment of the architecture
  • Significant standards used in the product architecture are changed which have a significant end-user impact; e.g., regulatory changes
    If there is a need for a refreshment cycle, then a new Request for Architecture Work must be issued (to move to another cycle).
42
Q

Requirements Management

A

The process of managing architecture requirements applies to all phases of the ADM cycle.
It is a dynamic process, which addresses the identification of requirements for the enterprise, stores them, and then feeds them in and out of the relevant ADM phases.

43
Q

Requirements Management - Objectives

A
  • Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases
  • Manage architecture requirements identified during any execution of the ADM cycle or a phase
  • Ensure that the relevant architecture requirements are available for use by each phase as the phase is executed
44
Q

Requirements Management - Approach

A

It is recommended that an Architecture Requirements Repository is used to record and manage all architecture requirements.
The TOGAF standard does not mandate or recommend any specific process or tool for requirements management.

45
Q

Transition Architectures defined in Phase E confirmed with the stakeholders

A

Phase F

46
Q

Cost/benefit analysis

A

Phase F

47
Q

Decide on approach — Make versus buy versus re-use

A

Phase E

48
Q

Assess an organization’s Business Transformation Readiness

A

Maturity Models

49
Q

The relationship between the Architecture Continuum and the Solutions Continuum is one of

A

Guidance, direction and support

50
Q

The levels of granularity of the Architecture Landscape

A

Strategic Architectures, Segment Architectures, and Capability Architectures

51
Q

Requirements Management

A

Does not dispose of, address, or prioritize any requirements; this is done within the relevant phase of the ADM

52
Q

An artifact

A

Describes an architecture from a specific view point

53
Q

Key Point of the ADM Cycle

A

The main guideline is to focus on what creates value for the enterprise, and to select horizontal and vertical scope, and project schedules, accordingly

54
Q

How is the scope of the enterprise architecture projects decided?

A

The scope is defined in phase A and refined in phases B, C and D

55
Q

Phase E

A

In Phase E major work packages or projects are identified and classified as new development, purchase opportunity, or re-use of the existing system

56
Q

Six characteristics used in TOGAF to highlight both the value and necessity for governance

A

Discipline, Transparency, Independence, Accountability, Responsibility, and Fairness

57
Q

The Standards Information Base

A

A database of facts and guidance about information systems standards.
It holds a set of specifications, to which architectures must conform.

58
Q

Business Transformation Readiness Assessment is a key technique

A

Phase A: Architecture Vision; Phase E: Opportunities and Solutions; Phase F: Migration Planning

59
Q

The Architecture Continuum classifies the assets

A

Self-explanatory

60
Q

The Gap Analysis technique is used

A

Phases B, C, D, and E

61
Q

A concern can be addressed by one or more viewpoints

A

Self-explanatory

62
Q

How is the scope of the enterprise architecture projects decided?

A

Agreement on the scope is reached in the Preliminary Phase and it is defined in Phase A

TOGAF9.2 (12 decks)

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