Architecture Development Method

Question 1

Phase H: Architecture Change Management

Answer 1

Ensures that the architecture responds to the needs of the enterprise

Question 2

The final step in the development of the four architecture domains

Answer 2

Create Architecture Definition Document

Question 3

The version numbers used by the TOGAF standard as a convention to denote a high-level outline of an architecture

Answer 3

Version 0.1

Question 4

The recommended information areas managed by a governance repository.

Answer 4

• Reference Data. Used for guidance and instruction during project implementation
• Process Status. Record of all information regarding the state of any governance processes
• Audit Information. A record of all completed governance process actions

Question 5

The ADM supports the concept of iteration at three levels.

Answer 5

• Cycling around the ADM. The ADM is presented in a circular manner indicating that the completion of one phase of architecture work directly feeds into subsequent phases of architecture work
• Iterating between phases. The TOGAF standard describes the concept of iterating across phases (e.g., returning to Business Architecture on completion of Technology Architecture)
• Cycling around a single phase. The ADM supports repeated execution of the activities within a single ADM phase as a technique for elaborating architectural content.

Question 6

Architecture Development Method Activities by Phase

Answer 6

• Preliminary Phase
• Requirements Management
• Phase A: Architecture Vision
• Phase B: Business Architecture
• Phase C: Information Systems Architectures (Application & Data)
• Phase D: Technology Architecture
• Phase E: Opportunities & Solutions
• Phase F: Migration Planning
• Phase G: Implementation Governance
• Phase H: Architecture Change Management

Question 7

Preliminary Phase

Answer 7

• Prepare the organization for successful TOGAF architecture projects.
• Undertake the preparation and initiation activities required to create an Architecture Capability, including the customization of the TOGAF framework, selection of tools, and the definition of Architecture Principles.

Question 8

Requirements Management

Answer 8

Every stage of a TOGAF project is based on and validates business requirements. Requirements are identified, stored, and fed into and out of the relevant ADM phases, which dispose of, address, and prioritize requirements.

Question 9

Phase A: Architecture Vision

Answer 9

• Set the scope, constraints, and expectations for a TOGAF project.
• Create the Architecture Vision.
• Identify stakeholders.
• Validate the business context and create the Statement of Architecture Work.
• Obtain approvals.

Question 10

Phase B: Business Architecture, Phase C: Information Systems Architectures (Application & Data), Phase D: Technology Architecture
Develop architectures in four domains.

Answer 10

1. Business
2. Information Systems – Application
3. Information Systems – Data
4. Technology
   In each case, develop the Baseline and Target Architecture and analyze gaps.

Question 11

Phase E: Opportunities & Solutions

Answer 11

• Perform initial implementation planning and the identification of delivery vehicles for the building blocks identified in the previous phases.
• Determine whether an incremental approach is required, and if so identify Transition Architectures.

Question 12

Phase F: Migration Planning

Answer 12

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

Question 13

Phase G: Implementation Governance

Answer 13

• Provide architectural oversight for the implementation.
• Prepare and issue Architecture Contracts.
• Ensure that the implementation project conforms to the architecture.

Question 14

Phase H: Architecture Change Management

Answer 14

Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise and maximizes the value of the architecture to the business.

Question 15

Phase A: Architecture Vision Deliverable

Answer 15

Architecture Vision
- Business Architecture
- Data Architecture
- Application Architecture
- Technology Architecture

Question 16

Phase B: Business Architecture Deliverable

Answer 16

Architecture Definition Document
- Business Architecture

Question 17

Phase C: Information Systems Architecture Deliverable

Answer 17

Architecture Definition Document
- Data Architecture
- Application Architecture

Question 18

Phase D: Technology Architecture Deliverable

Answer 18

Architecture Definition Document
- Technology Architecture

Question 19

Version 0.1

Answer 19

Indicates that a high-level outline of the architecture is in place.

Question 20

Version 1.0

Answer 20

Indicates a formally reviewed, detailed architecture.

Question 21

The practical implementation of the Enterprise Continuum

Answer 21

Take the form of an Architecture Repository

Question 22

Architecture Repository

Answer 22

Includes reference architectures, models, and patterns that have been accepted for use within the enterprise, and actual architectural work done previously within the enterprise.

Question 23

The application of the ADM is supported by

Answer 23

An extended set of resources – guidelines, templates, checklists, and other detailed materials

Question 24

Main reasons to constrain (or restrict) the scope of the architectural activity to be undertaken

Answer 24

• The organizational authority of the team producing the architecture
• The objectives and stakeholder concerns to be addressed within the architecture
• The availability of people, finance, and other resources

Question 25

Dimensions for Limiting the Scope of the Architecture Activity

Answer 25

• Breadth. What is the full extent of the enterprise, and what part of that extent should the architecting effort deal with?
• Depth. To what level of detail should the architecting effort go? How much architecture is “enough”? What is the appropriate demarcation between the architecture effort and other, related activities (system design, system engineering, system development)?
• Time period. What is the time period that needs to be articulated for the Architecture Vision, and does it make sense (in terms of practicality and resources) for the same period to be covered in the detailed architecture description? If not, how many Transition Architectures are to be defined, and what are their time periods?
• Architecture domains. A complete Enterprise Architecture description should contain all four architecture domains (Business, Data, Application, Technology), but the realities of resource and time constraints often mean there is not enough time, funding, or resources to build a top-down, all-inclusive architecture description encompassing all four architecture domains, even if the enterprise scope is chosen to be less than the full extent of the overall enterprise.
  The scope of architecture is first expressed in terms of breadth, depth, and time. Once these dimensions are understood, a suitable combination of architecture domains can be selected that are appropriate to the problem being addressed.