Personal PDF Edition.

For non-commercial use only

TOGAF Standard Courseware V9 Edition

Sample Catalogs,
Matrices
and Diagrams
v2.02: 7 April 2011
Download the bundle from
http://www.opengroup.org/bookstore/catalog/i093.htm

V9 Edition Copyright © 2009-2011

Slide 1 ©2009-2011 The Open Group, All Rights Reserved

The Open Group gratefully acknowledges the contributions
All rights reserved
Published by The Open Group, 2011 from SAP and Capgemini

© 2009-2011 The Open Group, All Rights Reserved

Sample
Catalogs,
Matrices and
Diagrams

TOGAF is a registered trademark of The

Open Group in the United States and other
countries

Slide 2 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 1

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

Objectives

The objectives of this presentation are to illustrate:

• TOGAF 9 Catalogs, Matrices and Diagrams
• What they consist of
• Examples
• How they can be used
The examples shown are illustrative.
The exact format of the catalogs,
matrices and diagrams will depend
on the tools used and adaptations to
TOGAF for the specific EA.

Slide 3 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

TOGAF 9
Catalogs, Matrices and Diagrams
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 • Data Security diagram diagram
Vision • Business Service/Information diagram • Class Hierarchy • System Use-Case diagram
• Functional Decomposition diagram diagram • Enterprise Manageability
• Stakeholder Map • Product Lifecycle diagram • Data Migration diagram diagram
matrix • Goal/Objective/Service diagram • Data Lifecycle diagram • Process/System Realization
• Value Chain • Business Use-Case diagram diagram
diagram • Organization Decomposition diagram • Software Engineering diagram
• Solution Concept • Process Flow diagram • 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

Slide 4 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 2

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

P Preliminary Phase
Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Principles Catalog

Matrices

Slide 5 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

P Catalogs
Catalog Purpose
Principles The Principles catalog captures principles of the business and architecture
principles that describe what a "good" solution or architecture should look
Catalog like. Principles are used to evaluate and agree an outcome for architecture
decision points. Principles are also used as a tool to assist in architectural
governance of change initiatives.

The Principles catalog contains the following metamodel entities:

* Principle

Slide 6 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 3

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

A Architecture Vision
Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Value Chain Diagram
Matrices
• Stakeholder Map Matrix
• Solution Concept Diagram

Slide 7 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

A Example Stakeholder Map

Matrix
Stakeholder Involvement Class Relevant Artifacts
CxO This stakeholder group is interested in the Keep Business Footprint
high-level drivers, goals and objectives of Satisfied Goal/Objective/Service
the organization, and how these are Model
translated into an effective process and IT Organization Chart
architecture to advance the business

Program This stakeholder group is interested in Keep Roadmaps

Management prioritizing, funding, and aligning change Satisfied Business Footprint
Office activity. An understanding of project content Application
and technical dependencies adds a further Communication
dimension of richness to portfolio
management and decision making. Functional
Decomposition

HR Key features of the enterprise architecture Keep Organization Chart

are roles and Actors that support the Informed Organization/Actor/
functions, applications, and technology of Location
the organization. HR are important
stakeholders in ensuring that the correct
roles and actors are represented.

Slide 8 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 4

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

A Example Value Chain Diagram

Source: Wikipedia.org

Slide 9 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

A Value Chain Diagram

Product
Sales Fulfilment Payments Servicing
& Offer

Slide 10 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 5

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

A Value Chain Diagram

Slide 11 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

A Example Solution Concept Diagram

• A high-level representation of the solution envisaged
• A pencil sketch of the expected solution at the outset of the
engagement

Membership
Conference
Attendance
Interest,
Customers Certification
consideration,
join, re-new Publication

Reliable, 24x7,
self-service
infrastructure

Slide 12 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 6

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

A Solution Concept Diagram

Slide 13 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

A Solution Concept Diagram

Today’s use of channels Tomorrow’s use of channels

High Value Tasks

RM
RM From RM
to ST

SERVICE TEAM
SERVICE
TEAM From Service From RM
Team to CC to CC

CALL CENTER

CALL CENTER From Call From Service From RM

Centre to Team to to Online
Online Online

SELF SERVICE SELF SERVICE INTERNET PORTAL

INTERNET PORTAL

Low Value Tasks

Slide 14 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 7

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Business Architecture
Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Organization/Actor catalog • Business Footprint diagram
• Driver/Goal/Objective catalog • Business Service/Information
• Role catalog diagram
• Business Service/Function • Functional Decomposition
catalog diagram
• Location catalog • Product Lifecycle diagram
• Process/Event/Control/Product • Goal/Objective/Service diagram
catalog • Business Use-Case diagram
• Contract/Measure catalog • Organization Decomposition
Matrices diagram
• Business Interaction matrix • Process Flow diagram
• Actor/Role matrix • Event diagram

Slide 15 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Catalogs
Catalog Purpose
Organization/ A definitive listing of all participants that interact with IT, including users and owners
of IT systems.
Actor It contains the following metamodel entities:
Catalog •Organization Unit, Actor Location (may be included in this catalog if an independent
Location catalog is not maintained)

Driver/Goal/ A cross-organizational reference of how an organization meets its drivers in practical

terms through goals, objectives, and (optionally) measures.
Objective It contains the following metamodel entities:
Catalog •Organization Unit, Driver, Goal, Objective, Measure (may optionally be included)

Role Catalog The purpose of the Role catalog is to provide a listing of all authorization levels or
zones within an enterprise. Frequently, application security or behavior is defined
against locally understood concepts of authorization that create complex and
unexpected consequences when combined on the user desktop.
It contains the following metamodel entities:
•Role

Slide 16 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 8

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Catalogs
Catalog Purpose
Business A functional decomposition in a form that can be filtered, reported on, and queried, as
a supplement to graphical Functional Decomposition diagrams.
Service / It contains the following metamodel entities:
Function •Organization Unit,Business Function, Business Service, Information System Service
Catalog (may optionally be included here)

Location A listing of all locations where an enterprise carries out business operations or
houses architecturally relevant assets, such as data centers or end-user computing
Catalog equipment.
It contains the following metamodel entities:
•Location

Process/ The Process/Event/Control/Product catalog provides a hierarchy of processes, events

that trigger processes, outputs from processes, and controls applied to the execution
Event/ of processes. This catalog provides a supplement to any Process Flow diagrams that
Control/ are created and allows an enterprise to filter, report, and query across organizations
and processes to identify scope, commonality, or impact.
Product It contains the following metamodel entities:
Catalog
•Process, Event, Control, Product

Slide 17 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Catalogs
Catalog Purpose
Contract/ A listing of all agreed service contracts and (optionally) the measures
attached to those contracts. It forms the master list of service levels
Measure
agreed to across the enterprise.
Catalog
It contains the following metamodel entities:
•Business Service
•Information System Service (optionally)
•Contract
•Measure

Slide 18 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 9

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Matrices

• Business Interaction matrix

• Actor/Role matrix

Slide 19 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Business Interaction Matrix

• The purpose of this matrix is to depict the relationship

interactions between organizations and business functions
across the enterprise.
Providing Business Services
Consuming Business Services Engineering Procurement Manufacturing Sales and Distribution Customer Service
Engineering
Procurement
Contract for
Contract for supply of
Manufacturing supply of
sales forecasts
materials
Contract for
supply of Contract for
Sales and Distribution
product supply of product
specification
Contract for fulfillment of
Customer Service
customer orders
Slide 20 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 10

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Actor/role Matrix
• The purpose of this matrix is to show which actors perform
which roles, supporting definition of security and skills
requirements.
Infrastructure
Office of Steering Group Business Unit Strategy and Architecture
Implementation
CIO Actors Actors Actors Actors
Actors

Architecture Configuration Manager

Business Unit Application Architect

Head of Strategy and Architecture

Enterprise Infrastructure Architect

Infrastructure Solution Architect
Business Unit Service Owner

External Vendors / Suppliers

Enterprise Design Authority

Technical Design Authority

Head of Implementation
Infrastructure Strategist

Infrastructure Designer
IT Management Forum

Business Unit Head

Enterprise Architect

Project Manager
IT Operations
R = Responsible for carrying out the role
A = Accountable for actors carrying out the role
C = Consulted in carrying out the role
CIO

I = Informed in carrying out the role

Strategy Lifecycle Roles
Architecture Refresh I R A I C C R C C C I I R I C C
Architecture Roadmap I C A I R C C I C R I I R C C I C
Benefits Assessment I I I I I I I I I R R I C A
Change Management C I A I I I R I I I R R C
Framework Refresh C C C C C I C A I I I R C C I
Project Lifecycle Roles
Solution Architecture Vision I I I A I I C C I I R I C C R
Logical Solution Architecture A I I C C I I R I C C C R
Physical Solution Architecture A I I C C I I R I C R C R
Design Governance A I I C C I I R I C R C C
Architecture Configuration Management C I I R R R A

Slide 21 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Diagrams

• Business Footprint diagram

• Business Service/Information diagram
• Functional Decomposition diagram
• Product Lifecycle diagram
• Goal/Objective/Service diagram
• Business Use-Case diagram
• Organization Decomposition diagram
• Process Flow diagram
• Event diagram

Slide 22 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 11

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Business Footprint Diagram

• Describes the links between business goals, organizational
units, business functions, and services, and maps these
functions to the technical components delivering the
required capability.
• Demonstrates only the key facts linking organization unit
functions to delivery services and is utilized as a
communication platform for senior-level (CxO) stakeholders

Slide 23 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Example Business Footprint Diagram

Slide 24 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 12

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Business Footprint Diagram

C0 Order-
to-Cash
C1 C2 C3 C4 C5 Manage

Order

Cash
Business Process Receive Process Distribute Invoice
Accounts
Order Order Goods / Services Customer
Integration Layer Receivable

Store Operations Support Services Supply Chain Mgmt

Functional
Services Layer

User Management Buyer Employee

Exchanges
Supplier Customer Partner
Others
Portal Portal Portal Portal Portal
Layer

Slide 25 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Business Footprint Diagram

SC6 –
SC4 – SC5 - Plan goods Schedule & execute
SC2 – SC3 –
SC1 – Plan &
Plan sales & Establish inventory Define movements and goods movements,
manage the demand plan manufacturing resources in the storage and
operations
plan distribution network transportation
decisions

SC11 - Monthly SC22 – Cross-UOT Demand & Supply Balancing SC51 – Logistics Capacity SC61 – Warehouse
Forecast Generation and LP S&OP validation Planning Management
SC52 – Distribution
SC12 - Monthly Supply Planning – mid- SC62 – Long Distance
Forecast Collaboration SC21 – UOT and LPS Tactical Supply Planning Term Transportation
SC42 – Multi-Plant SC53 – Distribution
SC17 – Forecast SC32 – Inventory Planning Supply Planning – short-
Term SC63– Short-Distance
Weekly Update Management Rules Transportation
Parameter Definition SC54 - Distribution
SC16 – Demand shortage management
explosion for assembly GFB57- Process steps
SC41 – Plant traceability
SC13 – Planned Production Planning SC55 – Deployment
demand consumption SC65 – Transportation
by customer order SC56 – Intra-group administration
exchanges management
SC14 – Allocation
Definition Rules for GFB58 – Product
SC57 – Procurement
ATP (monthly) Traceability
exchanges management
SC15 – Allocation
Definition Rules for SC70 - Inventory Management (physical and planned inventory including internal transfer orders)
ATP (daily)
SC04 - Inventory
SC0 - Referential Norms Definition
GFB64 - Supply Chain Costs & Margin Referential
GFB61 – Supply Chain Referential – Logistics
GFB62 – Supply Chain Referential – Production Process Model
Resource
GFB63 – Demand
GFB65 - Supply Chain Referential – Production & Distribution & Ship to Customer Network
Planning Referential
GFB59 – Product & Services – Client Catalog

GFB50 – Product & Services Referential

GFB51 - Client Referential
SC91 – Demand BI / SC92 – Tactical Planning SC93 – Inventory BI / SC94 – Plant Planning BI SC95 – Distribution SC96 – Logistics BI /
SC9 Reporting BI / Reporting Reporting / Reporting Planning BI / Reporting Reporting

- BI GFB70 – Global Cross-Domain Reporting & Analysis

Slide 26 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 13

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Business Footprint Diagram

Slide 27 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

BBusiness Service/Information Diagram

• Shows the information needed to support one or more
business services.
• Shows what data is consumed by or produced by a
business service and may also show the source of
information.
• Shows an initial representation of the information present
within the architecture and therefore forms a basis for
elaboration and refinement within Phase C (Data
Architecture).

Slide 28 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 14

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

BExample Business Service/Information

Diagram

Basic example

Slide 29 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

BExample Business Service/Information

Diagram

Extended example showing actors

and service interactions

Slide 30 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 15

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

Business Services and

Information Diagram

Slide 31 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

Business Services and

Information Diagram

Slide 32 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 16

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Functional Decomposition Diagram

• It shows on a single page the capabilities of an organization

that are relevant to the consideration of an architecture.
• By examining the capabilities of an organization from a
functional perspective, it is possible to quickly develop
models of what the organization does without being
dragged into extended debate on how the organization
does it.

Slide 33 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Example Functional Decomposition

Diagram

Slide 34 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 17

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Functional Decomposition Diagram

Support Primary

Human Marketing
Business
Admin Finance & Engineering Inventory Manufacturing Distribution
Resources Planning
Sales

Manage Public Develop & Track Plan Human Formulate Develop New Research and Plan Material Plan Engineer
Develop Manufacturing
Relations Financial Plan Resources Strategy Business Technology Requirements Requirements Packages

Acquire Develop and Establish Procure

Provide Legal Appropriate Engineer and Perform Quality Ship
Human Maintain Customer Equipment
Services Funds Resources Business Plan Design Products Material & Tools Engineering Products
Requirements

Perform Develop & Engineer and Convert

Develop Obtain Sales Manage
Audit Manage Design Resources
& Controls Product Cost Employees Commitments Processes Suppliers to Product

Provide Provide
Manage Manage Design Tools Manage Control
Employee Customer
Transportation Payables Services Support and Equipment Inventory Production

Manage Maintain Plant

Maintain Manage Manage Union Engineering Equipment &
Facilities Receivables Activities Changes Tools

Provide Manage
Terminate Active Warranty
Administrative Manage Assets
Services Employment Activities

Slide 35 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Product Lifecycle Diagram

• This assists in understanding the lifecycles of key entities within the

enterprise.
• Understanding product lifecycles is becoming increasingly important
with respect to environmental concerns, legislation, and regulation
where products must be tracked from manufacture to disposal.
• Equally, organizations that create products that involve personal or
sensitive information must have a detailed understanding of the product
lifecycle during the development of Business Architecture in order to
ensure rigor in design of controls, processes, and procedures.
Examples of this include credit cards, debit cards, store/loyalty cards,
smart cards, user identity credentials (identity cards, passports, etc.).

Slide 36 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 18

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Example Product Lifecycle Diagram

Source: Kotler and Armstrong, 2004

Slide 37 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Example Product Lifecycle Diagram

Slide 38 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 19

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Goal/Objective/Service
Diagram
• This defines the ways in which a service contributes to the
achievement of a business vision or strategy.
• Services are associated with the drivers, goals, objectives,
and measures that they support, allowing the enterprise to
understand which services contribute to similar aspects of
business performance.
• This also provides qualitative input on what constitutes high
performance for a particular service.

Slide 39 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Example Goal/Objective/
Service Diagram
rol-CFO
gol-Increase
revenues

rol-VP Marketing rol-VP Sales

obj-creating
obj-"aftersales"
new line of cars
market
by the end of...

Function-
sales and
marketing

c a p -
M a rk e t in g

c a p -P re -
O w n e d
v e h ic a . . .

c a p -
c a m p a ig n

c a p -S a le s

c a p - P r e -s a l e

c a p - O r d e r-
t o - D e l iv e r y
Slide 40 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 20

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Business Use-case Diagram

• This displays the relationships between consumers and

providers of business services.
• Business services are consumed by actors or other
business services and the Business Use-Case diagram
provides added richness in describing business capability
by illustrating how and when that capability is used.
• They help to describe and validate the interaction between
actors and their roles to processes and functions.
• As the architecture progresses, the use-case can evolve
from the business level to include data, application, and
technology details. Architectural business use-cases can
also be re-used in systems design work.

Slide 41 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Example Use-case Diagram

Slide 42 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 21

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

BOrganization Decomposition Diagram

• This describes the links between actor, roles, and location
within an organization tree.
• An organization map should provide a chain of command of
owners and decision-makers in the organization.

Slide 43 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

BExample Organization Decomposition

Diagram
rol-CEO

org-Global
org-Worldwide Public rol-Wolrdwide Pharmaceutical org-Wolrdwide talent
org-Chief Medical Officer Research & rol-Vice Chairman org-General Counsel
Affairs and Policy Operations Development and HR
Development

rol-Global Manufacturing loc-US

rol-Field Based Govt.
Relations rol-Wolrdwide rol-Talent
rol-Wolrdwide Medical rol-Intellectual Property
Research Development

rol-CFO

rol-Wolrdwide
loc-Japan/ASIA rol-HealthWelness rol-Employment Law
Communications rol-Safety Risk rol-Worldwide
rol-Worlwide Strategic Planning
Management Development

rol-Planning rol-Line Support

rol-Philanthropy/Stakeholder
rol-Animal Health
Advocacy rol-Worldwide
rol-Science Advocacy loc-Europe
Research Affairs
rol-Diversity and
rol-Litigation/Regulatory
rol-Worldwide Licensing and Inclusion
rol-Worldwide Policy
Business Develoment
rol-Financ ial Strategy

rol-compensation and
rol-Wolrdwide Technology loc-Middle East rol-Business Transactions
rol-Federal Government Benefits
relations
rol-Human Resources

rol-Business Services rol-Complinace Officer

loc-Canada
rol-Site Leader(s)

rol-Wolrdwide Investor
Development

rol-Internal Audit

Slide 44 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 22

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Process Flow Diagram

• This depicts all models and mappings related to the process

metamodel entity.
• It shows sequential flow of control between activities and
may utilize swim-lane techniques to represent ownership
and realization of process steps.
• In addition to showing a sequence of activity, process flows
can also be used to detail the controls that apply to a
process, the events that trigger or result from completion of
a process, and also the products that are generated from
process execution.

Slide 45 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Example Process Flow

Diagram
Start
Step 1 Step 2 Step 3 Step 4

Step 5 Step 6 Step 6 Step 6 STOP

Slide 46 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 23

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Example Process Flow

Technical Support
Diagram
Team
Sales Rep
Pricer Pricer

Start Step 2
Step 1 Step 3 Step 4

Custom app Email CRM

MS Word
MS Excel

Custom Bid
Approver
Customer Rep Customer Rep
Customer Rep

Step 5 Step 6 Step 6 Step 6 STOP

IWF email Consolidation

Tool Spreadsheet

Process Flow (w/Roles & Applications)

Slide 47 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Events Diagram

• This depicts the relationship between events and process.

• Certain events - such as arrival of information (e.g. a
customer’s sales order) or a point in time (e.g. end of fiscal
quarter) cause work and actions to be undertaken within
the business.

Slide 48 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 24

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

B Example Events Diagram

Triggers Impacts/Generates

Event Business
Process result
(e.g. End of Fiscal Quarter)
(e.g. 1Q results reported to
(e.g. Financial Reporting Government Agencies)
Process)

Slide 49 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

B Example Events Matrix

EVENT PROCESS TRIGGERED BUSINESS RESULT(S)

Customer submits Sales order processing ƒ Sales order captured in

sales order ƒ Create & save sales order order book
ƒ Generate acknowledgement
ƒ Confirm receipt of customer order
ƒ Begin order fulfilment activities

Customer submits Custom product configuration ƒ Custom product

request for ƒ Capture requirements from customer configured
custom ƒ Define custom specifications ƒ Customer contract signed
product ƒ Price custom configuration
ƒ Negotiate with customer
ƒ Secure approval from customer regarding
configuration and price

End of quarter Financial reporting process ƒ Financial report generated

Slide 50 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 25

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Data Architecture
Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Data Entity/Data • Class diagram
Component catalog • Data Dissemination
diagram
• Data Security diagram
Matrices • Class Hierarchy diagram
• Data Entity/Business • Data Migration diagram
Function matrix • Data Lifecycle diagram
• System/Data matrix

Slide 51 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Catalogs
Catalog Purpose
•Data To identify and maintain a list of all the data use across the
Entity/Data enterprise, including data entities and also the data components
Component where data entities are stored.
Catalog It contains the following metamodel entities:
•Data Entity
•Logical Data Component
•Physical Data Component

Slide 52 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 26

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Matrices

• Data Entity/Business Function matrix

• System/Data matrix

Slide 53 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Data Entity/Business
Function Matrix
• The purpose of the Data Entity/Business Function matrix is to depict the
relationship between data entities and business functions within the
enterprise.
• The mapping of the Data Entity-Business Function relationship enables
the following to take place:
– Assignment of ownership of data entities to organizations
– Understand the data and information exchange requirements business
services
– Support the gap analysis and determine whether any data entities are
missing and need to be created
– Define system of origin, system of record, and system of reference for data
entities
– Enable development of data governance programs across the enterprise
(establish data steward, develop data standards pertinent to the business
function, etc.)

Slide 54 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 27

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

CExample Data Entity/Business Function

Matrix
BUSINESS
FUNCTION
CUSTOMER BUSINESS CUSTOMER PRODUCT
(Y-AXIS) AND
MASTER PARTNER LEADS MASTER
DATA
ENTITY (X-AXIS)

Customer Relationship ƒ Business partner data ƒ Business partner data ƒ Lead Processing ƒ N/A
Management management service management service Service
ƒ Owner – Sales & ƒ Owner of data entity ƒ Owner – Customer
Marketing business (person or organization) Relationship Manager
unit executive ƒ Function can Create, ƒ Function can only
ƒ Function can Create, read, update and delete Create, read, update
read, update and customer leads
delete customer
master data

Supply Chain ƒ Customer ƒ N/A ƒ N/A ƒ Product data

Management Requirement management service
Processing Service ƒ Owner – Global
ƒ Owner – Supply product development
Chain Manager organization

Slide 55 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C System/Data Matrix

• The purpose of the System/Data matrix is to depict the

relationship between systems (i.e., application components)
and the data entities that are accessed and updated by
them.
• Systems will create, read, update, and delete specific data
entities that are associated with them. For example, a CRM
application will create, read, update, and delete customer
entity information.

Slide 56 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 28

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Example System/Data Matrix

APPLICATION (Y-
DESCRIPTION OR
AXIS) AND DATA DATA ENTITY DATA ENTITY TYPE
COMMENTS
(X-AXIS)

CRM ƒSystem of record for ƒCustomer data ƒMaster data

customer master data

Commerce Engine ƒSystem of record for order ƒSales orders ƒTransactional data
book

Sales Business ƒWarehouse and data mart ƒIntersection of multiple data ƒHistorical data
Warehouse that supports North American entities (e.g. All sales orders
region by customer XYZ and by
month for 2006)

Slide 57 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Diagrams

• Class diagram
• Data Dissemination diagram
• Data Security diagram
• Class Hierarchy diagram
• Data Migration diagram
• Data Lifecycle diagram

Slide 58 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 29

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Class Diagram
• The purpose is to depict the relationships among the critical
data entities (or classes) within the enterprise.
Account
I.A1
Information

Update Customer Actor

Account Profile
P.A12 I.C2 Trigger

Contact Process
P.CS13
Payment
T.P8 P.CS5
Service
Agent Enquiry
Request
A.A4 T.C1
Customer
A.C2 Customer
Appeal Complaint
Information
I.C1 T.C19 T.C16
Slide 59 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Class Diagram

Slide 60 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 30

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Class Diagram

Slide 61 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Data Dissemination Diagram

• The purpose of the Data Dissemination diagram is to show

the relationship between data entity, business service, and
application components.
• The diagram should show how the logical entities are to be
physically realized by application components.
• Additionally, the diagram may show data replication and
system ownership of the master reference for data.

Slide 62 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 31

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

CExample Data Dissemination Diagram

Warehouse
Warehouse
Customer
Order History
Stock

Online
OnlineAccount
Account
Self Service
Self Service

Billing
Billing
Customer
Account Balance
Invoice History

Business Service Data Entities Application

Online Account Self Service Customer ƒWarehouse

ƒBilling

Order History ƒWarehouse

Stock ƒWarehouse

Account Balance ƒBilling

Invoice History ƒBilling

Slide 63 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Data Dissemination Diagram

Slide 64 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 32

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Data Dissemination Diagram

Slide 65 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Data Dissemination Diagram

Slide 66 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 33

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Data Lifecycle Diagram

• The Data Lifecycle diagram is an essential part of managing

business data throughout its lifecycle from conception until
disposal within the constraints of the business process.

Fulfilment Order
New Fulfilled Invoiced Paid Closed Archived Deleted

Customer Order
New Dispatched Closed Archived Deleted

Slide 67 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Data Security Diagram

• The purpose of the Data Security diagram is to depict which

actor (person, organization, or system) can access which
enterprise data.
• This relationship can also be shown in a matrix form
between two objects or can be shown as a mapping.

Slide 68 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 34

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Example Data Security

Diagram

Actor Business Process

Function
Class of Roles (by job
function)

Physical Access Single Sign-on or

Access Control

Location Business
Service
Access Control (levels of
granularity)

Access Control (levels of

granularity) Logical
Application
Component

Slide 69 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Example Data Security Matrix

CLASS OF
BUSINESS TYPE OF
ACTOR ROLES (JOB FUNCTION LOCATION
SERVICE ACCESS
FUNCTION)

Financial Analyst SOA Portfolio Financial Analysis SOA portfolio service ƒ NA (US, CA) ƒ Physical
Financial Analyst ƒ EMEA (UK, DE) ƒ Access Control
ƒ APJ (tables xyz only)

Procurement & Procurement WW Direct Supplier portal ƒ NA (US ƒ Access control

Spend Analyst Management and Procurement Service Midwest)
Control

WW Contracts Not applicable WW Direct Supplier Portal ƒ LA ƒ Access control

System (application) Procurement Service (system to
system)

WW Product Geo Brand Managers WW Direct Supplier Portal ƒ WW (all Geos) ƒ Access Control
Development (Org Procurement Service
Unit)

Slide 70 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 35

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Data Migration Diagram

• The purpose of the Data Migration diagram is to show the

flow of data from the source to the target applications.
• The diagram will provide a visual representation of the
spread of sources/targets and serve as a tool for data
auditing and establishing traceability.

Slide 71 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Example Data Migration

Diagram
“Baseline” Data migration technology “Target”
application components application
components components

ABM
Source of CRM
Customer records
System of Record
CCB for Customer Master

ERP
BDW
Source of order
System of Record for
history
Material Master & Order
history

Source Transformation & Target

MRPA Staging Data Quality Staging
Source of Material
data
SRM
VLC (one
System of Record for
per geo)
Vendor Master &
Source of vendor
Contracts
data

Slide 72 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 36

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Example Data Migration

Mapping

SOURCE LOGICAL TARGET LOGICAL

APPLICATION SOURCE DATA ELEMENT APPLICATION TARGET DATA ELEMENT
COMPONENT COMPONENT

ABM Cust_Name CRM CUSTNAME

Cust_Street_Addr CUSTADDR_LINE1

Cust_Street_Addr CUSTADDR_LINE2

Cust_Street_Addr CUSTADDR_LINE3

Cust_ContactName CUSTCONTACT

Cust_Tele CUSTTELEPHONE

Slide 73 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Class Hierarchy Diagram

• The purpose of the Class Hierarchy diagram is to show the

technical stakeholders a perspective of the class hierarchy.
• This diagram gives the stakeholders an idea of who is using
the data, how, why, and when.

Slide 74 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 37

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Example Class Hierarchy Diagram

Authorised User Keeper
Authorised User Keeper

Vehicle Tester Individual Customer Purchaser/Nominee

Vehicle Tester Individual Customer Purchaser/Nominee

Trainer/Booker
Trainer/Booker

Driver Organisation Manufacturer

Driver Organisation Manufacturer

Driving
DrivingInstructor
Instructor Operator
Operator

Taxi Driver Dealing

Taxi Driver Dealing

Driving Examiner Driving Examiner

Driving Examiner Driving Examiner

Slide 75 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Application Architecture
Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Application Portfolio catalog • Application Communication
• Interface catalog diagram
• Application and User Location
Matrices diagram
• System/Organization matrix • System Use-Case diagram
• Role/System matrix • Enterprise Manageability
• System/Function matrix diagram
• Application Interaction matrix • Process/System Realization
diagram
• Software Engineering diagram
• Application Migration diagram
• Software Distribution diagram

Slide 76 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 38

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Catalogs
Catalog Purpose
Application To identify and maintain a list of all the applications in the enterprise. This list helps to
Portfolio Catalog define the horizontal scope of change initiatives that may impact particular kinds of
applications. An agreed Application Portfolio allows a standard set of applications to
be defined and governed.

It contains the following metamodel entities:

•Information System Service
•Logical Application Component
•Physical Application Component
Interface Catalog The purpose of the Interface catalog is to scope and document the interfaces
between applications to enable the overall dependencies between applications to be
scoped as early as possible.

It contains the following metamodel entities:

•Logical Application Component
•Physical Application Component
•Application communicates with application relationship

Slide 77 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Matrices

• System/Organization matrix
• Role/System matrix
• System/Function matrix
• Application Interaction matrix

Slide 78 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 39

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C System/Organization Matrix

• The purpose of this matrix is to depict the relationship

between systems (i.e., application components) and
organizational units within the enterprise.
• The mapping of the Application Component-Organization
Unit relationship is an important step as it enables the
following to take place:
– Assign usage of applications to the organization units that perform
business functions
– Understand the application support requirements of the business
services and processes carried out by an organization unit
– Support the gap analysis and determine whether any of the
applications are missing and as a result need to be created
– Define the application set used by a particular organization unit

Slide 79 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Example System/Organization Matrix

APPLICATION
(Y-AXIS)
CUSTOMER PROCUREMENT AND CORPORATE
AND HR
SERVICES WAREHOUSING FINANCE
ORGANISATION
UNIT (X-AXIS)

SAP HR X X X

SIEBEL X X

SAP FINANCIALS X X X

PROCURESOFT X X

Slide 80 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 40

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Role/System Matrix

• The purpose of the Role/System matrix is to depict the relationship

between systems (i.e., application components) and the business roles
that use them within the enterprise.
• The mapping of the Application Component-Role relationship is an
important step as it enables the following to take place:
– Assign usage of applications to the specific roles in the organization
– Understand the application security requirements of the business services
and processes supporting the function, and check these are in line with
current policy
– Support the gap analysis and determine whether any of the applications are
missing and as a result need to be created
– Define the application set used by a particular business role; essential in
any move to role-based computing

Slide 81 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Example Role/System Matrix

APPLICATION (Y-
AXIS) AND CALL CENTRE CALL CENTRE CHIEF
FINANCE ANALYST
FUNCTION (X- OPERATOR MANAGER ACCOUNTANT
AXIS)

SAP HR X X X X

SIEBEL X X

SAP FINANCIALS X X X X

PROCURESOFT X X

Slide 82 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 41

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C System/Function Matrix

• The purpose of the System/Function matrix is to depict the

relationship between systems (i.e., application components)
and business functions within the enterprise.
• The mapping of the Application Component-Function
relationship is an important step as it enables the following
to take place:
– Assign usage of applications to the business functions that are
supported by them
– Understand the application support requirements of the business
services and processes carried out
– Support the gap analysis and determine whether any of the
applications are missing and as a result need to be created
– Define the application set used by a particular business function

Slide 83 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Example System/Function
Matrix

APPLICATION (Y-
AXIS) AND CALL CENTRE 1ST WAREHOUSE GENERAL LEDGER
VACANCY FILLING
FUNCTION (X- LINE CONTROL MAINTENANCE
AXIS)

SAP HR X X X X

SIEBEL X X

SAP FINANCIALS X X X

PROCURESOFT X X

Slide 84 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 42

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Diagrams

• Application Communication diagram

• N2 model or Node Connectivity diagram
• Application and User Location diagram
• System Use-Case diagram
• Enterprise Manageability diagram
• Process/System Realization diagram
• Software Engineering diagram
• Application Migration diagram
• Software Distribution diagram

Slide 85 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Application Communication Diagram

• The purpose of the Application Communication diagram is
to depict all models and mappings related to communication
between applications in the metamodel entity.
• It shows application components and interfaces between
components.
• Communication should be logical and should only show
intermediary technology where it is architecturally relevant.

Slide 86 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 43

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Example Application
Communication Diagram

Slide 87 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Application Communication
Diagram

Slide 88 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 44

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Application Communication
Diagram

Slide 89 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C N2 Model

1c
ABC
1a

1b
ABM 2a

3c

CCD 3a

4a
3b
CRM
1d

4b
IPC
3d

Slide 90 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 45

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Information Exchange Matrix

EVENT
LABEL SOURCE DESTINATION DATA ENTITY
TRIGGERED

1a ƒ ABC ƒ ABM ƒ Sales order ƒ New sales

(create order from front
request) end

1b ƒ ABM ƒ ABC ƒ Sales order ƒ Order created

(confirm create) in the backend
ERP system

2a ƒ ABM ƒ CCD ƒ Product catalog ƒ Subscribe/Publi

sh timer

Slide 91 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

CApplication & User Location Diagram

• The purpose of this diagram is to clearly depict the business
locations from which business users typically interact with
the applications, but also the hosting location of the
application infrastructure.
• The diagram enables:
– Identification of the number of package instances needed
– Estimation of the number and the type of user licenses
– Estimation of the level of support needed
– Selection of system management tools, structure, and management
system
– Appropriate planning for the technological components of the
business
– Performance considerations while implementing solutions

Slide 92 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 46

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

CExample Application & User Location

Diagram (part 1)
INTERNAL,
USER
CUSTOMER LOCATION ORG UNIT (USER
APPLICATION USER TYPE BUSINESS
OR ADDRESS BELONGS TO)
LOCATION
PARTNER

CRM Developer Internal NA Western Chicago Sears NA Sales &

Super User Region tower office Marketing
Administrator Chicago
EMEA EMEA Sales
Headquarters, Downtown office
UK Middlesex, London

SAP R/3 Test Engineers Internal Beijing Manufacturing &

Mechanical Manufacturing logistics
Engineers Plant
Procurement
managers

Slide 93 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

CExample Application & User Location

Diagram (part 2)

Slide 94 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 47

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Application and User Location

Diagram

Slide 95 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C Application and User Location

Diagram

Slide 96 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 48

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Application and User Location

Diagram

Slide 97 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C System Use Case Diagram

Source: wikipedia.org

Slide 98 ©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 49

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C System Use Case Diagram

Slide 99 ©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

C System Use Case Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

100

Copyright © 2009-2011, The Open Group 50

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Enterprise Manageability Diagram

• The Enterprise Manageability diagram shows how one or

more applications interact with application and technology
components that support operational management of a
solution.
• Analysis can reveal duplication and gaps, and opportunities
in the IT service management operation of an organization.

Slide ©2009-2011 The Open Group, All Rights Reserved

101

© 2009-2011 The Open Group, All Rights Reserved

C Example Enterprise Manageability

Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

102

Copyright © 2009-2011, The Open Group 51

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Process/System Realization Diagram

• The purpose of the Process/System Realization diagram is
to clearly depict the sequence of events when multiple
applications are involved in executing a business process.
• It enhances the Application Communication diagram by
augmenting it with any sequencing constraints, and hand-off
points between batch and real-time processing.

Slide ©2009-2011 The Open Group, All Rights Reserved

103

© 2009-2011 The Open Group, All Rights Reserved

C Example Process/System
Realization Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

104

Copyright © 2009-2011, The Open Group 52

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Software Engineering
Diagram
• The Software Engineering diagram breaks applications into
packages, modules, services, and operations from a
development perspective.
• It enables more detailed impact analysis when planning
migration stages, and analyzing opportunities and solutions.
• It is ideal for application development teams and application
management teams when managing complex development
environments.

Slide ©2009-2011 The Open Group, All Rights Reserved

105

© 2009-2011 The Open Group, All Rights Reserved

C Example Software
Engineering Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

106

Copyright © 2009-2011, The Open Group 53

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Application/Migration
Diagram
• The Application Migration diagram identifies application
migration from baseline to target application components.
• It enables a more accurate estimation of migration costs
• It should be used to identify temporary applications, staging
areas, and the infrastructure required to support migrations

Slide ©2009-2011 The Open Group, All Rights Reserved

107

© 2009-2011 The Open Group, All Rights Reserved

C Example
Application/Migration Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

108

Copyright © 2009-2011, The Open Group 54

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

C Software Distribution
Diagram
• This diagram is a composite of the Software Engineering
diagram and the Application-User Location diagram.
• Depending on the circumstances, this diagram alone may
be sufficient, or may not be needed.

Slide ©2009-2011 The Open Group, All Rights Reserved

109

© 2009-2011 The Open Group, All Rights Reserved

D Technology Architecture
Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Technology Standards catalog • Environments and Locations
• Technology Portfolio catalog diagram
• Platform Decomposition diagram
• Processing diagram
• Matrices • Networked Computing/Hardware
• System/Technology matrix diagram
• Communications Engineering
diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

110

Copyright © 2009-2011, The Open Group 55

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

D Catalogs

• Technology Standards catalog

• Technology Portfolio catalog

Slide ©2009-2011 The Open Group, All Rights Reserved

111

© 2009-2011 The Open Group, All Rights Reserved

D Catalogs
Catalog Purpose
Technology This documents the agreed standards for technology across the enterprise
covering technologies, and versions, the technology lifecycles, and the
Standards
refresh cycles for the technology.
Catalog
It contains the following metamodel entities:
•Platform Service, Logical Technology Component, Physical Technology
Component
Technology The purpose of this catalog is to identify and maintain a list of all the
technology in use across the enterprise, including hardware, infrastructure
Portfolio
software, and application software. An agreed technology portfolio
Catalog supports lifecycle management of technology products and versions and
also forms the basis for definition of technology standards
It contains the following metamodel entities:
•Platform Service, Logical Technology Component, Physical Technology
Component

Slide ©2009-2011 The Open Group, All Rights Reserved

112

Copyright © 2009-2011, The Open Group 56

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

D Matrices

• System/Technology matrix

Slide ©2009-2011 The Open Group, All Rights Reserved

113

© 2009-2011 The Open Group, All Rights Reserved

D System/Technology Matrix

• The System/Technology matrix documents the mapping of

business systems to technology platform.
• The System/Technology matrix shows:
– Logical/Physical Application Components
– Services, Logical Technology Components, and Physical
Technology Components
– Physical Technology Component realizes Physical Application
Component relationships

Slide ©2009-2011 The Open Group, All Rights Reserved

114

Copyright © 2009-2011, The Open Group 57

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

DExample System/Technology Matrix

LOGICAL PHYSICAL
APPLICATION TECHNOLOGY SERVER ADDRESS IP ADDRESS
COMPONENT COMPONENT

ABM Web server - node 1 [email protected] 10.xx.xx.xx

Web server - node 2 [email protected] 10.xx.xx.xx
Web server - node 3 [email protected] 10.xx.xx.xx
App server – node 1 [email protected] 10.xx.xx.xx
App server – node 2 [email protected] 10.xx.xx.xx
App server – node 3 [email protected] 10.xx.xx.xx
Database server [email protected] 10.xx.xx.xx
(production)
Database server (stating) [email protected] 10.xx.xx.xx
Load balancer and Dispatcher server [email protected] 242.xx.xx.xx
Dispatcher

Slide ©2009-2011 The Open Group, All Rights Reserved

115

© 2009-2011 The Open Group, All Rights Reserved

DExample System/Technology Matrix

TECH HARDWARE HARDWARE SOFTWARE SOFTWARE

FUNCTION LOGICAL PHYSICAL LOGICAL PHYSICAL

Load balancing ƒName – Balancer ƒModel/Type – IBM ƒProduct- IBM Load ƒSW Components
ƒVendor - IBM P7xx balance manager – LB v3.2 (list all
ƒServer Type – ƒSerial Number – ƒVendor - IBM the other
eServer 1S4568 ƒOS – UNIX based components of the
ƒClustered – No ƒProcessor Type - SW product)
ƒNo. of Nodes – N/A RISC Power p5 ƒAIX 10.2.1
ƒServer logical ƒNumber of ƒLicense Type -
address - Processors - 4 way ƒEnterprise wide
[email protected] ƒMemory - 8GB license
ƒMaintenance Window ƒHard drive - 4 TB ƒLicense expiry
– Sun 0100 to 0300 ƒIP - 11.xx.xx.xx date - 12/31/2011

Slide ©2009-2011 The Open Group, All Rights Reserved

116

Copyright © 2009-2011, The Open Group 58

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

DExample System/Technology Matrix

APPLICATION COMPONENT DEPLOYMENT UNIT TECHNOLOGY COMPONENT

ƒLoad Balancer ƒSmart dispatch v1.2 (both ƒLoad balancing server

installation and execution code) ([email protected])

ƒCommerce pages ƒHTML code ƒWeb Server cluster

ƒApplets ([email protected],
ƒJSP [email protected],
[email protected])

ƒCommerce Engine •Order Entry (both installation and •Application Server

execution code) ([email protected],
•Shopping Cart (both installation [email protected])
and execution code)

Slide ©2009-2011 The Open Group, All Rights Reserved

117

© 2009-2011 The Open Group, All Rights Reserved

D Diagrams

• Environments and Locations diagram

• Platform Decomposition diagram
• Processing diagram
• Networked Computing/Hardware diagram
• Communications Engineering diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

118

Copyright © 2009-2011, The Open Group 59

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

DEnvironments and Locations Diagram

• Depicts which locations host which applications
• Identifies what technologies and/or applications are used at
which locations
• Identifies the locations from which business users typically
interact with the applications.
• It should also show the existence and location of different
deployment environments
– including non-production environments, such as development and
pre production.

Slide ©2009-2011 The Open Group, All Rights Reserved

119

© 2009-2011 The Open Group, All Rights Reserved

DExample Environments and Locations

Diagram
app-integration
platform for
suppliers(dexis
)
loc- app-Project
Ludwigsburg managment
app- loc- system
Ludwigsburg
CAD/CAE
loc-Italia app-R&D
system of
systems

loc-Japan tec-Windows tec-Windows tec-RDB

XP Vista

loc-
loc- tec-OCR Ludwigsburg
Stuttgart

loc-Italia app-
loc-USA Build-to-
Order
(BTO)

loc-Japan

Slide ©2009-2011 The Open Group, All Rights Reserved

120

Copyright © 2009-2011, The Open Group 60

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

D Environments and Location

Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

121

© 2009-2011 The Open Group, All Rights Reserved

D Environments and Location

Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

122

Copyright © 2009-2011, The Open Group 61

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

D Environments and Location

Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

123

© 2009-2011 The Open Group, All Rights Reserved

D Platform Decomposition
Diagram
• The Platform Decomposition diagram depicts the
technology platform that supports the operations of the
Information Systems Architecture.
• The diagram covers all aspects of the infrastructure platform
and provides an overview of the enterprise's technology
platform.

Slide ©2009-2011 The Open Group, All Rights Reserved

124

Copyright © 2009-2011, The Open Group 62

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

D Example Platform
Decomposition Diagram
Platform Decomposition (Application Support)

Hardware Software
Logical Technology Physical Technology
Logical Technology Physical Technology
Components Components
Components Components

Tech Function Tech Function Tech Function Tech Function

Web Server Web server layer

Layer Web Server Layer Web Server Layer

Application Layer Application Layer Application Layer Application Layer

Database Layer Database Layer Database Layer Database Layer

Attributes Attributes
• Name ƒ Product Name
• Model/Type ƒ Vendor
• Clusters ƒ OS
• Number of Components ƒ SW components
• Vendor ƒ License Type
• Server Type (mainframe, Mid range, RISC, ƒ License Expiry etc
Intel)
• Server logical name
• IP Address etc

Slide ©2009-2011 The Open Group, All Rights Reserved

125

© 2009-2011 The Open Group, All Rights Reserved

D Platform Decomposition
Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

126

Copyright © 2009-2011, The Open Group 63

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

D Platform Decomposition
Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

127

© 2009-2011 The Open Group, All Rights Reserved

D Processing Diagram

• The Processing diagram focuses on deployable units of

code/configuration and how these are deployed onto the technology
platform.
• The Processing diagram addresses the following:
– Which set of application components need to be grouped to form a
deployment unit
– How one deployment unit connects/interacts with another (LAN, WAN, and
the applicable protocols)
– How application configuration and usage patterns generate load or capacity
requirements for different technology components
• The organization and grouping of deployment units depends on
separation concerns of the presentation, business logic, and data store
layers and service-level requirements of the components.

Slide ©2009-2011 The Open Group, All Rights Reserved

128

Copyright © 2009-2011, The Open Group 64

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

D Example Processing Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

129

© 2009-2011 The Open Group, All Rights Reserved

DNetwork Computing Hardware Diagram

• The purpose of this diagram is to show the "as deployed" logical view of
logical application components in a distributed network computing
environment.
• The diagram is useful for the following reasons:
– Enable understanding of which application is deployed where
– Establishing authorization, security, and access to these technology
components
– Understand the Technology Architecture that support the applications during
problem resolution and troubleshooting
– Isolate performance problems encountered and perform necessary upgrade
to specific physical technology components
– Identify areas of optimization
– Enable application/technology auditing and prove compliance
– Serve as an important tool supporting effective change management
Slide ©2009-2011 The Open Group, All Rights Reserved
130

Copyright © 2009-2011, The Open Group 65

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

DExample Network Computing Hardware

DMZ
Diagram
Internet Zone Intranet Zone

Application
Web Server cluster
Load server Application
(node 3) Database
Web
cluster Database
Balancer Server cluster (ABM (ABM
server
and (node 3)
App Server Staging)
cluster Production)
Dispatcher cluster - node 3
Web (ABM)
server
cluster-
node 3 DFS Distributed File
(ABM) System (html,
images)

Load Web server Database

cluster Application App
Balancer Web server DB
Server (Order Server
and cluster-node Engine)
Dispatcher 2
(eCommerce
)

App Server

Firewall Firewall Firewall

Slide ©2009-2011 The Open Group, All Rights Reserved

131

© 2009-2011 The Open Group, All Rights Reserved

DCommunications Engineering Diagram

• The Communications Engineering diagram describes the
means of communication between assets in the Technology
Architecture
• It takes logical connections between client and server
components and identifies network boundaries and network
infrastructure required to physically implement those
connections.
• It does not describe the information format or content, but
addresses protocol and capacity issues.

Slide ©2009-2011 The Open Group, All Rights Reserved

132

Copyright © 2009-2011, The Open Group 66

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

D Example Communications
Engineering Diagram

Prop col
OBM tary
(Enc
Proto ed)
rie
rypt

G
Au l
th co
Pr oto
oto Pr
co th
l Au

Slide ©2009-2011 The Open Group, All Rights Reserved

133

© 2009-2011 The Open Group, All Rights Reserved

E Opportunities & Solutions

Catalogs, Matrices and Diagrams
Catalogs Diagrams
Matrices • Project Context diagram
• Benefits diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

134

Copyright © 2009-2011, The Open Group 67

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

Project Context Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

135

© 2009-2011 The Open Group, All Rights Reserved

Project Context Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

136

Copyright © 2009-2011, The Open Group 68

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

E Benefits Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

137

© 2009-2011 The Open Group, All Rights Reserved

E Benefits Diagram

Slide ©2009-2011 The Open Group, All Rights Reserved

138

Copyright © 2009-2011, The Open Group 69

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

R Requirements Management
Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Requirements Catalog

Matrices

Slide ©2009-2011 The Open Group, All Rights Reserved

139

© 2009-2011 The Open Group, All Rights Reserved

R Catalogs
Catalog Purpose

Requirements The Requirements catalog captures things that the enterprise needs to do
to meet its objectives. Requirements generated from architecture
Catalog
engagements are typically implemented through change initiatives
identified and scoped during Phase E (Opportunities & Solutions).
Requirements can also be used as a quality assurance tool to ensure that
a particular architecture is fit-for-purpose (i.e., can the architecture meet all
identified requirements).

The Requirements catalog contains the following metamodel entities:

* Requirement
* Assumption
* Constraint
* Gap

Slide ©2009-2011 The Open Group, All Rights Reserved

140

Copyright © 2009-2011, The Open Group 70

 Personal PDF Edition. For non-commercial use only
TOGAF Standard Courseware V9 Edition

Resources

• A full set of downloadable templates is available

– http://www.opengroup.org/bookstore/catalog/i093.htm

Slide ©2009-2011 The Open Group, All Rights Reserved

141

© 2009-2011 The Open Group, All Rights Reserved

Sample
Catalogs,
Matrices and
Diagrams

TOGAF is a registered trademark of The

Open Group in the United States and other
countries

Slide ©2009-2011 The Open Group, All Rights Reserved

142

Copyright © 2009-2011, The Open Group 71