1. No category

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
•
Principles
catalog
Phase A, Architecture
Vision
•
•
•
Stakeholder Map
matrix
Value Chain
diagram
Solution Concept
diagram
Phase B, Business Architecture
•
Organization/Actor catalog
•
Driver/Goal/Objective catalog
•
Role catalog
•
Business Service/Function catalog
•
Location catalog
•
Process/Event/Control/Product
catalog
•
Contract/Measure catalog
•
Business Interaction matrix
•
Actor/Role matrix
•
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
Phase D, Technology Architecture
•
Technology Standards catalog
•
Technology Portfolio catalog
•
System/Technology matrix
•
Environments and Locations diagram
•
Platform Decomposition diagram
•
Processing diagram
•
Networked Computing/Hardware diagram
•
Communications Engineering diagram
Phase C, Data Architecture
•
•
•
•
•
•
•
•
•
Data Entity/Data
Component catalog
Data Entity/Business
Function matrix
System/Data matrix
Class diagram
Data Dissemination
diagram
Data Security diagram
Class Hierarchy
diagram
Data Migration diagram
Data Lifecycle diagram
Phase C, Application Architecture
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Phase E. Opportunities &
Solutions
•
Project Context
diagram
•
Benefits diagram
Application Portfolio catalog
Interface catalog
System/Organization matrix
Role/System matrix
System/Function matrix
Application Interaction matrix
Application Communication
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
Requirements Management
•
Requirements catalog
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
• Principles Catalog
Diagrams
Matrices
Slide 5 ©2009-2011 The Open Group, All Rights Reserved
© 2009-2011 The Open Group, All Rights Reserved
P
Catalogs
Catalog
Principles
Catalog
Purpose
The Principles catalog captures principles of the business and architecture
principles that describe what a "good" solution or architecture should look
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
Matrices
• Stakeholder Map Matrix
Diagrams
• Value Chain Diagram
• Solution Concept Diagram
Slide 7 ©2009-2011 The Open Group, All Rights Reserved
© 2009-2011 The Open Group, All Rights Reserved
A
Stakeholder
Example Stakeholder Map
Matrix
Involvement
Class
Relevant Artifacts
CxO
This stakeholder group is interested in the
high-level drivers, goals and objectives of
the organization, and how these are
translated into an effective process and IT
architecture to advance the business
Keep
Satisfied
Business Footprint
Goal/Objective/Service
Model
Organization Chart
Program
Management
Office
This stakeholder group is interested in
prioritizing, funding, and aligning change
activity. An understanding of project content
and technical dependencies adds a further
dimension of richness to portfolio
management and decision making.
Keep
Satisfied
Roadmaps
Business Footprint
Application
Communication
Functional
Decomposition
HR
Key features of the enterprise architecture
are roles and Actors that support the
functions, applications, and technology of
the organization. HR are important
stakeholders in ensuring that the correct
roles and actors are represented.
Keep
Informed
Organization Chart
Organization/Actor/
Location
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
& Offer
Sales
Fulfilment
Payments
Servicing
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
Customers
Interest,
consideration,
join, re-new
Certification
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
SERVICE
TEAM
From RM
to ST
SERVICE TEAM
From Service
Team to CC
From RM
to CC
CALL CENTER
CALL CENTER
SELF SERVICE
INTERNET PORTAL
From Call
Centre to
Online
From Service
Team to
Online
From RM
to Online
SELF SERVICE 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
• Organization/Actor catalog
• Driver/Goal/Objective catalog
• Role catalog
• Business Service/Function
catalog
• Location catalog
• Process/Event/Control/Product
catalog
• Contract/Measure catalog
Matrices
• Business Interaction matrix
• Actor/Role matrix
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 15 ©2009-2011 The Open Group, All Rights Reserved
© 2009-2011 The Open Group, All Rights Reserved
B
Catalogs
Catalog
Organization/
Actor
Catalog
Purpose
A definitive listing of all participants that interact with IT, including users and owners
of IT systems.
It contains the following metamodel entities:
•Organization Unit, Actor Location (may be included in this catalog if an independent
Location catalog is not maintained)
Driver/Goal/
Objective
Catalog
A cross-organizational reference of how an organization meets its drivers in practical
terms through goals, objectives, and (optionally) measures.
It contains the following metamodel entities:
•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
Service /
Function
Catalog
A functional decomposition in a form that can be filtered, reported on, and queried, as
a supplement to graphical Functional Decomposition diagrams.
It contains the following metamodel entities:
Location
Catalog
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
equipment.
It contains the following metamodel entities:
•Location
Process/
Event/
Control/
Product
Catalog
The Process/Event/Control/Product catalog provides a hierarchy of processes, events
that trigger processes, outputs from processes, and controls applied to the execution
of processes. This catalog provides a supplement to any Process Flow diagrams that
are created and allows an enterprise to filter, report, and query across organizations
and processes to identify scope, commonality, or impact.
It contains the following metamodel entities:
•Organization Unit,Business Function, Business Service, Information System Service
(may optionally be included here)
•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
Contract/
Measure
Catalog
Purpose
A listing of all agreed service contracts and (optionally) the measures
attached to those contracts. It forms the master list of service levels
agreed to across the enterprise.
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
supply of
materials
Manufacturing
Sales and Distribution
Contract for
supply of
product
specification
Customer Service
Contract for supply of
sales forecasts
Contract for
supply of product
Contract for fulfillment of
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.
R
R
R
R
R
I
I
I
I
R
C
C
C
C
R
I
I
I
I
I
I
I
I
C
C
C
C
C
C
C
C
C
R
R
C
C
C
C
I
A
External Vendors / Suppliers
Head of Implementation
I
I
I
I
I
A
A
A
A
C
I
I
C
C
C
C
C
C
Project Manager
Enterprise Infrastructure Architect
I
I
I
I
I
R
C
I
I
I
IT Operations
Infrastructure Solution Architect
I
C
I
R
C
C
C
I
I
C
Infrastructure Designer
Infrastructure Strategist
I
I
R
R
R
R
R
C
R
I
A
C
I
Architecture Configuration Manager
Head of Strategy and Architecture
I
I
Business Unit Service Owner
I
I
R
I
I
Business Unit Head
C
R
I
I
I
IT Management Forum
C
C
I
R
A
I
I
I
I
C
C
Infrastructure
Implementation
Actors
C
I
A
A
I
R
C
I
C
C
Strategy and Architecture
Actors
Business Unit Application Architect
Business Unit
Actors
Technical Design Authority
I
Steering Group
Actors
Enterprise Design Authority
I
I
I
Enterprise Architect
R = Responsible for carrying out the role
A = Accountable for actors carrying out the role
C = Consulted in carrying out the role
I = Informed in carrying out the role
Strategy Lifecycle Roles
Architecture Refresh
Architecture Roadmap
Benefits Assessment
Change Management
Framework Refresh
Project Lifecycle Roles
Solution Architecture Vision
Logical Solution Architecture
Physical Solution Architecture
Design Governance
Architecture Configuration Management
CIO
Office of
CIO Actors
C
C
I
R
R
R
C
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
Order
C1
C2
Receive
Order
C3
Process
Order
Distribute
Goods / Services
C4
Support Services
Store Operations
C5 Manage
Invoice
Customer
Cash
Business Process
Integration Layer
C0 Orderto-Cash
Business Footprint Diagram
Accounts
Receivable
Supply Chain Mgmt
Functional
Services Layer
User Management
Layer
Buyer
Portal
Employee
Portal
Exchanges
Supplier
Portal
Customer
Portal
Partner
Portal
Others
Slide 25 ©2009-2011 The Open Group, All Rights Reserved
© 2009-2011 The Open Group, All Rights Reserved
B
Business Footprint Diagram
SC2 –
Plan sales &
operations
SC1 – Plan &
manage the demand
SC11 - Monthly
Forecast Generation
SC3 –
Establish inventory
plan
SC4 –
Define
manufacturing
plan
SC51 – Logistics Capacity
Planning
SC22 – Cross-UOT Demand & Supply Balancing
and LP S&OP validation
SC12 - Monthly
Forecast Collaboration
SC21 – UOT and LPS Tactical Supply Planning
SC17 – Forecast
Weekly Update
SC32 – Inventory
Management Rules
Parameter Definition
SC16 – Demand
explosion for assembly
SC42 – Multi-Plant
Planning
SC52 – Distribution
Supply Planning – midTerm
SC53 – Distribution
Supply Planning – shortTerm
SC54 - Distribution
shortage management
SC41 – Plant
Production Planning
SC13 – Planned
demand consumption
by customer order
SC5 - Plan goods
movements and
resources in the
distribution network
SC61 – Warehouse
Management
SC62 – Long Distance
Transportation
SC63– Short-Distance
Transportation
GFB57- Process steps
traceability
SC55 – Deployment
SC56 – Intra-group
exchanges management
SC14 – Allocation
Definition Rules for
ATP (monthly)
SC15 – Allocation
Definition Rules for
ATP (daily)
SC6 –
Schedule & execute
goods movements,
storage and
transportation
decisions
SC57 – Procurement
exchanges management
SC65 – Transportation
administration
GFB58 – Product
Traceability
SC70 - Inventory Management (physical and planned inventory including internal transfer orders)
SC04 - Inventory
Norms Definition
SC0 - Referential
GFB64 - Supply Chain Costs & Margin Referential
GFB61 – Supply Chain Referential – Logistics
Resource
GFB62 – Supply Chain Referential – Production Process Model
GFB63 – Demand
Planning Referential
GFB65 - Supply Chain Referential – Production & Distribution & Ship to Customer Network
GFB59 – Product & Services – Client Catalog
GFB50 – Product & Services Referential
GFB51 - Client Referential
SC9
- BI
SC91 – Demand BI /
Reporting
SC92 – Tactical Planning
BI / Reporting
SC93 – Inventory BI /
Reporting
SC94 – Plant Planning BI
/ Reporting
SC95 – Distribution
Planning BI / Reporting
SC96 – Logistics BI /
Reporting
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
Primary
Support
Human
Admin
Finance
Resources
Business
Planning
Marketing
&
Sales
Manage Public
Develop & Track
Plan Human
Formulate
Develop New
Relations
Financial Plan
Resources
Strategy
Business
Provide Legal
Appropriate
Services
Funds
Acquire
Human
Resources
Develop and
Maintain
Business Plan
Establish
Customer
Requirements
Perform
Audit
& Controls
Develop &
Manage
Product Cost
Manage
Manage
Transportation
Payables
Maintain
Manage
Facilities
Receivables
Provide
Administrative
Services
Manage Assets
Develop
Obtain Sales
Employees
Commitments
Provide
Employee
Services
Provide
Customer
Support
Manage Union
Activities
Terminate Active
Employment
Engineering
Research and
Develop
Technology
Inventory
Plan Material
Requirements
Engineer and
Design Products
Procure
Equipment
Material & Tools
Engineer and
Design
Processes
Suppliers
Manage
Manufacturing
Plan
Manufacturing
Requirements
Engineer
Packages
Perform Quality
Ship
Engineering
Products
Convert
Resources
to Product
Design Tools
Manage
Control
and Equipment
Inventory
Production
Manage
Engineering
Changes
Distribution
Maintain Plant
Equipment &
Tools
Manage
Warranty
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
obj-"aftersales"
market
rol-VP Sales
obj-creating
new line of cars
by the end of...
Functionsales 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
Slide 40 ©2009-2011 The Open Group, All Rights Reserved
Copyright © 2009-2011, The Open Group
c a p - O r d e rt o - D e l iv e r y
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-Worldwide Public
Affairs and Policy
org-Chief Medical Officer
rol-Field Based Govt.
Relations
org-Global
Research &
Development
rol-Wolrdwide Pharmaceutical
Operations
rol-Vice Chairman
rol-Global Manufacturing
rol-Wolrdwide Medical
org-Wolrdwide talent
Development and HR
org-General Counsel
loc-US
rol-Wolrdwide
Research
rol-Talent
Development
rol-Intellectual Property
rol-HealthWelness
rol-Employment Law
rol-CFO
rol-Wolrdwide
Communications
rol-Philanthropy/Stakeholder
Advocacy
rol-Safety Risk
Management
rol-Worldwide
Development
rol-Science Advocacy
rol-Worldwide
Research Affairs
rol-Worldwide Policy
rol-Financ ial Strategy
rol-Federal Government
relations
loc-Japan/ASIA
rol-Worlwide Strategic Planning
rol-Planning
rol-Line Support
rol-Diversity and
Inclusion
rol-Litigation/Regulatory
rol-compensation and
Benefits
rol-Business Transactions
rol-Animal Health
loc-Europe
rol-Worldwide Licensing and
Business Develoment
rol-Wolrdwide Technology
loc-Middle East
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
Start
Example Process Flow
Diagram
Step 2
Step 1
Step 5
Step 3
Step 6
Step 4
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
Diagram
Technical Support
Team
Start
Sales Rep
Pricer
Step 2
Step 1
Custom app
Email
Custom Bid
Approver
CRM
Customer Rep
Step 5
Step 6
email
IWF
Step 3
Customer Rep
Step 6
Consolidation
Tool
Pricer
Step 4
MS Word
MS Excel
Customer Rep
Step 6
STOP
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
Impacts/Generates
Triggers
Event
Business
result
Process
(e.g. End of Fiscal Quarter)
(e.g. 1Q results reported to
Government Agencies)
(e.g. Financial Reporting
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
Sales order processing
ƒ Create & save sales order
ƒ Generate acknowledgement
ƒ Confirm receipt of customer order
ƒ Begin order fulfilment activities
ƒ
Sales order captured in
order book
Customer submits
request for
custom
product
Custom product configuration
ƒ Capture requirements from customer
ƒ Define custom specifications
ƒ Price custom configuration
ƒ Negotiate with customer
ƒ Secure approval from customer regarding
configuration and price
ƒ
ƒ
Custom product
configured
Customer contract signed
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
• Data Entity/Data
Component catalog
Diagrams
• Class diagram
• Data Dissemination
diagram
• Data Security diagram
• Class Hierarchy diagram
• Data Migration diagram
• Data Lifecycle diagram
Matrices
• Data Entity/Business
Function matrix
• System/Data matrix
Slide 51 ©2009-2011 The Open Group, All Rights Reserved
© 2009-2011 The Open Group, All Rights Reserved
C
Catalogs
Catalog
•Data
Entity/Data
Component
Catalog
Purpose
To identify and maintain a list of all the data use across the
enterprise, including data entities and also the data components
where data entities are stored.
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
(Y-AXIS) AND
DATA
ENTITY (X-AXIS)
Customer Relationship
Management
CUSTOMER
MASTER
ƒ
ƒ
ƒ
Supply Chain
Management
ƒ
ƒ
BUSINESS
PARTNER
Business partner data
management service
Owner – Sales &
Marketing business
unit executive
Function can Create,
read, update and
delete customer
master data
ƒ
Customer
Requirement
Processing Service
Owner – Supply
Chain Manager
ƒ
ƒ
ƒ
CUSTOMER
LEADS
Business partner data
management service
Owner of data entity
(person or organization)
Function can Create,
read, update and delete
ƒ
N/A
ƒ
ƒ
ƒ
PRODUCT
MASTER
Lead Processing
Service
Owner – Customer
Relationship Manager
Function can only
Create, read, update
customer leads
ƒ
N/A
N/A
ƒ
Product data
management service
Owner – Global
product development
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 (YAXIS) AND DATA
(X-AXIS)
DESCRIPTION OR
COMMENTS
DATA ENTITY
DATA ENTITY TYPE
CRM
ƒSystem of record for
customer master data
ƒCustomer data
ƒMaster data
Commerce Engine
ƒSystem of record for order
book
ƒSales orders
ƒTransactional data
Sales Business
Warehouse
ƒWarehouse and data mart
that supports North American
region
ƒIntersection of multiple data
entities (e.g. All sales orders
by customer XYZ and by
month for 2006)
ƒHistorical data
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
Account
P.A12
Actor
Customer
Profile
I.C2
Trigger
Contact
Process
P.CS13
Payment
P.CS5
Service
Request
T.P8
Agent
A.A4
Enquiry
T.C1
Customer
A.C2
Customer
Information
I.C1
Slide 59 ©2009-2011 The Open Group, All Rights Reserved
Appeal
T.C19
Complaint
T.C16
© 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
Dispatched
Closed
Archived
Deleted
Closed
Archived
Deleted
Customer Order
New
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
Function
Process
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
ACTOR
CLASS OF
ROLES (JOB
FUNCTION)
FUNCTION
BUSINESS
SERVICE
TYPE OF
ACCESS
LOCATION
Financial Analyst
SOA Portfolio
Financial Analyst
Financial Analysis
SOA portfolio service
ƒ
ƒ
ƒ
NA (US, CA)
EMEA (UK, DE)
APJ
ƒ
ƒ
Physical
Access Control
(tables xyz only)
Procurement &
Spend Analyst
Procurement
Management and
Control
WW Direct
Procurement
Supplier portal
Service
ƒ
NA (US
Midwest)
ƒ
Access control
WW Contracts
System (application)
Not applicable
WW Direct
Procurement
Supplier Portal
Service
ƒ
LA
ƒ
Access control
(system to
system)
WW Product
Development (Org
Unit)
Geo Brand Managers
WW Direct
Procurement
Supplier Portal
Service
ƒ
WW (all Geos)
ƒ
Access Control
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”
application
components
Data migration technology
components
“Target”
application
components
ABM
CRM
Source of
Customer records
System of Record
for Customer Master
CCB
ERP
BDW
Source of order
history
MRPA
Source of Material
data
System of Record for
Material Master & Order
history
Source
Staging
Transformation &
Data Quality
VLC (one
per geo)
Source of vendor
data
Target
Staging
SRM
System of Record for
Vendor Master &
Contracts
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
APPLICATION
COMPONENT
ABM
SOURCE DATA ELEMENT
Cust_Name
TARGET LOGICAL
APPLICATION
COMPONENT
CRM
TARGET DATA ELEMENT
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
Authorised User
Vehicle Tester
Vehicle Tester
Keeper
Keeper
Individual
Individual
Customer
Customer
Driver
Driver
Organisation
Organisation
Purchaser/Nominee
Purchaser/Nominee
Trainer/Booker
Trainer/Booker
Manufacturer
Manufacturer
Driving
DrivingInstructor
Instructor
Operator
Operator
Taxi Driver
Taxi Driver
Dealing
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
• Application Portfolio catalog
• Interface catalog
Matrices
• System/Organization matrix
• Role/System matrix
• System/Function matrix
• Application Interaction matrix
Diagrams
• Application Communication
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 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
Application
Portfolio Catalog
Purpose
To identify and maintain a list of all the applications in the enterprise. This list helps to
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)
AND
ORGANISATION
UNIT (X-AXIS)
CUSTOMER
SERVICES
PROCUREMENT AND
WAREHOUSING
HR
X
SAP HR
X
X
SIEBEL
X
X
SAP FINANCIALS
X
X
PROCURESOFT
X
X
CORPORATE
FINANCE
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 (YAXIS) AND
FUNCTION (XAXIS)
CALL CENTRE
OPERATOR
CALL CENTRE
MANAGER
FINANCE ANALYST
CHIEF
ACCOUNTANT
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
APPLICATION (YAXIS) AND
FUNCTION (XAXIS)
Example System/Function
Matrix
CALL CENTRE 1ST
LINE
WAREHOUSE
CONTROL
VACANCY FILLING
GENERAL LEDGER
MAINTENANCE
SAP HR
X
X
X
X
SIEBEL
X
X
SAP FINANCIALS
X
X
PROCURESOFT
X
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
3d
IPC
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
LABEL
SOURCE
DESTINATION
EVENT
TRIGGERED
DATA ENTITY
1a
ƒ
ABC
ƒ
ABM
ƒ
Sales order
(create
request)
ƒ
New sales
order from front
end
1b
ƒ
ABM
ƒ
ABC
ƒ
Sales order
(confirm create)
ƒ
Order created
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)
APPLICATION
CRM
USER TYPE
Developer
Super User
Administrator
INTERNAL,
CUSTOMER
OR
PARTNER
Internal
USER
BUSINESS
LOCATION
NA Western
Region
EMEA
Headquarters,
UK
SAP R/3
Test Engineers
Mechanical
Engineers
Procurement
managers
Internal
LOCATION
ADDRESS
Chicago Sears
tower office
Chicago
Downtown office
Middlesex, London
Beijing
Manufacturing
Plant
ORG UNIT (USER
BELONGS TO)
NA Sales &
Marketing
EMEA Sales
Manufacturing &
logistics
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
• Technology Standards catalog
• Technology Portfolio catalog
•
•
Matrices
System/Technology matrix
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
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
Technology
Standards
Catalog
Purpose
This documents the agreed standards for technology across the enterprise
covering technologies, and versions, the technology lifecycles, and the
refresh cycles for the technology.
It contains the following metamodel entities:
•Platform Service, Logical Technology Component, Physical Technology
Component
Technology
Portfolio
Catalog
The purpose of this catalog is to identify and maintain a list of all the
technology in use across the enterprise, including hardware, infrastructure
software, and application software. An agreed technology portfolio
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
APPLICATION
COMPONENT
ABM
Load balancer and
Dispatcher
PHYSICAL
TECHNOLOGY
COMPONENT
SERVER ADDRESS
IP ADDRESS
Web server - node 1
F01ws001@host.com
10.xx.xx.xx
Web server - node 2
F01ws002@host.com
10.xx.xx.xx
Web server - node 3
F01ws003@host.com
10.xx.xx.xx
App server – node 1
F02as001@host.com
10.xx.xx.xx
App server – node 2
F02as002@host.com
10.xx.xx.xx
App server – node 3
F02as003@host.com
10.xx.xx.xx
Database server
(production)
F02dbp001@host.com
10.xx.xx.xx
Database server (stating)
F03dbs001@host.com
10.xx.xx.xx
Dispatcher server
F03nd001@host.com
242.xx.xx.xx
Slide ©2009-2011 The Open Group, All Rights Reserved
115
© 2009-2011 The Open Group, All Rights Reserved
DExample System/Technology Matrix
TECH
FUNCTION
HARDWARE
LOGICAL
Load balancing
ƒName – Balancer
ƒVendor - IBM
ƒServer Type –
eServer
ƒClustered – No
ƒNo. of Nodes – N/A
ƒServer logical
address d04lb01@host.com
ƒMaintenance Window
– Sun 0100 to 0300
HARDWARE
PHYSICAL
ƒModel/Type – IBM
P7xx
ƒSerial Number –
1S4568
ƒProcessor Type RISC Power p5
ƒNumber of
Processors - 4 way
ƒMemory - 8GB
ƒHard drive - 4 TB
ƒIP - 11.xx.xx.xx
SOFTWARE
LOGICAL
SOFTWARE
PHYSICAL
ƒProduct- IBM Load
balance manager
ƒVendor - IBM
ƒOS – UNIX based
ƒSW Components
– LB v3.2 (list all
the other
components of the
SW product)
ƒAIX 10.2.1
ƒLicense Type ƒEnterprise wide
license
ƒLicense expiry
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
installation and execution code)
ƒLoad balancing server
(d03lb001@host.com)
ƒCommerce pages
ƒHTML code
ƒApplets
ƒJSP
ƒWeb Server cluster
(d03ws001@host.com,
d03ws002@host.com,
d03ws003@host.com)
ƒCommerce Engine
•Order Entry (both installation and
execution code)
•Shopping Cart (both installation
and execution code)
•Application Server
(d03as001@host.com,
d03as002@host.com)
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
)
locLudwigsburg
appCAD/CAE
app-Project
managment
system
app-R&D
system of
systems
loc-Italia
loc-Japan
locLudwigsburg
tec-Windows
XP
tec-Windows
Vista
locStuttgart
tec-RDB
tec-OCR
loc-USA
locLudwigsburg
loc-Italia
appBuild-toOrder
(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
Components
Physical Technology
Components
Tech Function
Tech Function
Web Server
Layer
Web server layer
Application Layer
Application Layer
Database Layer
Database Layer
Attributes
•
•
•
•
•
•
•
•
Name
Model/Type
Clusters
Number of Components
Vendor
Server Type (mainframe, Mid range, RISC,
Intel)
Server logical name
IP Address etc
Logical Technology
Components
Physical Technology
Components
Tech Function
Tech Function
Web Server Layer
Web Server Layer
Application Layer
Application Layer
Database Layer
Database Layer
Attributes
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Product Name
Vendor
OS
SW components
License Type
License Expiry 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
Diagram
DMZ
Internet Zone
Web
server
Web
cluster
server
cluster
Load
Balancer
and
Dispatcher
Web
server
clusternode 3
(ABM)
Web server
cluster
Web server
cluster-node
2
(eCommerce
)
Load
Balancer
and
Dispatcher
Application
Server cluster
Application
(node 3)
Server cluster
(node
3)
App Server
cluster - node 3
(ABM)
Intranet Zone
Database
(ABM
Staging)
Database
(ABM
Production)
DFS Distributed File
System (html,
images)
Application
Server (Order
Engine)
Database
App
Server
DB
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
G
OBM tary
rie
Prop col
Proto ed)
rypt
(Enc
Au
th
Pr
oto
co
l
th
Au
l
co
oto
Pr
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
Matrices
Diagrams
• 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
• Requirements Catalog
Diagrams
Matrices
Slide ©2009-2011 The Open Group, All Rights Reserved
139
© 2009-2011 The Open Group, All Rights Reserved
R
Catalogs
Catalog
Requirements
Catalog
Purpose
The Requirements catalog captures things that the enterprise needs to do
to meet its objectives. Requirements generated from architecture
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