TOGAF

Question 1

Briefly describe the ADM cycle, its phases, and the objective of each phase.

Answer 1

The TOGAF Architecture Development Method (ADM) provides a tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architecture.

All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities.

Question 2

Phase B:
Business Architecture
Phase C:
Information Systems Architectures (Application & Data)
Phase D:
Technology Architecture

Answer 2

Develop architectures in four domains: 
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 3

Phase B

Answer 3

Business Architecture describes the development of a Business Architecture to support the agreed Architecture Vision

Question 4

Phase E:

Opportunities and Solutions

Answer 4

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 5

Phase D

Answer 5

Technology Architecture describes the development of the Technology Architecture to support the agreed Architecture Vision

Question 6

Phase E

Answer 6

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

Question 7

Phase F:

Migration Planning

Answer 7

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

Question 8

Phase G:

Implementation Governance

Answer 8

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

Question 9

Phase H

Answer 9

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 10

Requirements Management

Answer 10

examines the process of managing architecture requirements throughout the ADM

Question 11

Describe the objectives of the Preliminary Phase.

Answer 11

The Preliminary Phase describes the preparation and initiation activities required to create an Architecture Capability including customization of the TOGAF framework and definition of Architecture Principles

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 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

Question 12

Describe the structure of TOGAF, and briefly explain the contents of each of the parts.

Answer 12

PART I
(Introduction) This part provides a high-level introduction to the key concepts of Enterprise Architecture and in particular the TOGAF approach. It contains the definitions of terms used throughout this standard.
PART II
(Architecture Development Method) This part is the core of the TOGAF framework. It describes the TOGAF Architecture Development Method (ADM) - a step-by-step approach to developing an Enterprise Architecture.
PART III
(ADM Guidelines & Techniques) This part contains a collection of guidelines and techniques available for use in applying the TOGAF approach and the TOGAF ADM. Additional guidelines and techniques are available in the TOGAF Library.
PART IV
(Architecture Content Framework) This part describes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable Architecture Building Blocks (ABBs), and an overview of typical architecture deliverables.
PART V
(Enterprise Continuum & Tools) This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise.
PART VI
(Architecture Capability Framework) This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture function within an enterprise.

Question 13

What is an enterprise?

Answer 13

A whole corporation or a division of a corporation
A government agency or a single government department
A chain of geographically distant organizations linked together by common ownership
Groups of countries or governments working together to create common or shareable deliverables or infrastructures
Partnerships and alliances of businesses working together, such as a consortium or supply chain

Question 14

Explain the purpose of an enterprise architecture.

Answer 14

The purpose of Enterprise Architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy.

Question 15

List the 4 types of architecture that TOGAF deals with

Answer 15

The Business Architecture defines the business strategy, governance, organization, and key business processes
The Data Architecture describes the structure of an organization’s logical and physical data assets and data management resources
The Application Architecture provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization
The Technology Architecture describes the 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.

Question 16

Briefly explain what TOGAF is.

Answer 16

The TOGAF standard is an architecture framework. It provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an Enterprise Architecture. It is based on an iterative process model supported by best practices and a re-usable set of existing architecture assets.

Question 17

Explain why TOGAF is suitable as a framework for enterprise architecture.

Answer 17

The TOGAF standard has been developed through the collaborative efforts of the whole community. Using the TOGAF standard results in Enterprise Architecture that is consistent, reflects the needs of stakeholders, employs best practice, and gives due consideration both to current requirements and the perceived future needs of the business.

Developing and sustaining an Enterprise Architecture is a technically complex process which involves many stakeholders and decision processes in the organization. The TOGAF standard plays an important role in standardizing and de-risks the architecture development process. The TOGAF standard provides a best practice framework for adding value, and enables the organization to build workable and economic solutions which address their business issues and needs.

Question 18

Define an Architecture Framework

Answer 18

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

Question 19

List the business benefits of having an enterprise architecture - Benefit 1

Answer 19

More effective and efficient business operations:
Lower business operation costs
More agile organization
Business capabilities shared across the organization
Lower change management costs
More flexible workforce
Improved business productivity

Question 20

List the business benefits of having an enterprise architecture - Benefit 2

Answer 20

More effective and efficient Digital Transformation and IT operations:
Extending effective reach of the enterprise through digital capability
Bringing all components of the enterprise into a harmonized environment
Lower software development, support, and maintenance costs
Increased portability of applications
Improved interoperability and easier system and network management
Improved ability to address critical enterprise-wide issues like security
Easier upgrade and exchange of system components

Question 21

List the business benefits of having an enterprise architecture - Benefit 3

Answer 21

Better return on existing investment, reduced risk for future investment:
Reduced complexity in the business and IT
Maximum return on investment in existing business and IT infrastructure
The flexibility to make, buy, or out-source business and IT solutions
Reduced risk overall in new investments and their cost of ownership

Question 22

List the business benefits of having an enterprise architecture - Benefit 4

Answer 22

Faster, simpler, and cheaper procurement:
Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan
The procurement process is faster - maximizing procurement speed and flexibility without sacrificing architectural coherence
The ability to procure heterogeneous, multi-vendor open systems
The ability to secure more economic capabilities

Question 23

Describe the Enterprise Continuum.

Answer 23

The Enterprise Continuum provides strcuture and classification for assets enterprise repositories.

Supporting the Enterprise Continuum is the concept of an Architecture Repository which can be used to store different classes of architectural output at different levels of abstraction, created by the ADM. In this way, the TOGAF standard facilitates understanding and co-operation between stakeholders and practitioners at different levels.

Question 24

List the elements of the Architecture Repository -

Answer 24

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

Question 25

Explain how to establish and maintain an enterprise Architecture Capability.

Answer 25

In order to carry out architectural activity effectively within an enterprise, it is necessary to put in place an appropriate business capability for architecture, through organization structures, roles, responsibilities, skills, and processes

Question 26

Using the TOGAF Standard with Other Frameworks

Answer 26

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

Because the TOGAF standard is a generic framework and intended to be used in a wide variety of environments, it provides a flexible and extensible content framework that underpins a set of generic architecture deliverables.

As a result, the TOGAF framework may be used either in its own right, with the generic deliverables that it describes; or else these deliverables may be replaced or extended by a more specific set, defined in any other framework that the architect considers relevant.

Question 27

Describe the core concept of establishing the Architecture Capability as an operational entity.

Answer 27

Barring Architecture Capabilities set up to purely support change delivery programs, it is increasingly recognized that a successful Enterprise Architecture practice must sit on a firm operational footing. In effect, an Enterprise Architecture practice must be run like any other operational unit within a business; i.e., it should be treated like a business.

Financial Management
Performance Management
Service Management
Risk Management (see A.54 Risk Management)
Resource Management
Communications and Stakeholder Management (see 3.33 Communications and Stakeholder Management)
Quality Management
Supplier Management (see A.60 Supplier Management)
Configuration Management (see A.7 Configuration Management)
Environment Management

Question 28

Explain the need for the ADM process to be governed.

Answer 28

The ADM, whether adapted by the organization or used as documented here, is a key process to be managed in the same manner as other architecture artifacts classified through the Enterprise Continuum and held in the Architecture Repository. The Architecture Board should be satisfied that the method is being applied correctly across all phases of an architecture development iteration. Compliance with the ADM is fundamental to the governance of the architecture, to ensure that all considerations are made and all required deliverables are produced.

The management of all architectural artifacts, governance, and related processes should be supported by a controlled environment. Typically, this would be based on one or more repositories supporting versioned objects, process control, and status.

Question 29

Describe the major information areas held in the governance repository.

Answer 29

Reference Data - collateral from the organization’s own repositories/Enterprise Continuum, including external data; e.g., COBIT, the IT4IT Reference Architecture): used for guidance and instruction during project implementation

Process Status - all information regarding the state of any governance processes will be managed

Audit Information - this will record all completed governance process actions and will be used to support:
Key decisions and responsible personnel for any architecture project that has been sanctioned by the governance process
A reference for future architectural and supporting process developments, guidance, and precedence

Question 30

Briefly explain the reasons for scoping an architecture activity

Answer 30

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 31

List the main reasons why you would need to adapt the ADM.

Answer 31

One reason for wanting to adapt the ADM, which it is important to stress, 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.

Other possible reasons for wanting to adapt the ADM include:

1) The ADM is one of the many corporate processes that make up the corporate governance modelIt is complementary to, and supportive of, other standard program management processes, such as those for authorization, risk management, business planning and budgeting, development planning, systems development, and procurement.
2) he ADM is being mandated for use by a prime or lead contractor in an outsourcing situation, and needs to be tailored to achieve a suitable compromise between the contractor’s existing practices and the contracting enterprise’s requirements
3) The enterprise is a small-to-medium enterprise, and wishes to use a “cut-down” method more attuned to the reduced level of resources and system complexity typical of such an environment
4) The enterprise is very large and complex, comprising many separate but interlinked “enterprises” within an overall collaborative business framework, and the architecture method needs to be adapted to recognize this

Question 32

List the possible dimensions for limiting the scope.

Answer 32

Breadth - what is the full extent of the enterprise, and what part of that extent will this architecting effort deal with?

Depth- to what level of detail should the architecting effort go?

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?

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

Question 33

Briefly explain the need for an integration framework that sits above individual architectures.

Answer 33

Architectures that are created to address a subset of issues within an enterprise require a consistent frame of reference so that they can be considered as a group as well as point deliverables. The dimensions that are used to define the scope boundary of a single architecture (e.g., level of detail, architecture domain, etc.) are typically the same dimensions that must be addressed when considering the integration of many architectures. Figure 4-2 illustrates how different types of architecture need to co-exist.

Question 34

Briefly describe the key points of the ADM cycle.

Answer 34

The ADM is iterative, over the whole process, between phases, and within phases

The breadth of coverage of the enterprise to be defined
The level of detail to be defined
The extent of the time period aimed at, including the number and extent of any intermediate time periods
The architectural assets to be leveraged, including:
Assets created in previous iterations of the ADM cycle within the enterprise
Assets available elsewhere in the industry (other frameworks, systems models, vertical industry models, etc.)
These decisions should be based on a practical assessment of resource and competence availability, and the value that can realistically be expected to accrue to the enterprise from the chosen scope of the architecture work
As a generic method, the ADM is intended to be used by enterprises in a wide variety of different geographies and applied in different vertical sectors/industry types

Question 35

Describe a typical set of steps, such as those for Phase D.

Answer 35

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 the Architecture Definition Document

Question 36

Describe the versioning convention for deliverables used in Phases A to D.

Answer 36

During phase A: Architecture Definition 0.1- high level outline delivered

Phase B: Arch. Defn. 1.0- formally reviewed and delivered, detailed deliverable

Question 37

Briefly explain the seven aspects of the approach undertaken in the Preliminary Phase 1) Defining the enterprise

Answer 37

One of the main challenges of Enterprise Architecture is that of enterprise scope.

The scope of the enterprise, and whether it is federated, will determine those stakeholders who will derive most benefit from the Enterprise Architecture Capability. It is imperative that a sponsor is appointed at this stage to ensure that the resultant activity has resources to proceed and the clear support of the business management. The enterprise may encompass many organizations and the duties of the sponsor are to ensure that all stakeholders are included in defining, establishing, and using the Architecture Capability.

Question 38

Briefly explain the seven aspects of the approach undertaken in the Preliminary Phase -2) organizational context

Answer 38

In order to make effective and informed decisions about the framework for architecture to be used within a particular enterprise, it is necessary to understand the context surrounding the architecture framework. Specific areas to consider would include:

The commercial models for Enterprise Architecture and budgetary plans for Enterprise Architecture activity; where no such plans exist, the Preliminary Phase should be used to develop a budget plan
The stakeholders for architecture in the enterprise; their key issues and concerns
The intentions and culture of the organization, as captured within board business directives, business imperatives, business strategies, business principles, business goals, and business drivers
Current processes that support execution of change and operation of the enterprise, including the structure of the process and also the level of rigor and formality applied within the organization
Areas for focus should include:

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
The Baseline Architecture landscape, including the state of the enterprise and also how the landscape is currently represented in documentation form
The skills and capabilities of the enterprise and specific organizations that will be adopting the framework
Review of the organizational context should provide valuable requirements on how to tailor the architecture framework in terms of:

Level of formality and rigor to be applied
Level of sophistication and expenditure required
Touch-points with other organizations, processes, roles, and responsibilities
Focus of content coverage

Question 39

Briefly explain the seven aspects of the approach undertaken in the Preliminary Phase- •3) Defining the requirements for architecture work

Answer 39

The business imperatives behind the Enterprise Architecture work drive the requirements and performance metrics for the architecture work. They should be sufficiently clear so that this phase may scope the business outcomes and resource requirements, and define the outline enterprise business information requirements and associated strategies of the Enterprise Architecture work to be done. For example, these may include:

1-Business requirements
2-Cultural aspirations
3-Organization intents
4-Strategic intent
5-Forecast financial requirements
Significant elements of these need to be articulated so that the sponsor can identify all the key decision-makers and stakeholders involved in defining and establishing an Architecture Capability.

Question 40

Briefly explain the seven aspects of the approach undertaken in the Preliminary Phase 4) Defining the Architecture Principles that will inform any architecture work

Answer 40

The definition of Architecture Principles is fundamental to the development of an Enterprise Architecture. Architecture work is informed by business principles as well as Architecture Principles. The Architecture Principles themselves are also normally based in part on business principles. Defining business principles normally lies outside the scope of the architecture function. However, depending on how such principles are defined and promulgated within the enterprise, it may be possible for the set of Architecture Principles to also restate, or cross-refer to a set of business principles, business goals, and strategic business drivers defined elsewhere within the enterprise. Within an architecture project, the architect will normally need to ensure that the definitions of these business principles, goals, and strategic drivers are current, and to clarify any areas of ambiguity.

Question 41

Briefly explain the seven aspects of the approach undertaken in the Preliminary Phase 5) Defining the framework to be used

Answer 41

The main frameworks suggested to be co-ordinated with the TOGAF framework are:

Business Capability Management -that determines what business capabilities are required to deliver business value including the definition of return on investment and the requisite control/performance measures
Project/Portfolio Management Methods -that determine how a company manages its change initiatives
Operations Management Methods -that describe how a company runs its day-to-day operations, including IT
Solution Development Methods -that formalize the way that business systems are delivered in accordance with the structures developed in the IT architecture

Question 42

Briefly explain the seven aspects of the approach undertaken in the Preliminary Phase 6) - Defining the relationships between management frameworks

Answer 42

Business planning -at the strategy level provides the initial direction to Enterprise Architecture. Updates at the annual planning level provide a finer level of ongoing guidance. Capability-based planning is one of many popular techniques for business planning.

Enterprise Architecture structures- the business planning into an integrated framework that regards the enterprise as a system or system of systems. This integrated approach will validate the business plan and can provide valuable feedback to the corporate planners. In some organizations, the Enterprise Architects have been moved to or work very closely with the strategic direction groups. The TOGAF approach delivers a framework for Enterprise Architecture.

Project/portfolio management - is the delivery framework that receives the structured, detailed direction that enables them to plan and build what is required, knowing that each assigned deliverable will be in context (i.e., the piece of the puzzle that they deliver will fit into the corporate puzzle that is the Enterprise Architecture). Often this framework is based upon the Project Management Institute or UK Office of Government Commerce (PRINCE2) project management methodologies. Project architectures and detailed out-of-context design are often based upon systems design methodologies.

Question 43

Briefly explain the seven aspects of the approach undertaken in the Preliminary Phase 7) Outlining the enterprise architecture maturity

Answer 43

Level 0: None
No Enterprise Architecture program. No Enterprise Architecture to speak of.

Level 1: Initial
Informal Enterprise Architecture process underway.

Level 2: Under Development
Enterprise Architecture process is under development.

Level 3: Defined
Defined Enterprise Architecture including detailed written procedures and TRM.

Level 4: Managed
Managed and measured Enterprise Architecture process.

Level 5: Measured
Continuous improvement of Enterprise Architecture process.

Question 44

Explain the purpose of the supporting guidelines and techniques, and the difference between guidelines and techniques.

Answer 44

Guidelines help to adapt the ADM to deal with different scenarios, including different process styles( e.g the use of iteration) and also specfici requirements(e.g.g security)

Techiques support specific tasks within the ADM (e.g defining principles , business scenarios , gap analysis, migration planning, risk managment etc

Question 45

Briefly describe deliverables, artifacts, and building blocks in the context of the Architecture Content Framework

Answer 45

Adeliverableis a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders
(Deliverables represent the output of projects and those deliverables that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time )

Anartifactis an architectural work product that describes an aspect of the architecture
(Artifacts are generally classified as catalogs (lists of things), matrices (showing relationships between things), and diagrams (pictures of things). Examples include a requirements catalog, business interaction matrix, and a use-case diagram.architectural deliverable may contain many artifacts and artifacts will form the content of the Architecture Repository.

A building block represents a (potentially re-usable) component of enterprise capability that can be combined with other building blocks to deliver architectures and solutions
Building blocks can be defined at various levels of detail, depending on what stage of architecture development has been reached. For instance, at an early stage, a building block can simply consist of a name or an outline description. Later on, a building block may be decomposed into multiple supporting building blocks and may be accompanied by a full specification. Building blocks can relate to “architectures” or “solutions”.

Architecture Building Blocks (ABBs)- typically describe required capability and shape the specification of Solution Building Blocks (SBBs); for example, a customer services capability may be required within an enterprise, supported by many SBBs, such as processes, data, and application software

Solution Building Blocks (SBBs) -represent components that will be used to implement the required capability; for example, a network is a building block that can be described through complementary artifacts and then put to use to realize solutions for the enterprise

Question 46

Describe the objectives of the Preliminary Phase.

Answer 46

Set up an EA team and make sure it can do its work -
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 Capability Maturity target
1. Establish the Architecture Capability:
◦ Define and establish the Organizational Model for Enterprise Architecture
◦ Define and establish the detailed process and resources for Architecture Governance

Question 47

Describe the main objectives of Phase A.

Answer 47

1. Establish the Project
2. Identify Stakeholders and Concerns, Business
   Requirements, and Architecture Vision
3. Identify Business Goals and Business Drivers
4. Define Scope
5. Define Constraints
6. Review Architecture Principles, including
   Business Principles
7. Develop Statement of Architecture Work and
   Secure Approval
8. [Conduct an architecture maturity assessment]

Question 48

Briefly explain the two main aspects to the approach in Phase A.

Answer 48

Creating the Architecture Vision - he 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. Architecture Vision describes how the new capability will meet the business goals and strategic objectives and address the stakeholder concerns when implemented.

Integral to the Architecture Vision is an understanding of emerging technologies and their potential impact on industries and enterprises, without which many business opportunities may be missed.

Clarifying and agreeing the purpose of the architecture effort is one of the key parts of this activity, and the purpose needs to be clearly reflected in the vision that is created. Architecture projects are often undertaken with a specific purpose in mind - a specific set of business drivers that represent the return on investment for the stakeholders in the architecture development. Clarifying that purpose, and demonstrating how it will be achieved by the proposed architecture development, is the whole point of the Architecture Vision.

Question 49

Briefly explain the two main aspects to the approach in Phase A

Answer 49

Business Scenarios - Business scenarios are an appropriate and useful technique to discover and document business requirements, and to articulate an Architecture Vision that responds to those requirements. Business scenarios may also be used at more detailed levels of the architecture work (e.g., in Phase B) and are described in the TOGAF® Series Guide: Business Scenarios.

Question 50

Describe the main objectives of Phase B.

Answer 50

Establish or refine:

1. An Architecture Ontology
2. The Architecture Process
3. The Architecture Viewpoints and Views
4. The Architecture Framework(s)
5. The Architecture Accountability Matrix
6. The Architecture Performance Metrics
7. The Architecture Governance Framework

OR

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 upon gaps between the Baseline and Target Business Architectures

Question 51

Briefly explain the main aspects of the approach in Phase B - Developing the Baseline Description

Answer 51

If an enterprise has existing Architecture Descriptions, they should be used as the basis for the Baseline Description. This input may have been used already in Phase A in developing the Architecture Vision, such as the business capability map or a core set of value streams as introduced in 6.5.2 Creating the Architecture Vision , and may be sufficient in itself for this baseline.

The reasons to update these materials include having a missing business capability, a new value stream, or changed organizational unit that has not previously been assessed within the scope of the Enterprise Architecture project. 7.5.3 Applying Business Capabilities to 7.5.5 Applying the Organization Map address the use of core Business Architecture methods to model the Business Architecture driven by the strategy scope from Phase A. Note that putting these methods into action to drive a focus and target state for later architecture work does not mean the fundamental frameworks from Phase A, such as a common enterprise business capability map, necessarily change but rather that they are applied in a manner driven by the scope and needs of the specific Enterprise Architecture project.

Question 52

Briefly explain the main aspects of the approach in Phase B -Business Modeling

Answer 52

Business modeling and strategy assessments are effective techniques for framing the target state of an organization’s Business ArchitectureThe output from that activity is then used to articulate the business capabilities, organizational structure, and value streams required to close gaps between the current and target state

Question 53

Briefly explain the main aspects of the approach in Phase B - • Using the Architecture Repository

Answer 53

As part of Phase B, the architecture team will need to consider what relevant Business Architecture resources are available from the Architecture Repository

Question 54

Describe the main objectives of Phase C.

Answer 54

The Data Architecture
of the EA practice would:
1. Specify and govern the structure of the
organization’s Enterprise Continuum and
Architecture Repository
2. Define the data architecture (the
metamodel of the architecture practice)
based on the architecture framework

0r

Develop the Target Information Systems Architectures, 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

Question 55

Briefly explain the approach in Phase C recommended by TOGAF - • Key considerations for Data Architecture

Answer 55

A clear definition of which application components in the landscape will serve as the system of record or reference for enterprise master data

Will there be an enterprise-wide standard that all application components, including software packages, need to adopt?

Clearly understand how data entities are utilized by business functions, processes, and services

Clearly understand how and where enterprise data entities are created, stored, transported, and reported

What is the level and complexity of data transformations required to support the information exchange needs between applications?

What will be 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.)?

Question 56

Briefly explain the approach in Phase C recommended by TOGAF - • Using the Architecture Repository

Answer 56

As part of this phase, the architecture team will need to consider what relevant Data Architecture resources are available in the organization’s Architecture Repository

Question 57

Describe the main objectives of Phase D.

Answer 57

Technology Architecture: Focus here is on
architecture of IT platforms, especially hardware
and communications. It’s important to separate the
different concerns of business, information systems
and technology stakeholders.

0r

The Technology Architecture
of the EA practice would:
1. Define technology infrastructure supporting
the architecture practice

or

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

Question 58

Briefly explain the approach to Phase D including:

• Using the Architecture Repository

Answer 58

As part of Phase D, the architecture team will need to consider what relevant Technology Architecture resources are available in the Architecture Repository
• Existing IT services as documented in the IT repository or IT service catalog
• The adopted technical reference model, if applicable
• Technology models relevant to Common Systems Architectures
• The Open Group has a Reference Model for Integrated Information Infrastructure (III-RM) - see the TOGAF® Series Guide: The TOGAF Integrated Information Infrastructure Reference Model (III-RM) - that focuses on the application-level components and underlying services necessary to provide an integrated information infrastructure

Question 59

Describe the main objectives of Phase E.

Answer 59

Identify organizational change that is
required and how this will be achieved, Opportunities & Solutions: Here we move away
from a wholly architectural perspective to figure out
how you’re going to deliver, fund and resource the
changes.

or

Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
Define the overall solution building blocks to finalize the Target Architecture based on the Architecture Building Blocks (ABBs)

Question 60

Briefly explain the approach to Phase E.

Answer 60

Phase E concentrates on how to deliver the architecture. It takes into account the complete set of gaps between the Target and Baseline Architectures in all architecture domains, and logically groups changes into work packages within the enterprise’s portfolios. This is an effort to build a best-fit roadmap that is based upon the stakeholder requirements, the enterprise’s business transformation readiness, identified opportunities and solutions, and identified implementation constraints. The key is to focus on the final target while realizing incremental business value.

Phase E is the initial step on the creation of the Implementation and Migration Plan which is completed in Phase F. It provides the basis of a well considered Implementation and Migration Plan that is integrated into the enterprise’s portfolio in Phase F.
The following four concepts are key to transitioning from developing to delivering a Target Architecture:

Architecture Roadmap
Work Packages
Transition Architectures
Implementation and Migration Plan

Question 61

Describe the main objectives of Phase F.

Answer 61

Apply the architecture process
and framework to establish
the architecture practice
in the organization,Migration Planning: The detailed planning here is
more the province of project managers than architects,
but get involved to make sure commitment is in line
with the architecture vision

or

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

Question 62

Briefly explain the approach to Phase F -

Answer 62

The focus of Phase F is the creation of an Implementation and Migration Plan in co-operation with the project and portfolio managers.

Phase E provides an incomplete Architecture Roadmap and Implementation and Migration Plan that address the Statement of Architecture Work. In Phase F this Roadmap and the Implementation and Migration Plan are integrated with the enterprise’s other change activity.

Activities include assessing the dependencies, costs, and benefits of the various migration projects within the context of the enterprise’s other activity. The Architecture Roadmap, Version 0.1 and Implementation and Migration Plan, Version 0.1 from Phase E will form the basis of the final Implementation and Migration Plan that will include portfolio and project-level detail.

Question 63

Describe the main objectives of Phase G.

Answer 63

1. Implement the architecture practice
2. Adopt more structured and discipline,
   Along with
   the policing role of monitoring each project
   and solution, this plase needs a delicate political
   sensitivity to remind people of the long term vision
   and persuade them not to compromise.

or

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

Question 64

Describe the main objectives of Phase H

Answer 64

1. Manage changes to the
   architecture of the
   architecture practice,When projects
   and solutions are unable to meet original expectations
   - due to cuts in spending, changes in priority or lack of
   funding and resources - you need to revisit the other
   phases to address the consequences.

or

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

Question 65

Briefly explain the approach to Phase H including:

• Drivers for change

Answer 65

There are also probably drivers for change which are often bottom-up, based upon modifying the existing infrastructure to enhance functionality. Enterprise Architecture changes this paradigm by a strategic top-down approach to a degree, although the delivery of increments makes the equation more complex.

In addition, there are many technology-related drivers for architecture Change Requests. For example:

New technology reports
Asset management cost reductions
Technology withdrawal
Standards initiatives

In addition, there are business drivers for architecture change, including:

Business-as-usual developments
Business exceptions
Business innovations
Business technology innovations
Strategic change

Question 66

Briefly explain the approach to Phase H including: • Enterprise architecture management process

Answer 66

he Enterprise Architecture change management process needs to determine how changes are to be managed, what techniques are to be applied, and what methodologies used. The process also needs a filtering function that determines which phases of the architecture development process are impacted by requirements. For example, changes that affect only migration may be of no interest in the architecture development phases.

Simplification change: a simplification change can normally be handled via change management techniques
Incremental change: an 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 (see 15.5.3 Guidelines for Maintenance versus Architecture Redesign for guidelines)
Re-architecting change: a re-architecting change requires putting the whole architecture through the architecture development cycle again

Question 67

Briefly explain the approach to Phase H including: • Guidelines for maintenance versus architecture redesign

Answer 67

A good guideline is:

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
For example:

If the impact is significant for the business strategy, then there may be a need to redo the whole Enterprise Architecture - thus a re-architecting approach
If a new technology or standards emerge, then there may be a need to refresh the Technology Architecture, but not the whole Enterprise Architecture - thus an incremental change
If the change is at an infrastructure level - for example, ten systems reduced or changed to one system - this may not change the architecture above the physical layer, but it will change the Baseline Description of the Technology Architecture; this would be a simplification change handled via change management techniques
In particular, a refreshment cycle (partial or complete re-architecting) may be required if:

The Foundation Architecture needs to be re-aligned with the business strategy
Substantial change is required to components and guidelines for use in deployment of the architecture
Significant standards used in the product architecture are changed which have significant end-user impact; e.g., regulatory changes

Question 68

Briefly explain how Requirements Management fits into the ADM cycle.

Answer 68

At the heart of the
EA role, this is where a good EA can manage diverse
stakeholder concerns and create an integrated view
of how the architecture will evolve. All work products
created or used in the other phases are managed here!

or

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 relevant architecture requirements are available for use by each phase as the phase is executed