TOGAF-Phase B - Business Architecture

TOGAF Standard Courseware V9 Edition
Module 16
Phase B
Business Architecture
V9 Edition Copyright © January 2009
TM
Slide 1 of 34
All rights reserved
Published by The Open Group, January 2009
Copyright © 2009, The Open Group 1

Phase B
Phase B:
Business
Architecture
Business
Architecture
TOGAF is a trademark of The Open Group

in the United States and other countries
TM
Slide 2 of 34 TM

Module Objectives
The objectives of this module are to understand:

• The objectives of Phase B, Business Architecture
• The Approach
• What it consists of
• What inputs are needed for it
• What the outputs are
TM
Slide 3 of 34

Business Architecture Objectives
The objectives of this phase are to:

• Describe the existing Business Architecture (the baseline)
• Develop a target Business Architecture
• Analyze gaps between the baseline and target
• Select architectural viewpoints
• Select tools and techniques for viewpoints
TM
Slide 4 of 34

Approach
• Knowledge of the Business Architecture is a prerequisite
for architecture work in the other domains (Data,
Applications, Technology)
– and so is the first activity that needs to be undertaken.
• Business Strategy defines what to achieve

• Business Architecture describes how to achieve it
• This Phase is often required to demonstrate business
value of subsequent work to key stakeholders.
TM
Slide 5 of 34

Approach
• Scope depends on existing strategy and planning

– Update and verify
– bridge between high-level business drivers, strategy, and
– goals on the one hand, and specific business requirements
– Existing architecture discovery must include all relevant detail
• If there is no existing strategy or planning:
– Identify any existing architecture definitions, then verify and update
– New process definitions may require detailed work
• In both cases, use business scenarios to identify key

business objectives and processes
TM
Slide 6 of 34

Phase B: Inputs
• Request for Architecture Work
• Refined statements of Business
principles, goals and drivers
• Capability Assessment
• Communications Plan
• Organization model for enterprise
architecture
• Tailored Architecture Framework
• Approved Statement of Architecture
Work
• Architecture Principles
• Enterprise Continuum
• Architecture Repository
• Architecture Vision
– including the first versions of the
architectures
TM
Slide 7 of 34

Steps
The order of the steps 9. Create Architecture
should be adapted to Definition Document
the situation. 8. Finalize the Business
Architecture
In particular you should
7. Conduct formal stakeholder review
determine whether it is
appropriate to do the 6. Resolve impacts across the
Baseline Business Architecture Landscape
Architecture or Target 5. Define roadmap components
Business Architecture
development first 4. Perform gap analysis
3. Develop Target Business Architecture Description
2. Develop Baseline Business Architecture Description
1. Select reference models, viewpoints, and tools
TM
Slide 8 of 34

Step 1: Select reference models,

viewpoints, and tools
• Select relevant Business Architecture resources from the
Architecture Repository, on the basis of the business drivers,
stakeholders and concerns.
• Select relevant Business Architecture viewpoints that will enable
the architect to demonstrate how the stakeholder concerns are
being addressed.
• Identify appropriate tools and techniques to be used for capture,
modeling, and analysis with the viewpoints. These may be
simple documents or spreadsheets, or more sophisticated
modeling tools and techniques, such as activity models,
business process models, use-case models, etc.
• ctd.
TM
Slide 9 of 34

TOGAF 9 Viewpoints
Preliminary Phase Phase B, Business Architecture Phase C, Data Architecture Phase C, Application Architecture
• Organization/Actor catalog
• Principles • Driver/Goal/Objective catalog • Application Portfolio catalog
catalog • Role catalog • Data Entity/Data • Interface catalog
• Business Service/Function catalog Component catalog • System/Organization matrix
• Location catalog • Data Entity/Business • Role/System matrix
• Process/Event/Control/Product Function matrix • System/Function matrix
catalog • System/Data matrix • Application Interaction matrix
• Contract/Measure catalog • Class diagram • Application Communication
• Business Interaction matrix • Data Dissemination diagram
• Actor/Role matrix diagram • Application and User Location
Phase A, Architecture • Business Footprint diagram •
Note:
Data Security diagram diagram
Vision • Business Service/Information diagram • System Use-Case diagram
• Functional Decomposition diagram Module 16A provides
• Class Hierarchy
diagram • Enterprise Manageability
• Stakeholder Map • Product Lifecycle diagram diagram
matrix • Goal/Objective/Service diagram
detailed
• information• on
Data Migration diagram
Process/System Realization
• Data Lifecycle diagram
• Value Chain
diagram
•
•
Use-Case diagram Phase D Catalogs, Matrices
Organization Decomposition diagram •
diagram
Software Engineering diagram
• Solution Concept • Process Flow diagram and Diagrams • Application Migration diagram
diagram • Event diagram • Software Distribution diagram
Phase D, Technology Architecture Phase E. Opportunities & Requirements Management

• Technology Standards catalog Solutions • Requirements catalog
• Technology Portfolio catalog • Project Context
• System/Technology matrix diagram
• Environments and Locations diagram • Benefits diagram
• Platform Decomposition diagram
• Processing diagram
• Networked Computing/Hardware diagram
• Communications Engineering diagram
TM
Slide 10 of 34


• Determine Overall Modeling Process
– For each viewpoint, select the models needed to support the
specific view required, using the selected tool or method. Confirm
all stakeholders’ concerns are addressed. If not, use business
scenarios to discover business requirements.
• Identify Required Service Granularity Level, Boundaries, and
Contracts
– identify which components of the architecture are functions and
which are services. Specify required service levels. This can lead to
the generation of formal Service Level Agreements.
• ctd.
TM
Slide 11 of 34

Modeling Examples
TM
Slide 12 of 34


• Identify Required Catalogs of Business Building Blocks
– Catalogs form the raw material for development of matrices and
views and also act as a key resource for portfolio managing
business and IT capability.
• ctd.
TM
Slide 13 of 34


• Identify Types of Requirement to be Collected,
– e.g. Functional requirements, Non-functional requirements,
Assumptions, Constraints, Domain-specific Business
Architecture principles, Policies, Standards, Guidelines,
Specifications
TM
Slide 14 of 34

Step 2: Develop Baseline Business

Architecture Description
• Must be complete, but without unnecessary detail
• If possible, identify the relevant Business
Architecture building blocks, drawing on the
Architecture Repository
• If not, develop a new architecture description:
– use the models identified within Step 1 as a guideline
TM
Slide 15 of 34

Step 3: Develop Target Business

Architecture Description
• If possible, identify the relevant Business Architecture
building blocks, drawing on the Architecture
Repository
• If not, develop a new architecture description:
– use the models identified within Step 1 as a guideline
TM
Slide 16 of 34

Step 4: Perform Gap Analysis

Verify the architecture models for internal consistency and accuracy:
• Perform trade-off analysis to resolve conflicts (if any) among the different
views
• Validate that the models support the principles, objectives, and
constraints
• Note changes to the viewpoint represented in the selected models from
the Architecture Repository, and document
• Test architecture models for completeness against requirements
• Identify gaps between the baseline and target:
– Create the gap matrix (see next slide).
– Identify building blocks to be carried over, classifying them as either changed
or unchanged.
– Identify eliminated building blocks.
– Identify new building blocks.
– Identify gaps and classify as those that should be developed and those that
should be procured. Continued…
TM
Slide 17 of 34

Gap analysis highlights services and/or functions that have

been omitted or are yet to be developed; these are the
gaps. They should be marked as ‘correctly eliminated’ or
as ‘to be addressed by reinstating, developing or
procuring’.
1. Create a matrix of business ABBs:
– Put ‘Current architecture’ + ‘New Services’ on the vertical axis
– Put ‘Target Architecture’ + ‘Eliminated Services’ on the horizontal
axis
2. Mark ABBs that are common to both as ‘Included’

Continued…
TM
Slide 18 of 34


3. Review blocks missing from current:
– Confirm as ‘Eliminated’
– Else mark for ‘Review’
4. Mark any ‘New Services’ as gap to be filled by acquiring

function by either:
– Development
– Procurement
TM
Slide 19 of 34

Gap Analysis Exercise
Given the following ABBs in the baseline architecture:

• Broadcast services, Video conferencing services, Enhanced
telephony services, Shared screen services.
And the following ABBs in the target architecture:
• Video conferencing services, Enhanced telephony services,
Mailing list services.
Assume that ‘Shared screen services’ has been
unintentionally excluded and that the ‘Enhanced telephony
services’ of the baseline may match those needed.
Draw the gap analysis matrix.
TM
Slide 20 of 34

Gap Analysis: Answer
TM
Slide 21 of 34

Step 5: Define roadmap components
• The initial Business Architecture roadmap will be used as

raw material to support more detailed definition of a
consolidated, cross-discipline roadmap within the
Opportunities & Solutions phase.
TM
Slide 22 of 34

Step 6: Resolve impacts across the

Architecture Landscape
• Architecture artifacts in the Architecture Landscape should
be examined to identify:
– Does this Business Architecture create an impact on any pre-
existing architectures?
– Have recent changes been made that impact on the Business
Architecture?
– Are there any opportunities to leverage work from this Business
Architecture in other areas of the organization?
– Does this Business Architecture impact other projects ?
– Will this Business Architecture be impacted by other projects?
TM
Slide 23 of 34

Step 7: Conduct Formal Stakeholder

Review
• This is a formal review of the model and building blocks
selected.
• The purpose is to compare proposed business architecture
against the SOW.
• It is possible to loop back to earlier steps if necessary.
TM
Slide 24 of 34

Step 8: Finalize the Business

Architecture
• Select standards for each of the ABBs, reusing where
possible from the Architecture Repository.
• Fully document each ABB.
• Cross check the overall architecture against the business
goals.
• Document final requirements traceability report.
• Document final mapping of the architecture within the
Architecture Repository. From the selected ABBs, identify
those that might be reused and publish via the architecture
repository.
Continued
TM
Slide 25 of 34

Step 9: Create Architecture Definition

Document
• Document the rationale for all building block decisions in
the architecture definition document.
• Prepare the Business sections of the architecture definition
document report.
• If appropriate, use reports and/or graphics generated by
modeling tools to demonstrate key views of the
architecture. Route the document for review by relevant
stakeholders, and incorporate feedback.
TM
Slide 26 of 34

Phase B: Outputs
• Statement of Architecture
Work
• Validated business
principles, goals and
drivers
• Elaborated Business
Architecture principles
• Draft Architecture Definition
Document
• Draft Architecture Requirements
Specification
• Business Architecture
components of an Architecture
Roadmap
TM
Slide 27 of 34

Architecture Definition Document
• Scope • Rationale and justification for

• Goals, objectives, and architectural approach
constraints • Mapping to Architecture
• Architecture principles Repository:
• Baseline Architecture – Mapping to Architecture
Landscape
• Architecture models (for each
– Mapping to reference models
state to be modeled):
– Mapping to standards
– Business Architecture models
– Re-use assessment
– Data Architecture models
• Gap analysis
– Application Architecture models
– Technology Architecture models • Impact assessment
TM
Slide 28 of 34

Architecture Definition Document –

Business Architecture Components
• Baseline Business Architecture, if – Business processes, including
appropriate – this is a description of measures and deliverables
the existing Business Architecture
– Business roles, including
• Target Business Architecture, development and modification of
including:
skills requirements
– Organization structure – identifying
business locations and relating them – Business data model
to organizational units – Correlation of organization and
– Business goals and objectives – for functions – relate business functions
the enterprise and each
organizational unit to organizational units in the form
– Business functions – a detailed, of a matrix report
recursive step involving successive • Views corresponding to the selected
decomposition of major functional
areas into sub-functions viewpoints addressing key
– Business services – the services stakeholder concerns
that the enterprise and each
enterprise unit provides to its
customers, both internally and
externally
TM
Slide 29 of 34

Architecture Requirements Specification
• Success measures
• Architecture requirements
• Business service contracts
• Application service contracts
• Implementation guidelines
• Implementation specifications
• Implementation standards
• Interoperability requirements
• Constraints
• Assumptions
TM
Slide 30 of 34

Architecture Requirements Specification

– Business Architecture Components
• Gap analysis results
• Technical requirements
• Updated business requirements
TM
Slide 31 of 34

Summary
• The objective of Phase B is

to document the
fundamental organization
of a business
– Embodied in its business
processes and people
– Their relationships to each
other and the environment
– The principles governing its
design and evolution
– How the organization meets
its business goals
TM
Slide 32 of 34

Test Yourself Question
Q. Choose the correct ending for the following phrase:

“Business Architecture is the first architecture activity undertaken because
…”
A. It is often necessary to demonstrate the business value of the overall
architecture activity
B. It provides knowledge that is a prerequisite for undertaking architecture
work in the other domains (data, applications, technology)
C. It can be used to demonstrate the return on investment to key
stakeholders
D. It embodies the fundamental organization of a business and shows
how an organization meets its business goals
E. All of the above
TM
Slide 33 of 34

Phase B
Phase B:
Business
Architecture
TOGAF is a trademark of The Open Group

in the United States and other countries
TM
Slide 34 of 34 TM

TOGAF-Phase B - Business Architecture

Uploaded by

Copyright:

Available Formats

TOGAF-Phase B - Business Architecture

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TOGAF-Phase B - Business Architecture

Uploaded by

Copyright:

Available Formats

TOGAF Standard Courseware V9 Edition

V9 Edition Copyright © January 2009

Copyright © 2009, The Open Group 1

TOGAF is a trademark of The Open Group

Copyright © 2009, The Open Group 2

The objectives of this module are to understand:

Copyright © 2009, The Open Group 3

Business Architecture Objectives

The objectives of this phase are to:

Copyright © 2009, The Open Group 4

• Business Strategy defines what to achieve

Copyright © 2009, The Open Group 5

• Scope depends on existing strategy and planning

• In both cases, use business scenarios to identify key

Copyright © 2009, The Open Group 6

Copyright © 2009, The Open Group 7

3. Develop Target Business Architecture Description

2. Develop Baseline Business Architecture Description

1. Select reference models, viewpoints, and tools

Copyright © 2009, The Open Group 8

Step 1: Select reference models,

Copyright © 2009, The Open Group 9

Phase D, Technology Architecture Phase E. Opportunities & Requirements Management

Copyright © 2009, The Open Group 10

Step 1: Select reference models,

Copyright © 2009, The Open Group 11

Copyright © 2009, The Open Group 12

Step 1: Select reference models,

Copyright © 2009, The Open Group 13

Step 1: Select reference models,

Copyright © 2009, The Open Group 14

Step 2: Develop Baseline Business

Copyright © 2009, The Open Group 15

Step 3: Develop Target Business

Copyright © 2009, The Open Group 16

Step 4: Perform Gap Analysis

Copyright © 2009, The Open Group 17

Step 4: Perform Gap Analysis

Gap analysis highlights services and/or functions that have

2. Mark ABBs that are common to both as ‘Included’

Copyright © 2009, The Open Group 18

Step 4: Perform Gap Analysis

4. Mark any ‘New Services’ as gap to be filled by acquiring

Copyright © 2009, The Open Group 19

Gap Analysis Exercise

Given the following ABBs in the baseline architecture:

Copyright © 2009, The Open Group 20

Gap Analysis: Answer

Copyright © 2009, The Open Group 21

Step 5: Define roadmap components

• The initial Business Architecture roadmap will be used as

Copyright © 2009, The Open Group 22

Step 6: Resolve impacts across the

Copyright © 2009, The Open Group 23

Step 7: Conduct Formal Stakeholder

Copyright © 2009, The Open Group 24

Step 8: Finalize the Business

Copyright © 2009, The Open Group 25

Step 9: Create Architecture Definition

Copyright © 2009, The Open Group 26