TOGAF V91 Sample Catalogs Matrics Diagrams v3

Personal PDF Edition.
For non-commercial use only

TOGAF® Standard Courseware V9.1
Edition
Sample Catalogs,
Matrices
and Diagrams
v3: December 2011
Download the template bundle from
http://www.opengroup.org/bookstore/catalog/i093.htm
V9.1 Edition Copyright © 2009-2011
The Open Group gratefully acknowledges the contributions

Slide 1 reserved
All rights
from SAP and Capgemini
Published by
©2009-2011 TheThe Open
Open Group,All
Group, 2011
Rights Reserved
© 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
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
Preliminary Phase Phase A, Architecture Vision

• Principles catalog • Stakeholder Map Matrix • Solution Concept diagram • Value Chain diagram
Requirements Management
TOGAF 9 Artifacts
• Requirements catalog
Phase B, Business Architecture Phase C, Data Phase C, Application Phase D, Technology

• Organization/Actor catalog Architecture Architecture Architecture
• Driver/Goal/Objective catalog • Data Entity/Data • Application Portfolio • Technology
• Role catalog Component catalog catalog Standards catalog
• Business Service/Function • Data Entity/Business • Interface catalog • Technology Portfolio
catalog Function matrix • Application/Organization catalog
• Location catalog • Application/Data matrix • System/Technology
• Process/Event/Control/Product matrix • Role/Application matrix matrix
catalog • Logical Data • Application/Function • Environments and
• Contract/Measure catalog diagram matrix Locations diagram
• Business Interaction matrix • Data Dissemination • Application Interaction • Platform
• Actor/Role matrix diagram matrix Decomposition
• Business Footprint diagram • Data Security • Application diagram
• Business Service/Information diagram Communication diagram • Processing diagram
diagram • Class Hierarchy • Application and User • Networked
• Functional Decomposition diagram Location diagram Computing/Hardware
diagram • Data Migration • Application Use-Case diagram
• Product Lifecycle diagram diagram diagram • Communications
• Goal/Objective/Service diagram • Data Lifecycle • Enterprise Manageability Engineering diagram
• Business Use-Case diagram diagram diagram
• Organization Decomposition • Process/Application
diagram Realization diagram
• Process Flow diagram • Software Engineering
• Event diagram diagram
• Application Migration
diagram
• Software Distribution
diagram
TOGAF 9 Artifacts
Phase E. Opportunities & Solutions
• Project Context diagram
Slide
• 4
Benefits diagram

Edition
Phase C
Preliminary
Phase –
Catalogs,
Matrices and
Diagrams

countries
Slide 5
P Preliminary Phase
Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Principles Catalog
Matrices
Slide 6

Edition
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 7
Phase C
Phase A:
Architecture
Vision –
Catalogs,
Matrices and
Diagrams

countries
Slide 8

Edition
A Architecture Vision
Catalogs Diagrams
• Value Chain Diagram
Matrices
• Stakeholder Map Matrix
• Solution Concept Diagram
Slide 9
Stakeholder Map
Stakeholder Key Concerns Class Catalogs, Matrices and
Diagrams
CxO The high-level drivers, goals and Keep Business Footprint diagram
objectives of the organization, and Satisfied Goal/Objective/Service diagram
how these are translated into an Organization Decomposition
effective process and IT architecture diagram
to advance the business
Program Prioritizing, funding, and aligning Keep Project Context diagram

Management change activity. An understanding of Satisfied Business Footprint diagram
Office project content and technical Application Communication
dependencies adds a further diagram
dimension of richness to portfolio
management and decision making. Functional Decomposition
diagram
HR The roles and Actors that support the Keep Organization Decomposition
functions, applications, and Informed diagram
technology of the organization. HR Organization/Actor catalog
are important stakeholders in Location catalog
ensuring that the correct roles and
actors are represented.
Slide 10

Edition
Value Chain Diagram
Source: Wikipedia.org
Slide 11
Example Value Chain Diagrams
Product
Sales Fulfilment Payments Servicing
& Offer
Slide 12

Edition
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 13
Example Solution Concept Diagrams
Today’s use of channels Tomorrow’s use of channels
High Value Tasks

RM
RM From RM
to ST
SERVICE SERVICE TEAM

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

Edition
Phase C
Phase B:
Business
Architecture –
Catalogs,
Matrices and
Diagrams

countries
Slide 15
B 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 • Use-Case diagram
• Contract/Measure catalog • Organization Decomposition
Matrices diagram
• Business Interaction matrix • Process Flow diagram
• Actor/Role matrix • Event diagram
Slide 16

Edition
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 17
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.
•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 18

Edition
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
•Business Service
•Information System Service (optionally)
•Contract
•Measure
Slide 19
Matrices
• Business Interaction matrix

• Actor/Role matrix
Slide 20

Edition
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 21
Actor/role Matrix
• This matrix 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
Enterprise Infrastructure Architect
Business Unit Application Architect
Infrastructure Solution Architect

Head of Strategy and Architecture
Architecture Configuration Mgr

Business Unit Service Owner
External Vendors / Suppliers

Enterprise Design Authority
Technical Design Authority
Head of Implementation
Infrastructure Strategist
Infrastructure Designer
IT Management Forum
Enterprise Architect
Business Unit Head
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 22

Edition
Diagrams
• Business Footprint diagram

• Business Service/Information diagram
• Functional Decomposition diagram
• Product Lifecycle diagram
• Goal/Objective/Service diagram
• Use-Case diagram
• Organization Decomposition diagram
• Process Flow diagram
• Event diagram
Slide 23
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 24

Edition
Example Business Footprint Diagram
Slide 25
Business 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 26

Edition
Example Business Service/Information

Diagram
Basic example
Slide 27
Example Business Service/Information

Diagram
Complaint
Fault
Complaint Handling
Common Faults Management
Service
Service
Customer Details
Customer
Complaint
Resolution Customer Details
Lead
Management
Service
Extended example showing actors

and service interactions
Slide 28

Edition
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 29
Example Functional Decomposition

Diagram
Slide 30

Edition
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 31
Example Product Lifecycle Diagram
Slide 32

Edition
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 33
Example Goal/Objective/Service
Diagram
Goal:Increase Role:CFO
Revenues
Role: Role:
VP Marketing VP Sales
Objective: Objective:
After Sales Creating new line
Market of cars by end of…
Function:
Sales and
Marketing
Service:
Marketing
Service: Pre-
owned vehicles-
Service:
Campaign
Service:
Sales
Service:
Pre-Sales
Service: Order
To Delivery
Slide 34

Edition
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 35
Example Business Use-case Diagram
Slide 36

Edition
Organization 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 37
Example Organization Decomposition

Diagram
Slide 38

Edition
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 39
Example Process Flow Diagram
Start
Step 1 Step 2 Step 3 Step 4
Step 5 Step 6 Step 6 Step 6 STOP
Slide 40

Edition
Example Process Flow Diagram

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

Spreadsheet
Tool
Process Flow (w/Roles & Applications)
Slide 41
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 42

Edition
Example Events Diagram
Impacts/Generates
Triggers
Event Business
Process result
(e.g. End of Fiscal

Quarter) (e.g. 1Q results reported to
(e.g. Financial Government Agencies)
Reporting Process)
Slide 43
Example Events Matrix
EVENT PROCESS TRIGGERED BUSINESS RESULT(S)
Customer Sales order processing Sales order captured in

submits Create & save sales order order book
sales order Generate acknowledgement
Confirm receipt of customer order
Begin order fulfillment activities
Customer Custom product configuration Custom product

submits Capture requirements from customer configured
request for Define custom specifications Customer contract
custom Price custom configuration signed
product Negotiate with customer
Secure approval from customer regarding
configuration and price
End of quarter Financial reporting process Financial report

generated
Slide 44

Edition
Phase C
Phase C:
Data
Architecture –
Catalogs,
Matrices and
Diagrams

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

Edition
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 47
Matrices
• Data Entity/Business Function matrix

• Application/Data matrix
Slide 48

Edition
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 49
Example Data Entity/Business Function

Matrix
BUSINESS
FUNCTION
(Y-AXIS) / CUSTOMER BUSINESS CUSTOMER PRODUCT
DATA MASTER PARTNER LEADS MASTER
ENTITY (X-
AXIS)
Customer Business partner data Business Lead Processing N/A
Relationship management service partner data Service
Management Owner – Sales & management Owner –
Marketing business unit service Customer
executive Owner of data Relationship
Function can Create, entity (person or Manager
read, update and delete organization) Function can only
customer master data Function can Create, read,
Create, read, update customer
update and leads
delete
Supply Chain Customer Requirement N/A N/A Product data
Management Processing Service management
Owner – Supply Chain service
Manager Owner –
Global
product
development
organization
Slide 50

Edition
Application/Data Matrix
• The purpose of the Application/Data matrix is to depict the

relationship between applications and the data entities that
are accessed and updated by them.
• Applications 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 51
Example Application/Data Matrix
APPLICATION (Y-
DESCRIPTION OR
AXIS) AND DATA (X- DATA ENTITY DATA ENTITY TYPE
COMMENTS
AXIS)
CRM System of record for Customer data Master data

customer master data
Commerce Engine System of record for Sales orders Transactional data

order book
Sales Business Warehouse and data Intersection of multiple Historical data

Warehouse mart that supports North data entities (e.g. All sales
American region orders by customer XYZ
and by month for 2006)
Slide 52

Edition
Diagrams
• Conceptual Data diagram

• Logical Data diagram
• Data Dissemination diagram
• Data Security diagram
• Data Migration diagram
• Data Lifecycle diagram
Slide 53
Conceptual Data 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 54

Edition
Logical Data Diagram

• The purpose is to depict logical views relationships among
the critical data entities (or classes) within the enterprise.
• The audience is
– Application developers
– Database designers
Slide 55
Data Dissemination Diagram
• The purpose of the Data Dissemination diagram is to show

the relationship between
– data entity
– business service
– 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 56

Edition
Example 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 57
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 58

Edition
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 59
Example Data Security Diagram
Class of Roles
(by job function)
Actor Business Process

Function
Single
- Sign
Physical
On or
Access
Access Control
Location Business
Service
Access Control
(levels of
Granularity)
Access Control
(levels of Logical
Granularity) Application
Component
Slide 60

Edition
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 NA (US, CA) Physical
Financial Analyst service EMEA (UK, Access
DE) Control
APJ (tables xyz
only)
Procurement & Procurement WW Direct Supplier portal NA (US Access
Spend Analyst Management and Procurement Service Midwest) control
Control
WW Contracts Not applicable WW Direct Supplier Portal LA Access

System Procurement Service control
(application) (system to
system)
WW Product Geo Brand WW Direct Supplier Portal WW (all Access

Development Managers Procurement Service Geos) Control
(Org Unit)
Slide 61
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 62

Edition
Example Data Migration Diagram

“Baseline” Data migration technology “Target”
application components application
components components
ABM
Source of CRM
Customer records
CCB System of Record

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

MRPA Staging Data Quality Staging
Source of Material
data SRM
VLC (one
per geo) System of Record for
Source of vendor Vendor Master &
data Contracts
Slide 63
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_ContactName CUSTCONTACT
Cust_Tele CUSTTELEPHONE
Slide 64

Edition
Phase C
Phase C:
Application
Architecture –
Catalogs,
Matrices and
Diagrams
Application
Architecture

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

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

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

•Logical Application Component
•Physical Application Component
•Application communicates with application relationship
Slide 67
Matrices
• Application/Organization matrix
• Role/Application matrix
• Application/Function matrix
• Application Interaction matrix
Slide 68

Edition
Application/Organization Matrix

between applications 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 69
Example Application/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 X X X
FINANCIALS
PROCURESOFT X X
Slide 70

Edition
Role/Application Matrix
• The purpose of this matrix is to depict the relationship between

applications 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 71
Example Role/Application 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 X X X X
FINANCIALS
PROCURESOFT X X
Slide 72

Edition
Application/Function Matrix

between applications 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 73
Example Application/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 X X X
FINANCIALS
PROCURESOFT X X
Slide 74

Edition
Diagrams
• Application Communication diagram

• N2 model or Node Connectivity diagram
• Application and User Location diagram
• System Use-Case diagram
• Enterprise Manageability diagram
• Process/Application Realization diagram
• Software Engineering diagram
• Application Migration diagram
• Software Distribution diagram
Slide 75
Application Communication Diagram
• The purpose of this 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 76

Edition
Application Communication Diagram
Slide 77
N2 Model
1c
ABC
1a
1b
ABM 2a
3c
CCD 3a
4a
3b
CRM
1d
4b
IPC
3d
Slide 78

Edition
Information Exchange Matrix

EVENT
LABEL SOURCE DESTINATION DATA ENTITY
TRIGGERED
1a ABC ABM Sales order New sales
(create order from
request) front end
1b ABM ABC Sales order Order

(confirm created in the
create) backend
ERP system
2a ABM CCD Product Subscribe/
catalog Publish timer
Slide 79
Application & 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 80

Edition
Example Application & User Location

Diagram (part 1)
INTERNAL,
USER
CUSTOMER LOCATION
APPLICATION USER TYPE BUSINESS
OR ADDRESS ORG UNIT (USER
LOCATION BELONGS TO)
PARTNER
CRM Developer Internal NA Western Chicago Sears NA Sales &
Super User Region tower office Marketing
Administrator Chicago
EMEA EMEA Sales
Headquarter Downtown
s, office
UK Middlesex,
London
SAP R/3 Test Engineers Internal Beijing Manufacturing &
Mechanical Manufacturin logistics
Engineers g
Procurement Plant
managers
Slide 81
Example Application & User Location

Diagram (part 2)
Slide 82

Edition
Application Use Case Diagram
Source: wikipedia.org
Slide 83
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 84

Edition
Example Enterprise Manageability

Diagram
Slide 85
Process/Application Realization Diagram
• The purpose of this diagram is to 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 86

Edition
Example Process/Application
Realization Diagram
Slide 87
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 88

Edition
Example Software Engineering Diagram
Slide 89
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 90

Edition
Example Application/Migration Diagram
Slide 91
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 92

Edition
Phase C
Phase D:
Technology
Architecture –
Catalogs,
Matrices and
Diagrams

countries
Slide 93
D Catalogs, Matrices and Diagrams
Catalogs Diagrams
• Technology Standards catalog • Environments and Locations
• Technology Portfolio catalog diagram
• Platform Decomposition diagram
• Processing diagram
• Networked Computing/Hardware
• Matrices diagram
• Application/Technology matrix • Communications Engineering
diagram
Slide 94

Edition
Catalogs
• Technology Standards catalog

• Technology Portfolio catalog
Slide 95
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 can be implemented as an extension to the Technology Portfolio Catalog
and thus will share the same metamodel entities:
•Platform Service, Logical Technology Component, Physical Technology
Component
Technology This catalog identifies and list all the technology in use across the
enterprise, including hardware, infrastructure software, and application
Portfolio
software. An agreed technology portfolio supports lifecycle management of
Catalog technology products and versions and also forms the basis for definition of
technology standards
•Platform Service, Logical Technology Component, Physical Technology
Component
Slide 96

Edition
Matrices
• Application/Technology matrix
Slide 97
Application/Technology Matrix
• The Application/Technology matrix documents the mapping

of applications to the technology platform.
• The Application/Technology matrix shows:
– Logical/Physical Application Components
– Services, Logical Technology Components, and Physical
Technology Components
– Physical Technology Component realizes Physical Application
Component relationships
Slide 98

Edition
Example Application/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
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 99
Example Application/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 components of
Clustered – No Processor Type - the SW product)
No. of Nodes – N/A RISC Power p5 AIX 10.2.1
Server logical Number of License Type -
address - Processors - 8 way Enterprise wide
[email protected] Memory - 1GB license
Maintenance Window Hard drive - 40 GB License expiry
– Sun 0100 to 0300 IP - 11.xx.xx.xx date - 12/31/2014
Slide 100

Edition
Example 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 101
Diagrams
• Environments and Locations diagram

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

Edition
Environments 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 103
Example Environments and Locations

Diagram
Slide 104

Edition
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 105
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 106

Edition
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 107
Example Processing Diagram

Open DMZ Internet Zone Intranet Zone
Internet
File Explorer, HTML, Images

(DFS Distributed File System
Server)
Order capture
(DB server)
HTML Code (Web Order Entry &

Load server cluster with Shopping
Balancer 2 nodes) Cart
Code (Application Server
cluster with 2 nodes) App
Messaging Server DB
Server
Over LAN
HTTP
Firewall Firewall Firewall
Slide 108

Edition
Network 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 109
Example Network Computing Hardware

Diagram DMZ 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 Production) Staging)
cluster
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 DB
Web server Server (Order Server
and
cluster-node Engine)
Dispatcher
2
(eCommerce)
App Server
Firewall Firewall Firewall
Slide 110

Edition
Communications 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 111
Communications Engineering Diagram

Prop col
OBM tary
(Enc
Proto ed)
rie
rypt
Au l
th co
Pr oto
oto Pr
co th
l Au
Slide 112

Edition
Phase C
Phase E:
Opportunities
& Solutions –
Catalogs,
Matrices and
Diagrams

countries
Slide 113
E Opportunities & Solutions

Catalogs Diagrams
Matrices • Project Context diagram
• Benefits diagram
Slide 114

Edition
Project Context Diagram
Slide 115
Project Context Diagram
Slide 116

Edition
Benefits Diagram
Slide 117
Phase C
Requirements
Management –
Catalogs,
Matrices and
Diagrams

countries
Slide 118

Edition
R Requirements Management
Catalogs Diagrams
• Requirements Catalog
Matrices
Slide 119
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 120

Edition
Resources
• A set of downloadable templates is available

– http://www.opengroup.org/bookstore/catalog/i093.htm
Slide 121
Sample
Catalogs,
Matrices and
Diagrams

countries
Slide 122

TOGAF V91 Sample Catalogs Matrics Diagrams v3

Uploaded by

Copyright:

Available Formats

TOGAF V91 Sample Catalogs Matrics Diagrams v3

Uploaded by

Document Information

Original Title

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 V91 Sample Catalogs Matrics Diagrams v3

Uploaded by

Copyright:

Available Formats

What are catalogs, matrices and diagrams in TOGAF?

What are catalogs, matrices and diagrams in TOGAF?

What are some examples of catalogs, matrices and diagrams mentioned in the document?

What are some examples of catalogs, matrices and diagrams mentioned in the document?

Personal PDF Edition.

For non-commercial use only

V9.1 Edition Copyright © 2009-2011

The Open Group gratefully acknowledges the contributions

© 2009-2011 The Open Group, All Rights Reserved

TOGAF is a registered trademark of The

Copyright © 2009-2011, The Open Group 1

The objectives of this presentation are to illustrate:

© 2009-2011 The Open Group, All Rights Reserved

Preliminary Phase Phase A, Architecture Vision

Phase B, Business Architecture Phase C, Data Phase C, Application Phase D, Technology

Copyright © 2009-2011, The Open Group 2

TOGAF is a registered trademark of The

© 2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group 3

The Principles catalog contains the following metamodel entities:

© 2009-2011 The Open Group, All Rights Reserved

TOGAF is a registered trademark of The

Copyright © 2009-2011, The Open Group 4

© 2009-2011 The Open Group, All Rights Reserved

Program Prioritizing, funding, and aligning Keep Project Context diagram

Copyright © 2009-2011, The Open Group 5

Value Chain Diagram

© 2009-2011 The Open Group, All Rights Reserved

Example Value Chain Diagrams

Copyright © 2009-2011, The Open Group 6

Example Solution Concept Diagram

• A high-level representation of the solution envisaged

© 2009-2011 The Open Group, All Rights Reserved

Example Solution Concept Diagrams

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

High Value Tasks

SERVICE SERVICE TEAM

CALL CENTER From Call From Service From RM

SELF SERVICE SELF SERVICE INTERNET PORTAL

Low Value Tasks

Copyright © 2009-2011, The Open Group 7

TOGAF is a registered trademark of The

© 2009-2011 The Open Group, All Rights Reserved

B Catalogs, Matrices and Diagrams

Copyright © 2009-2011, The Open Group 8

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

© 2009-2011 The Open Group, All Rights Reserved

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

Copyright © 2009-2011, The Open Group 9

© 2009-2011 The Open Group, All Rights Reserved

• Business Interaction matrix

Copyright © 2009-2011, The Open Group 10

Business Interaction Matrix

• The purpose of this matrix is to depict the relationship

© 2009-2011 The Open Group, All Rights Reserved

Infrastructure Solution Architect

Architecture Configuration Mgr

External Vendors / Suppliers

Technical Design Authority

Customer Sales order processing Sales order captured in

Customer Custom product configuration Custom product

End of quarter Financial reporting process Financial report