TOGAF-V9-Sample-Catalogs-Matrics-Diagrams-v2
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
<strong>Sample</strong> <strong>Catalogs</strong>,<br />
Matrices<br />
and <strong>Diagrams</strong><br />
<strong>v2</strong>.02: 7 April 2011<br />
Download the bundle from<br />
http://www.opengroup.org/bookstore/catalog/i093.htm<br />
<strong>V9</strong> Edition Copyright © 2009-2011<br />
Slide 1 ©2009-2011 The Open Group, All Rights Reserved<br />
All rights reserved<br />
Published by The Open Group, 2011<br />
The Open Group gratefully acknowledges the contributions<br />
from SAP and Capgemini<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
<strong>Sample</strong><br />
<strong>Catalogs</strong>,<br />
Matrices and<br />
<strong>Diagrams</strong><br />
Slide 2 ©2009-2011 The Open Group, All Rights Reserved<br />
<strong>TOGAF</strong> is a registered trademark of The<br />
Open Group in the United States and other<br />
countries<br />
Copyright © 2009-2011, The Open Group 1
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
Objectives<br />
The objectives of this presentation are to illustrate:<br />
• <strong>TOGAF</strong> 9 <strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
• What they consist of<br />
• Examples<br />
• How they can be used<br />
The examples shown are illustrative.<br />
The exact format of the catalogs,<br />
matrices and diagrams will depend<br />
on the tools used and adaptations to<br />
<strong>TOGAF</strong> for the specific EA.<br />
Slide 3 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
Preliminary Phase<br />
• Principles<br />
catalog<br />
<strong>TOGAF</strong> 9<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
Phase A, Architecture<br />
Vision<br />
• Stakeholder Map<br />
matrix<br />
• Value Chain<br />
diagram<br />
• Solution Concept<br />
diagram<br />
Phase B, Business Architecture<br />
• Organization/Actor catalog<br />
• Driver/Goal/Objective catalog<br />
• Role catalog<br />
• Business Service/Function catalog<br />
• Location catalog<br />
• Process/Event/Control/Product<br />
catalog<br />
• Contract/Measure catalog<br />
• Business Interaction matrix<br />
• Actor/Role matrix<br />
• Business Footprint diagram<br />
• Business Service/Information diagram<br />
• Functional Decomposition diagram<br />
• Product Lifecycle diagram<br />
• Goal/Objective/Service diagram<br />
• Business Use-Case diagram<br />
• Organization Decomposition diagram<br />
• Process Flow diagram<br />
• Event diagram<br />
Phase C, Data Architecture<br />
• Data Entity/Data<br />
Component catalog<br />
• Data Entity/Business<br />
Function matrix<br />
• System/Data matrix<br />
• Class diagram<br />
• Data Dissemination<br />
diagram<br />
• Data Security diagram<br />
• Class Hierarchy<br />
diagram<br />
• Data Migration diagram<br />
• Data Lifecycle diagram<br />
Phase C, Application Architecture<br />
• Application Portfolio catalog<br />
• Interface catalog<br />
• System/Organization matrix<br />
• Role/System matrix<br />
• System/Function matrix<br />
• Application Interaction matrix<br />
• Application Communication<br />
diagram<br />
• Application and User Location<br />
diagram<br />
• System Use-Case diagram<br />
• Enterprise Manageability<br />
diagram<br />
• Process/System Realization<br />
diagram<br />
• Software Engineering diagram<br />
• Application Migration diagram<br />
• Software Distribution diagram<br />
Phase D, Technology Architecture<br />
• Technology Standards catalog<br />
• Technology Portfolio catalog<br />
• System/Technology matrix<br />
• Environments and Locations diagram<br />
• Platform Decomposition diagram<br />
• Processing diagram<br />
• Networked Computing/Hardware diagram<br />
• Communications Engineering diagram<br />
Phase E. Opportunities &<br />
Solutions<br />
• Project Context<br />
diagram<br />
• Benefits diagram<br />
Requirements Management<br />
• Requirements catalog<br />
Slide 4 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 2
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
P<br />
Preliminary Phase<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
<strong>Catalogs</strong><br />
• Principles Catalog<br />
<strong>Diagrams</strong><br />
Matrices<br />
Slide 5 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
P<br />
Catalog<br />
Principles<br />
Catalog<br />
<strong>Catalogs</strong><br />
Purpose<br />
The Principles catalog captures principles of the business and architecture<br />
principles that describe what a "good" solution or architecture should look<br />
like. Principles are used to evaluate and agree an outcome for architecture<br />
decision points. Principles are also used as a tool to assist in architectural<br />
governance of change initiatives.<br />
The Principles catalog contains the following metamodel entities:<br />
* Principle<br />
Slide 6 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 3
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
A<br />
Architecture Vision<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
<strong>Catalogs</strong><br />
Matrices<br />
• Stakeholder Map Matrix<br />
<strong>Diagrams</strong><br />
• Value Chain Diagram<br />
• Solution Concept Diagram<br />
Slide 7 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
A<br />
Stakeholder<br />
CxO<br />
Example Stakeholder Map<br />
Matrix<br />
Involvement<br />
This stakeholder group is interested in the<br />
high-level drivers, goals and objectives of<br />
the organization, and how these are<br />
translated into an effective process and IT<br />
architecture to advance the business<br />
Class<br />
Keep<br />
Satisfied<br />
Relevant Artifacts<br />
Business Footprint<br />
Goal/Objective/Service<br />
Model<br />
Organization Chart<br />
Program<br />
Management<br />
Office<br />
This stakeholder group is interested in<br />
prioritizing, funding, and aligning change<br />
activity. An understanding of project content<br />
and technical dependencies adds a further<br />
dimension of richness to portfolio<br />
management and decision making.<br />
Keep<br />
Satisfied<br />
Roadmaps<br />
Business Footprint<br />
Application<br />
Communication<br />
Functional<br />
Decomposition<br />
HR<br />
Key features of the enterprise architecture<br />
are roles and Actors that support the<br />
functions, applications, and technology of<br />
the organization. HR are important<br />
stakeholders in ensuring that the correct<br />
roles and actors are represented.<br />
Keep<br />
Informed<br />
Organization Chart<br />
Organization/Actor/<br />
Location<br />
Slide 8 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 4
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
A<br />
Example Value Chain Diagram<br />
Source: Wikipedia.org<br />
Slide 9 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
A<br />
Value Chain Diagram<br />
Product<br />
& Offer<br />
Sales Fulfilment Payments Servicing<br />
Slide 10 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 5
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
A<br />
Value Chain Diagram<br />
Slide 11 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
A<br />
Example Solution Concept Diagram<br />
• A high-level representation of the solution envisaged<br />
• A pencil sketch of the expected solution at the outset of the<br />
engagement<br />
Customers<br />
Interest,<br />
consideration,<br />
join, re-new<br />
Membership<br />
Conference<br />
Attendance<br />
Certification<br />
Publication<br />
Reliable, 24x7,<br />
self-service<br />
infrastructure<br />
Slide 12 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 6
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
A<br />
Solution Concept Diagram<br />
Slide 13 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
A<br />
Solution Concept Diagram<br />
Today’s use of channels<br />
Tomorrow’s use of channels<br />
High Value Tasks<br />
RM<br />
SERVICE<br />
TEAM<br />
RM<br />
From RM<br />
to ST<br />
SERVICE TEAM<br />
From Service From RM<br />
Team to CC to CC<br />
CALL CENTER<br />
CALL CENTER<br />
From Call<br />
Centre to<br />
Online<br />
From Service<br />
Team to<br />
Online<br />
From RM<br />
to Online<br />
SELF SERVICE<br />
INTERNET PORTAL<br />
SELF SERVICE INTERNET PORTAL<br />
Low Value Tasks<br />
Slide 14 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 7
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Business Architecture<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
<strong>Catalogs</strong><br />
• Organization/Actor catalog<br />
• Driver/Goal/Objective catalog<br />
• Role catalog<br />
• Business Service/Function<br />
catalog<br />
• Location catalog<br />
• Process/Event/Control/Product<br />
catalog<br />
• Contract/Measure catalog<br />
Matrices<br />
• Business Interaction matrix<br />
• Actor/Role matrix<br />
<strong>Diagrams</strong><br />
• Business Footprint diagram<br />
• Business Service/Information<br />
diagram<br />
• Functional Decomposition<br />
diagram<br />
• Product Lifecycle diagram<br />
• Goal/Objective/Service diagram<br />
• Business Use-Case diagram<br />
• Organization Decomposition<br />
diagram<br />
• Process Flow diagram<br />
• Event diagram<br />
Slide 15 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
<strong>Catalogs</strong><br />
Catalog<br />
Organization/<br />
Actor<br />
Catalog<br />
Driver/Goal/<br />
Objective<br />
Catalog<br />
Role Catalog<br />
Purpose<br />
A definitive listing of all participants that interact with IT, including users and owners<br />
of IT systems.<br />
It contains the following metamodel entities:<br />
•Organization Unit, Actor Location (may be included in this catalog if an independent<br />
Location catalog is not maintained)<br />
A cross-organizational reference of how an organization meets its drivers in practical<br />
terms through goals, objectives, and (optionally) measures.<br />
It contains the following metamodel entities:<br />
•Organization Unit, Driver, Goal, Objective, Measure (may optionally be included)<br />
The purpose of the Role catalog is to provide a listing of all authorization levels or<br />
zones within an enterprise. Frequently, application security or behavior is defined<br />
against locally understood concepts of authorization that create complex and<br />
unexpected consequences when combined on the user desktop.<br />
It contains the following metamodel entities:<br />
•Role<br />
Slide 16 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 8
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Catalog<br />
Business<br />
Service /<br />
Function<br />
Catalog<br />
Location<br />
Catalog<br />
Process/<br />
Event/<br />
Control/<br />
Product<br />
Catalog<br />
<strong>Catalogs</strong><br />
Purpose<br />
A functional decomposition in a form that can be filtered, reported on, and queried, as<br />
a supplement to graphical Functional Decomposition diagrams.<br />
It contains the following metamodel entities:<br />
•Organization Unit,Business Function, Business Service, Information System Service<br />
(may optionally be included here)<br />
A listing of all locations where an enterprise carries out business operations or<br />
houses architecturally relevant assets, such as data centers or end-user computing<br />
equipment.<br />
It contains the following metamodel entities:<br />
•Location<br />
The Process/Event/Control/Product catalog provides a hierarchy of processes, events<br />
that trigger processes, outputs from processes, and controls applied to the execution<br />
of processes. This catalog provides a supplement to any Process Flow diagrams that<br />
are created and allows an enterprise to filter, report, and query across organizations<br />
and processes to identify scope, commonality, or impact.<br />
It contains the following metamodel entities:<br />
•Process, Event, Control, Product<br />
Slide 17 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Catalog<br />
Contract/<br />
Measure<br />
Catalog<br />
<strong>Catalogs</strong><br />
Purpose<br />
A listing of all agreed service contracts and (optionally) the measures<br />
attached to those contracts. It forms the master list of service levels<br />
agreed to across the enterprise.<br />
It contains the following metamodel entities:<br />
•Business Service<br />
•Information System Service (optionally)<br />
•Contract<br />
•Measure<br />
Slide 18 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 9
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Matrices<br />
• Business Interaction matrix<br />
• Actor/Role matrix<br />
Slide 19 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Business Interaction Matrix<br />
• The purpose of this matrix is to depict the relationship<br />
interactions between organizations and business functions<br />
across the enterprise.<br />
Providing Business Services<br />
Consuming Business Services Engineering Procurement Manufacturing Sales and Distribution Customer Service<br />
Engineering<br />
Procurement<br />
Manufacturing<br />
Sales and Distribution<br />
Customer Service<br />
Contract for<br />
supply of<br />
product<br />
specification<br />
Contract for<br />
supply of<br />
materials<br />
Slide 20 ©2009-2011 The Open Group, All Rights Reserved<br />
Contract for<br />
supply of product<br />
Contract for supply of<br />
sales forecasts<br />
Contract for fulfillment of<br />
customer orders<br />
Copyright © 2009-2011, The Open Group 10
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Actor/role Matrix<br />
• The purpose of this matrix is to show which actors perform<br />
which roles, supporting definition of security and skills<br />
requirements.<br />
Office of<br />
CIO Actors<br />
Steering Group<br />
Actors<br />
Business Unit<br />
Actors<br />
Strategy and Architecture<br />
Actors<br />
Infrastructure<br />
Implementation<br />
Actors<br />
CIO<br />
Enterprise Architect<br />
Enterprise Design Authority<br />
Technical Design Authority<br />
IT Management Forum<br />
Business Unit Head<br />
R = Responsible for carrying out the role<br />
A = Accountable for actors carrying out the role<br />
C = Consulted in carrying out the role<br />
I = Informed in carrying out the role<br />
Strategy Lifecycle Roles<br />
Architecture Refresh I R A I C C R C C C I I R I C C<br />
Architecture Roadmap I C A I R C C I C R I I R C C I C<br />
Benefits Assessment I I I I I I I I I R R I C A<br />
Change Management C I A I I I R I I I R R C<br />
Framework Refresh C C C C C I C A I I I R C C I<br />
Project Lifecycle Roles<br />
Solution Architecture Vision I I I A I I C C I I R I C C R<br />
Logical Solution Architecture A I I C C I I R I C C C R<br />
Physical Solution Architecture A I I C C I I R I C R C R<br />
Design Governance A I I C C I I R I C R C C<br />
Architecture Configuration Management C I I R R R A<br />
Business Unit Service Owner<br />
Business Unit Application Architect<br />
Head of Strategy and Architecture<br />
Infrastructure Strategist<br />
Infrastructure Solution Architect<br />
Architecture Configuration Manager<br />
Enterprise Infrastructure Architect<br />
Head of Implementation<br />
Infrastructure Designer<br />
IT Operations<br />
Project Manager<br />
External Vendors / Suppliers<br />
Slide 21 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
<strong>Diagrams</strong><br />
• Business Footprint diagram<br />
• Business Service/Information diagram<br />
• Functional Decomposition diagram<br />
• Product Lifecycle diagram<br />
• Goal/Objective/Service diagram<br />
• Business Use-Case diagram<br />
• Organization Decomposition diagram<br />
• Process Flow diagram<br />
• Event diagram<br />
Slide 22 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 11
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Business Footprint Diagram<br />
• Describes the links between business goals, organizational<br />
units, business functions, and services, and maps these<br />
functions to the technical components delivering the<br />
required capability.<br />
• Demonstrates only the key facts linking organization unit<br />
functions to delivery services and is utilized as a<br />
communication platform for senior-level (CxO) stakeholders<br />
Slide 23 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B Example Business Footprint Diagram<br />
Slide 24 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 12
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Business Footprint Diagram<br />
Business Process<br />
Integration Layer<br />
C0 Orderto-Cash<br />
Order<br />
C1 C2 C3 C4 C5<br />
Manage<br />
Receive<br />
Process<br />
Distribute<br />
Invoice<br />
Accounts<br />
Order<br />
Order<br />
Goods / Services<br />
Customer<br />
Receivable<br />
Cash<br />
Store Operations<br />
Support Services<br />
Supply Chain Mgmt<br />
Functional<br />
Services Layer<br />
User Management<br />
Layer<br />
Buyer<br />
Portal<br />
Employee<br />
Portal<br />
Exchanges<br />
Supplier<br />
Portal<br />
Customer<br />
Portal<br />
Partner<br />
Portal<br />
Others<br />
Slide 25 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Business Footprint Diagram<br />
SC1 – Plan &<br />
manage the demand<br />
SC2 –<br />
Plan sales &<br />
operations<br />
SC3 –<br />
Establish inventory<br />
plan<br />
SC4 –<br />
Define<br />
manufacturing<br />
plan<br />
SC5 - Plan goods<br />
movements and<br />
resources in the<br />
distribution network<br />
SC6 –<br />
Schedule & execute<br />
goods movements,<br />
storage and<br />
transportation<br />
decisions<br />
SC11 - Monthly<br />
Forecast Generation<br />
SC12 - Monthly<br />
Forecast Collaboration<br />
SC17 – Forecast<br />
Weekly Update<br />
SC16 – Demand<br />
explosion for assembly<br />
SC13 – Planned<br />
demand consumption<br />
by customer order<br />
SC14 – Allocation<br />
Definition Rules for<br />
ATP (monthly)<br />
SC15 – Allocation<br />
Definition Rules for<br />
ATP (daily)<br />
SC0 - Referential<br />
SC22 – Cross-UOT Demand & Supply Balancing<br />
SC51 – Logistics Capacity<br />
SC61 – Warehouse<br />
and LP S&OP validation<br />
Planning<br />
Management<br />
SC52 – Distribution<br />
Supply Planning – mid-<br />
SC62 – Long Distance<br />
SC21 – UOT and LPS Tactical Supply Planning<br />
Term<br />
Transportation<br />
SC42 – Multi-Plant<br />
SC53 – Distribution<br />
SC32 – Inventory<br />
Planning<br />
Supply Planning – short-<br />
SC63– Short-Distance<br />
Management Rules<br />
Term<br />
Transportation<br />
Parameter Definition<br />
SC54 - Distribution<br />
shortage management<br />
GFB57- Process steps<br />
SC41 – Plant<br />
traceability<br />
Production Planning<br />
SC55 – Deployment<br />
SC65 – Transportation<br />
SC56 – Intra-group<br />
administration<br />
exchanges management<br />
GFB58 – Product<br />
SC57 – Procurement<br />
Traceability<br />
exchanges management<br />
SC70 - Inventory Management (physical and planned inventory including internal transfer orders)<br />
SC04 - Inventory<br />
Norms Definition<br />
GFB64 - Supply Chain Costs & Margin Referential<br />
GFB63 – Demand<br />
Planning Referential<br />
GFB61 – Supply Chain Referential – Logistics<br />
GFB62 – Supply Chain Referential – Production Process Model<br />
Resource<br />
GFB65 - Supply Chain Referential – Production & Distribution & Ship to Customer Network<br />
SC9<br />
-BI<br />
SC91 – Demand BI /<br />
Reporting<br />
SC92 – Tactical Planning<br />
BI / Reporting<br />
GFB59 – Product & Services – Client Catalog<br />
GFB50 – Product & Services Referential<br />
GFB51 - Client Referential<br />
SC93 – Inventory BI / SC94 – Plant Planning BI<br />
Reporting<br />
/ Reporting<br />
GFB70 – Global Cross-Domain Reporting & Analysis<br />
Slide 26 ©2009-2011 The Open Group, All Rights Reserved<br />
SC95 – Distribution<br />
Planning BI / Reporting<br />
SC96 – Logistics BI /<br />
Reporting<br />
Copyright © 2009-2011, The Open Group 13
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Business Footprint Diagram<br />
Slide 27 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Business Service/Information Diagram<br />
• Shows the information needed to support one or more<br />
business services.<br />
• Shows what data is consumed by or produced by a<br />
business service and may also show the source of<br />
information.<br />
• Shows an initial representation of the information present<br />
within the architecture and therefore forms a basis for<br />
elaboration and refinement within Phase C (Data<br />
Architecture).<br />
Slide 28 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 14
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Example Business Service/Information<br />
Diagram<br />
Basic example<br />
Slide 29 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Example Business Service/Information<br />
Diagram<br />
Extended example showing actors<br />
and service interactions<br />
Slide 30 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 15
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
Business Services and<br />
Information Diagram<br />
Slide 31 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
Business Services and<br />
Information Diagram<br />
Slide 32 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 16
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Functional Decomposition Diagram<br />
• It shows on a single page the capabilities of an organization<br />
that are relevant to the consideration of an architecture.<br />
• By examining the capabilities of an organization from a<br />
functional perspective, it is possible to quickly develop<br />
models of what the organization does without being<br />
dragged into extended debate on how the organization<br />
does it.<br />
Slide 33 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Example Functional Decomposition<br />
Diagram<br />
Slide 34 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 17
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Functional Decomposition Diagram<br />
Support<br />
Primary<br />
Admin Finance<br />
Human<br />
Business<br />
Marketing<br />
Resources Planning<br />
&<br />
Engineering Inventory Manufacturing Distribution<br />
Sales<br />
Manage Public<br />
Relations<br />
Develop & Track<br />
Financial Plan<br />
Plan Human<br />
Resources<br />
Formulate<br />
Strategy<br />
Develop New<br />
Business<br />
Research and<br />
Develop<br />
Technology<br />
Plan Material<br />
Requirements<br />
Plan<br />
Manufacturing<br />
Requirements<br />
Engineer<br />
Packages<br />
Provide Legal<br />
Services<br />
Appropriate<br />
Funds<br />
Acquire<br />
Human<br />
Resources<br />
Develop and<br />
Maintain<br />
Business Plan<br />
Establish<br />
Customer<br />
Requirements<br />
Engineer and<br />
Design Products<br />
Procure<br />
Equipment<br />
Material & Tools<br />
Perform Quality<br />
Engineering<br />
Ship<br />
Products<br />
Perform<br />
Audit<br />
& Controls<br />
Develop &<br />
Manage<br />
Product Cost<br />
Develop<br />
Employees<br />
Obtain Sales<br />
Commitments<br />
Engineer and<br />
Design<br />
Processes<br />
Manage<br />
Suppliers<br />
Convert<br />
Resources<br />
to Product<br />
Manage<br />
Transportation<br />
Manage<br />
Payables<br />
Provide<br />
Employee<br />
Services<br />
Provide<br />
Customer<br />
Support<br />
Design Tools<br />
and Equipment<br />
Manage<br />
Inventory<br />
Control<br />
Production<br />
Maintain<br />
Facilities<br />
Manage<br />
Receivables<br />
Manage Union<br />
Activities<br />
Manage<br />
Engineering<br />
Changes<br />
Maintain Plant<br />
Equipment &<br />
Tools<br />
Provide<br />
Administrative<br />
Services<br />
Manage Assets<br />
Terminate Active<br />
Employment<br />
Manage<br />
Warranty<br />
Activities<br />
Slide 35 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Product Lifecycle Diagram<br />
• This assists in understanding the lifecycles of key entities within the<br />
enterprise.<br />
• Understanding product lifecycles is becoming increasingly important<br />
with respect to environmental concerns, legislation, and regulation<br />
where products must be tracked from manufacture to disposal.<br />
• Equally, organizations that create products that involve personal or<br />
sensitive information must have a detailed understanding of the product<br />
lifecycle during the development of Business Architecture in order to<br />
ensure rigor in design of controls, processes, and procedures.<br />
Examples of this include credit cards, debit cards, store/loyalty cards,<br />
smart cards, user identity credentials (identity cards, passports, etc.).<br />
Slide 36 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 18
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Example Product Lifecycle Diagram<br />
Source: Kotler and Armstrong, 2004<br />
Slide 37 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B Example Product Lifecycle Diagram<br />
Slide 38 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 19
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Goal/Objective/Service<br />
Diagram<br />
• This defines the ways in which a service contributes to the<br />
achievement of a business vision or strategy.<br />
• Services are associated with the drivers, goals, objectives,<br />
and measures that they support, allowing the enterprise to<br />
understand which services contribute to similar aspects of<br />
business performance.<br />
• This also provides qualitative input on what constitutes high<br />
performance for a particular service.<br />
Slide 39 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Example Goal/Objective/<br />
Service Diagram<br />
gol-Increase<br />
revenues<br />
rol-CFO<br />
rol-VP Marketing<br />
rol-VP Sales<br />
obj-"aftersales"<br />
market<br />
obj-creating<br />
new line of cars<br />
by the end of...<br />
Functionsales<br />
and<br />
marketing<br />
c a p -<br />
M a rk e t in g<br />
cap-Pre-<br />
O w n e d<br />
ve h ic a . ..<br />
c a p -<br />
ca m paign<br />
c a p - S a l e s<br />
cap-Pre-sale<br />
Slide 40 ©2009-2011 The Open Group, All Rights Reserved<br />
c a p - O r d e r-<br />
to - D e live r y<br />
Copyright © 2009-2011, The Open Group 20
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Business Use-case Diagram<br />
• This displays the relationships between consumers and<br />
providers of business services.<br />
• Business services are consumed by actors or other<br />
business services and the Business Use-Case diagram<br />
provides added richness in describing business capability<br />
by illustrating how and when that capability is used.<br />
• They help to describe and validate the interaction between<br />
actors and their roles to processes and functions.<br />
• As the architecture progresses, the use-case can evolve<br />
from the business level to include data, application, and<br />
technology details. Architectural business use-cases can<br />
also be re-used in systems design work.<br />
Slide 41 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Example Use-case Diagram<br />
Slide 42 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 21
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Organization Decomposition Diagram<br />
• This describes the links between actor, roles, and location<br />
within an organization tree.<br />
• An organization map should provide a chain of command of<br />
owners and decision-makers in the organization.<br />
Slide 43 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Example Organization Decomposition<br />
Diagram<br />
rol-CEO<br />
org-Worldwide Public<br />
Affairs and Policy<br />
org-Chief Medical Officer<br />
org-Global<br />
Research &<br />
Development<br />
rol-Vice Chairman<br />
rol-Wolrdwide Pharmaceutical<br />
Operations<br />
org-Wolrdwide talent<br />
Development and HR<br />
org-General Counsel<br />
rol-Field Based Govt.<br />
Relations<br />
rol-Wolrdwide Medical<br />
rol-Wolrdwide<br />
Research<br />
rol-Global Manufacturing<br />
loc-US<br />
rol-Talent<br />
Development<br />
rol-Intellectual Property<br />
rol-CFO<br />
rol-Wolrdwide<br />
Communications<br />
rol-Safety Risk<br />
Management<br />
rol-Worldwide<br />
Development<br />
rol-Worlwide Strategic Planning<br />
loc-Japan/ASIA<br />
rol-HealthWelness<br />
rol-Employment Law<br />
rol-Philanthropy/Stakeholder<br />
Advocacy<br />
rol-Science Advocacy<br />
rol-Worldwide<br />
Research Affairs<br />
rol-Animal Health<br />
loc-Europe<br />
rol-Planning<br />
rol-Line Support<br />
rol-Worldwide Policy<br />
rol-Financ ial Strategy<br />
rol-Worldwide Licensing and<br />
Business Develoment<br />
rol-Diversity and<br />
Inclusion<br />
rol-Litigation/Regulatory<br />
rol-Federal Government<br />
relations<br />
rol-Human Resources<br />
rol-Wolrdwide Technology<br />
loc-Middle East<br />
rol-compensation and<br />
Benefits<br />
rol-Business Transactions<br />
rol-Business Services<br />
rol-Complinace Officer<br />
loc-Canada<br />
rol-Site Leader(s)<br />
rol-Wolrdwide Investor<br />
Development<br />
rol-Internal Audit<br />
Slide 44 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 22
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Process Flow Diagram<br />
• This depicts all models and mappings related to the process<br />
metamodel entity.<br />
• It shows sequential flow of control between activities and<br />
may utilize swim-lane techniques to represent ownership<br />
and realization of process steps.<br />
• In addition to showing a sequence of activity, process flows<br />
can also be used to detail the controls that apply to a<br />
process, the events that trigger or result from completion of<br />
a process, and also the products that are generated from<br />
process execution.<br />
Slide 45 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Example Process Flow<br />
Diagram<br />
Start<br />
Step 1 Step 2 Step 3 Step 4<br />
Step 5 Step 6 Step 6 Step 6 STOP<br />
Slide 46 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 23
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Technical Support<br />
Team<br />
Example Process Flow<br />
Diagram<br />
Sales Rep<br />
Pricer<br />
Pricer<br />
Start<br />
Step 1 Step 2 Step 3 Step 4<br />
Custom app<br />
Email<br />
CRM<br />
MS Word<br />
MS Excel<br />
Custom Bid<br />
Approver<br />
Customer Rep Customer Rep Customer Rep<br />
Step 5 Step 6 Step 6 Step 6 STOP<br />
IWF<br />
email<br />
Consolidation<br />
Tool<br />
Spreadsheet<br />
Process Flow (w/Roles & Applications)<br />
Slide 47 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Events Diagram<br />
• This depicts the relationship between events and process.<br />
• Certain events - such as arrival of information (e.g. a<br />
customer’s sales order) or a point in time (e.g. end of fiscal<br />
quarter) cause work and actions to be undertaken within<br />
the business.<br />
Slide 48 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 24
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
B<br />
Example Events Diagram<br />
Event<br />
Triggers<br />
Process<br />
Impacts/Generates<br />
Business<br />
result<br />
(e.g. End of Fiscal Quarter)<br />
(e.g. Financial Reporting<br />
Process)<br />
(e.g. 1Q results reported to<br />
Government Agencies)<br />
Slide 49 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
B<br />
Example Events Matrix<br />
EVENT<br />
PROCESS TRIGGERED<br />
BUSINESS RESULT(S)<br />
Customer submits<br />
sales order<br />
Sales order processing<br />
• Create & save sales order<br />
• Generate acknowledgement<br />
• Confirm receipt of customer order<br />
• Begin order fulfilment activities<br />
• Sales order captured in<br />
order book<br />
Customer submits<br />
request for<br />
custom<br />
product<br />
Custom product configuration<br />
• Capture requirements from customer<br />
• Define custom specifications<br />
• Price custom configuration<br />
• Negotiate with customer<br />
• Secure approval from customer regarding<br />
configuration and price<br />
• Custom product<br />
configured<br />
• Customer contract signed<br />
End of quarter<br />
Financial reporting process<br />
• Financial report generated<br />
Slide 50 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 25
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Data Architecture<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
<strong>Catalogs</strong><br />
• Data Entity/Data<br />
Component catalog<br />
Matrices<br />
• Data Entity/Business<br />
Function matrix<br />
• System/Data matrix<br />
<strong>Diagrams</strong><br />
• Class diagram<br />
• Data Dissemination<br />
diagram<br />
• Data Security diagram<br />
• Class Hierarchy diagram<br />
• Data Migration diagram<br />
• Data Lifecycle diagram<br />
Slide 51 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
<strong>Catalogs</strong><br />
Catalog<br />
•Data<br />
Entity/Data<br />
Component<br />
Catalog<br />
Purpose<br />
To identify and maintain a list of all the data use across the<br />
enterprise, including data entities and also the data components<br />
where data entities are stored.<br />
It contains the following metamodel entities:<br />
•Data Entity<br />
•Logical Data Component<br />
•Physical Data Component<br />
Slide 52 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 26
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Matrices<br />
• Data Entity/Business Function matrix<br />
• System/Data matrix<br />
Slide 53 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Data Entity/Business<br />
Function Matrix<br />
• The purpose of the Data Entity/Business Function matrix is to depict the<br />
relationship between data entities and business functions within the<br />
enterprise.<br />
• The mapping of the Data Entity-Business Function relationship enables<br />
the following to take place:<br />
– Assignment of ownership of data entities to organizations<br />
– Understand the data and information exchange requirements business<br />
services<br />
– Support the gap analysis and determine whether any data entities are<br />
missing and need to be created<br />
– Define system of origin, system of record, and system of reference for data<br />
entities<br />
– Enable development of data governance programs across the enterprise<br />
(establish data steward, develop data standards pertinent to the business<br />
function, etc.)<br />
Slide 54 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 27
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Example Data Entity/Business Function<br />
Matrix<br />
BUSINESS<br />
FUNCTION<br />
(Y-AXIS) AND<br />
DATA<br />
ENTITY (X-AXIS)<br />
CUSTOMER<br />
MASTER<br />
BUSINESS<br />
PARTNER<br />
CUSTOMER<br />
LEADS<br />
PRODUCT<br />
MASTER<br />
Customer Relationship<br />
Management<br />
• Business partner data<br />
management service<br />
• Owner – Sales &<br />
Marketing business<br />
unit executive<br />
• Function can Create,<br />
read, update and<br />
delete customer<br />
master data<br />
• Business partner data<br />
management service<br />
• Owner of data entity<br />
(person or organization)<br />
• Function can Create,<br />
read, update and delete<br />
• Lead Processing<br />
Service<br />
• Owner – Customer<br />
Relationship Manager<br />
• Function can only<br />
Create, read, update<br />
customer leads<br />
• N/A<br />
Supply Chain<br />
Management<br />
• Customer<br />
Requirement<br />
Processing Service<br />
• Owner – Supply<br />
Chain Manager<br />
• N/A<br />
• N/A<br />
• Product data<br />
management service<br />
• Owner – Global<br />
product development<br />
organization<br />
Slide 55 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
System/Data Matrix<br />
• The purpose of the System/Data matrix is to depict the<br />
relationship between systems (i.e., application components)<br />
and the data entities that are accessed and updated by<br />
them.<br />
• Systems will create, read, update, and delete specific data<br />
entities that are associated with them. For example, a CRM<br />
application will create, read, update, and delete customer<br />
entity information.<br />
Slide 56 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 28
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Example System/Data Matrix<br />
APPLICATION (Y-<br />
AXIS) AND DATA<br />
(X-AXIS)<br />
DESCRIPTION OR<br />
COMMENTS<br />
DATA ENTITY<br />
DATA ENTITY TYPE<br />
CRM<br />
•System of record for<br />
customer master data<br />
•Customer data<br />
•Master data<br />
Commerce Engine<br />
•System of record for order<br />
book<br />
•Sales orders<br />
•Transactional data<br />
Sales Business<br />
Warehouse<br />
•Warehouse and data mart<br />
that supports North American<br />
region<br />
•Intersection of multiple data<br />
entities (e.g. All sales orders<br />
by customer XYZ and by<br />
month for 2006)<br />
•Historical data<br />
Slide 57 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
<strong>Diagrams</strong><br />
• Class diagram<br />
• Data Dissemination diagram<br />
• Data Security diagram<br />
• Class Hierarchy diagram<br />
• Data Migration diagram<br />
• Data Lifecycle diagram<br />
Slide 58 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 29
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Class Diagram<br />
• The purpose is to depict the relationships among the critical<br />
data entities (or classes) within the enterprise.<br />
Account<br />
I.A1<br />
Information<br />
Update<br />
Account<br />
P.A12<br />
Customer<br />
Profile<br />
I.C2<br />
Actor<br />
Trigger<br />
Contact<br />
P.CS13<br />
Payment<br />
T.P8<br />
Agent<br />
A.A4<br />
Customer<br />
A.C2<br />
Customer<br />
Information<br />
I.C1<br />
Slide 59 ©2009-2011 The Open Group, All Rights Reserved<br />
P.CS5<br />
Service<br />
Request<br />
Appeal<br />
T.C19<br />
Process<br />
Enquiry<br />
Complaint<br />
T.C1<br />
T.C16<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Class Diagram<br />
Slide 60 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 30
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Class Diagram<br />
Slide 61 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Data Dissemination Diagram<br />
• The purpose of the Data Dissemination diagram is to show<br />
the relationship between data entity, business service, and<br />
application components.<br />
• The diagram should show how the logical entities are to be<br />
physically realized by application components.<br />
• Additionally, the diagram may show data replication and<br />
system ownership of the master reference for data.<br />
Slide 62 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 31
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Example Data Dissemination Diagram<br />
Warehouse<br />
Warehouse<br />
Customer<br />
Order History<br />
Stock<br />
Online<br />
Online<br />
Account<br />
Account<br />
Self Service<br />
Self Service<br />
Billing<br />
Billing<br />
Customer<br />
Account Balance<br />
Invoice History<br />
Business Service<br />
Online Account Self Service<br />
Data Entities<br />
Customer<br />
Order History<br />
Stock<br />
Account Balance<br />
Invoice History<br />
Application<br />
•Warehouse<br />
•Billing<br />
•Warehouse<br />
•Warehouse<br />
•Billing<br />
•Billing<br />
Slide 63 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Data Dissemination Diagram<br />
Slide 64 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 32
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Data Dissemination Diagram<br />
Slide 65 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Data Dissemination Diagram<br />
Slide 66 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 33
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Data Lifecycle Diagram<br />
• The Data Lifecycle diagram is an essential part of managing<br />
business data throughout its lifecycle from conception until<br />
disposal within the constraints of the business process.<br />
Fulfilment Order<br />
New<br />
Fulfilled Invoiced Paid Closed Archived Deleted<br />
Customer Order<br />
New<br />
Dispatched<br />
Closed Archived Deleted<br />
Slide 67 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Data Security Diagram<br />
• The purpose of the Data Security diagram is to depict which<br />
actor (person, organization, or system) can access which<br />
enterprise data.<br />
• This relationship can also be shown in a matrix form<br />
between two objects or can be shown as a mapping.<br />
Slide 68 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 34
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Example Data Security<br />
Diagram<br />
Class of Roles (by job<br />
function)<br />
Actor<br />
Business<br />
Function<br />
Process<br />
Physical Access<br />
Single Sign-on or<br />
Access Control<br />
Location<br />
Business<br />
Service<br />
Access Control (levels of<br />
granularity)<br />
Access Control (levels of<br />
granularity)<br />
Logical<br />
Application<br />
Component<br />
Slide 69 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example Data Security Matrix<br />
ACTOR<br />
CLASS OF<br />
ROLES (JOB<br />
FUNCTION)<br />
FUNCTION<br />
BUSINESS<br />
SERVICE<br />
LOCATION<br />
TYPE OF<br />
ACCESS<br />
Financial Analyst<br />
SOA Portfolio<br />
Financial Analyst<br />
Financial Analysis<br />
SOA portfolio service<br />
• NA (US, CA)<br />
• EMEA (UK, DE)<br />
• APJ<br />
• Physical<br />
• Access Control<br />
(tables xyz only)<br />
Procurement &<br />
Spend Analyst<br />
Procurement<br />
Management and<br />
Control<br />
WW Direct<br />
Procurement<br />
Supplier portal<br />
Service<br />
• NA (US<br />
Midwest)<br />
• Access control<br />
WW Contracts<br />
System (application)<br />
Not applicable<br />
WW Direct<br />
Procurement<br />
Supplier Portal<br />
Service<br />
• LA<br />
• Access control<br />
(system to<br />
system)<br />
WW Product<br />
Development (Org<br />
Unit)<br />
Geo Brand Managers<br />
WW Direct<br />
Procurement<br />
Supplier Portal<br />
Service<br />
• WW (all Geos)<br />
• Access Control<br />
Slide 70 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 35
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Data Migration Diagram<br />
• The purpose of the Data Migration diagram is to show the<br />
flow of data from the source to the target applications.<br />
• The diagram will provide a visual representation of the<br />
spread of sources/targets and serve as a tool for data<br />
auditing and establishing traceability.<br />
Slide 71 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example Data Migration<br />
Diagram<br />
“Baseline”<br />
application<br />
components<br />
ABM<br />
Source of<br />
Customer records<br />
CCB<br />
Data migration technology<br />
components<br />
“Target”<br />
application<br />
components<br />
CRM<br />
System of Record<br />
for Customer Master<br />
BDW<br />
Source of order<br />
history<br />
ERP<br />
System of Record for<br />
Material Master & Order<br />
history<br />
MRPA<br />
Source of Material<br />
data<br />
Source<br />
Staging<br />
Transformation &<br />
Data Quality<br />
Target<br />
Staging<br />
SRM<br />
VLC (one<br />
per geo)<br />
Source of vendor<br />
data<br />
System of Record for<br />
Vendor Master &<br />
Contracts<br />
Slide 72 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 36
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Example Data Migration<br />
Mapping<br />
SOURCE LOGICAL<br />
APPLICATION<br />
COMPONENT<br />
SOURCE DATA ELEMENT<br />
TARGET LOGICAL<br />
APPLICATION<br />
COMPONENT<br />
TARGET DATA ELEMENT<br />
ABM<br />
Cust_Name<br />
CRM<br />
CUSTNAME<br />
Cust_Street_Addr<br />
CUSTADDR_LINE1<br />
Cust_Street_Addr<br />
CUSTADDR_LINE2<br />
Cust_Street_Addr<br />
CUSTADDR_LINE3<br />
Cust_ContactName<br />
CUSTCONTACT<br />
Cust_Tele<br />
CUSTTELEPHONE<br />
Slide 73 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Class Hierarchy Diagram<br />
• The purpose of the Class Hierarchy diagram is to show the<br />
technical stakeholders a perspective of the class hierarchy.<br />
• This diagram gives the stakeholders an idea of who is using<br />
the data, how, why, and when.<br />
Slide 74 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 37
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Example Class Hierarchy Diagram<br />
Authorised User<br />
Authorised User<br />
Keeper<br />
Keeper<br />
Vehicle Tester<br />
Vehicle Tester<br />
Individual<br />
Individual<br />
Customer<br />
Customer<br />
Purchaser/Nominee<br />
Purchaser/Nominee<br />
Trainer/Booker<br />
Trainer/Booker<br />
Driver<br />
Driver<br />
Organisation<br />
Organisation<br />
Manufacturer<br />
Manufacturer<br />
Driving<br />
Driving<br />
Instructor<br />
Instructor<br />
Operator<br />
Operator<br />
Taxi Driver<br />
Taxi Driver<br />
Dealing<br />
Dealing<br />
Driving Examiner<br />
Driving Examiner<br />
Driving Examiner<br />
Driving Examiner<br />
Slide 75 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Application Architecture<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
<strong>Catalogs</strong><br />
• Application Portfolio catalog<br />
• Interface catalog<br />
Matrices<br />
• System/Organization matrix<br />
• Role/System matrix<br />
• System/Function matrix<br />
• Application Interaction matrix<br />
<strong>Diagrams</strong><br />
• Application Communication<br />
diagram<br />
• Application and User Location<br />
diagram<br />
• System Use-Case diagram<br />
• Enterprise Manageability<br />
diagram<br />
• Process/System Realization<br />
diagram<br />
• Software Engineering diagram<br />
• Application Migration diagram<br />
• Software Distribution diagram<br />
Slide 76 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 38
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Catalog<br />
Application<br />
Portfolio Catalog<br />
<strong>Catalogs</strong><br />
Purpose<br />
To identify and maintain a list of all the applications in the enterprise. This list helps to<br />
define the horizontal scope of change initiatives that may impact particular kinds of<br />
applications. An agreed Application Portfolio allows a standard set of applications to<br />
be defined and governed.<br />
Interface Catalog<br />
It contains the following metamodel entities:<br />
•Information System Service<br />
•Logical Application Component<br />
•Physical Application Component<br />
The purpose of the Interface catalog is to scope and document the interfaces<br />
between applications to enable the overall dependencies between applications to be<br />
scoped as early as possible.<br />
It contains the following metamodel entities:<br />
•Logical Application Component<br />
•Physical Application Component<br />
•Application communicates with application relationship<br />
Slide 77 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Matrices<br />
• System/Organization matrix<br />
• Role/System matrix<br />
• System/Function matrix<br />
• Application Interaction matrix<br />
Slide 78 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 39
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
System/Organization Matrix<br />
• The purpose of this matrix is to depict the relationship<br />
between systems (i.e., application components) and<br />
organizational units within the enterprise.<br />
• The mapping of the Application Component-Organization<br />
Unit relationship is an important step as it enables the<br />
following to take place:<br />
– Assign usage of applications to the organization units that perform<br />
business functions<br />
– Understand the application support requirements of the business<br />
services and processes carried out by an organization unit<br />
– Support the gap analysis and determine whether any of the<br />
applications are missing and as a result need to be created<br />
– Define the application set used by a particular organization unit<br />
Slide 79 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example System/Organization Matrix<br />
APPLICATION<br />
(Y-AXIS)<br />
AND<br />
ORGANISATION<br />
UNIT (X-AXIS)<br />
CUSTOMER<br />
SERVICES<br />
PROCUREMENT AND<br />
WAREHOUSING<br />
HR<br />
CORPORATE<br />
FINANCE<br />
SAP HR<br />
X<br />
X<br />
X<br />
SIEBEL<br />
X<br />
X<br />
SAP FINANCIALS<br />
X<br />
X<br />
X<br />
PROCURESOFT<br />
X<br />
X<br />
Slide 80 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 40
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Role/System Matrix<br />
• The purpose of the Role/System matrix is to depict the relationship<br />
between systems (i.e., application components) and the business roles<br />
that use them within the enterprise.<br />
• The mapping of the Application Component-Role relationship is an<br />
important step as it enables the following to take place:<br />
– Assign usage of applications to the specific roles in the organization<br />
– Understand the application security requirements of the business services<br />
and processes supporting the function, and check these are in line with<br />
current policy<br />
– Support the gap analysis and determine whether any of the applications are<br />
missing and as a result need to be created<br />
– Define the application set used by a particular business role; essential in<br />
any move to role-based computing<br />
Slide 81 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example Role/System Matrix<br />
APPLICATION (Y-<br />
AXIS) AND<br />
FUNCTION (X-<br />
AXIS)<br />
CALL CENTRE<br />
OPERATOR<br />
CALL CENTRE<br />
MANAGER<br />
FINANCE ANALYST<br />
CHIEF<br />
ACCOUNTANT<br />
SAP HR<br />
X<br />
X<br />
X<br />
X<br />
SIEBEL<br />
X<br />
X<br />
SAP FINANCIALS<br />
X<br />
X<br />
X<br />
X<br />
PROCURESOFT<br />
X<br />
X<br />
Slide 82 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 41
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
System/Function Matrix<br />
• The purpose of the System/Function matrix is to depict the<br />
relationship between systems (i.e., application components)<br />
and business functions within the enterprise.<br />
• The mapping of the Application Component-Function<br />
relationship is an important step as it enables the following<br />
to take place:<br />
– Assign usage of applications to the business functions that are<br />
supported by them<br />
– Understand the application support requirements of the business<br />
services and processes carried out<br />
– Support the gap analysis and determine whether any of the<br />
applications are missing and as a result need to be created<br />
– Define the application set used by a particular business function<br />
Slide 83 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example System/Function<br />
Matrix<br />
APPLICATION (Y-<br />
AXIS) AND<br />
FUNCTION (X-<br />
AXIS)<br />
CALL CENTRE 1 ST<br />
LINE<br />
WAREHOUSE<br />
CONTROL<br />
VACANCY FILLING<br />
GENERAL LEDGER<br />
MAINTENANCE<br />
SAP HR<br />
X<br />
X<br />
X<br />
X<br />
SIEBEL<br />
X<br />
X<br />
SAP FINANCIALS<br />
X<br />
X<br />
X<br />
PROCURESOFT<br />
X<br />
X<br />
Slide 84 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 42
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
<strong>Diagrams</strong><br />
• Application Communication diagram<br />
• N2 model or Node Connectivity diagram<br />
• Application and User Location diagram<br />
• System Use-Case diagram<br />
• Enterprise Manageability diagram<br />
• Process/System Realization diagram<br />
• Software Engineering diagram<br />
• Application Migration diagram<br />
• Software Distribution diagram<br />
Slide 85 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Application Communication Diagram<br />
• The purpose of the Application Communication diagram is<br />
to depict all models and mappings related to communication<br />
between applications in the metamodel entity.<br />
• It shows application components and interfaces between<br />
components.<br />
• Communication should be logical and should only show<br />
intermediary technology where it is architecturally relevant.<br />
Slide 86 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 43
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Example Application<br />
Communication Diagram<br />
Slide 87 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Application Communication<br />
Diagram<br />
Slide 88 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 44
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Application Communication<br />
Diagram<br />
Slide 89 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
N2 Model<br />
ABC<br />
1a<br />
1c<br />
1b<br />
ABM<br />
2a<br />
3c<br />
CCD<br />
3a<br />
1d<br />
3b<br />
CRM<br />
4a<br />
3d<br />
4b<br />
IPC<br />
Slide 90 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 45
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Information Exchange Matrix<br />
LABEL<br />
SOURCE<br />
DESTINATION<br />
DATA ENTITY<br />
EVENT<br />
TRIGGERED<br />
1a<br />
• ABC<br />
• ABM<br />
• Sales order<br />
(create<br />
request)<br />
• New sales<br />
order from front<br />
end<br />
1b<br />
• ABM<br />
• ABC<br />
• Sales order<br />
(confirm create)<br />
• Order created<br />
in the backend<br />
ERP system<br />
2a<br />
• ABM<br />
• CCD<br />
• Product catalog<br />
• Subscribe/Publi<br />
sh timer<br />
Slide 91 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Application & User Location Diagram<br />
• The purpose of this diagram is to clearly depict the business<br />
locations from which business users typically interact with<br />
the applications, but also the hosting location of the<br />
application infrastructure.<br />
• The diagram enables:<br />
– Identification of the number of package instances needed<br />
– Estimation of the number and the type of user licenses<br />
– Estimation of the level of support needed<br />
– Selection of system management tools, structure, and management<br />
system<br />
– Appropriate planning for the technological components of the<br />
business<br />
– Performance considerations while implementing solutions<br />
Slide 92 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 46
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Example Application & User Location<br />
Diagram (part 1)<br />
APPLICATION<br />
USER TYPE<br />
INTERNAL,<br />
CUSTOMER<br />
OR<br />
PARTNER<br />
USER<br />
BUSINESS<br />
LOCATION<br />
LOCATION<br />
ADDRESS<br />
ORG UNIT (USER<br />
BELONGS TO)<br />
CRM<br />
Developer<br />
Super User<br />
Administrator<br />
Internal<br />
NA Western<br />
Region<br />
EMEA<br />
Headquarters,<br />
UK<br />
Chicago Sears<br />
tower office<br />
Chicago<br />
Downtown office<br />
Middlesex, London<br />
NA Sales &<br />
Marketing<br />
EMEA Sales<br />
SAP R/3<br />
Test Engineers<br />
Mechanical<br />
Engineers<br />
Procurement<br />
managers<br />
Internal<br />
Beijing<br />
Manufacturing<br />
Plant<br />
Manufacturing &<br />
logistics<br />
Slide 93 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
CExample Application & User Location<br />
Diagram (part 2)<br />
Slide 94 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 47
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Application and User Location<br />
Diagram<br />
Slide 95 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Application and User Location<br />
Diagram<br />
Slide 96 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 48
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Application and User Location<br />
Diagram<br />
Slide 97 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
System Use Case Diagram<br />
Source: wikipedia.org<br />
Slide 98 ©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 49
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
System Use Case Diagram<br />
Slide 99 ©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
System Use Case Diagram<br />
Slide<br />
100<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 50
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Enterprise Manageability Diagram<br />
• The Enterprise Manageability diagram shows how one or<br />
more applications interact with application and technology<br />
components that support operational management of a<br />
solution.<br />
• Analysis can reveal duplication and gaps, and opportunities<br />
in the IT service management operation of an organization.<br />
Slide<br />
101<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example Enterprise Manageability<br />
Diagram<br />
Slide<br />
102<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 51
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Process/System Realization Diagram<br />
• The purpose of the Process/System Realization diagram is<br />
to clearly depict the sequence of events when multiple<br />
applications are involved in executing a business process.<br />
• It enhances the Application Communication diagram by<br />
augmenting it with any sequencing constraints, and hand-off<br />
points between batch and real-time processing.<br />
Slide<br />
103<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example Process/System<br />
Realization Diagram<br />
Slide<br />
104<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 52
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Software Engineering<br />
Diagram<br />
• The Software Engineering diagram breaks applications into<br />
packages, modules, services, and operations from a<br />
development perspective.<br />
• It enables more detailed impact analysis when planning<br />
migration stages, and analyzing opportunities and solutions.<br />
• It is ideal for application development teams and application<br />
management teams when managing complex development<br />
environments.<br />
Slide<br />
105<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example Software<br />
Engineering Diagram<br />
Slide<br />
106<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 53
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Application/Migration<br />
Diagram<br />
• The Application Migration diagram identifies application<br />
migration from baseline to target application components.<br />
• It enables a more accurate estimation of migration costs<br />
• It should be used to identify temporary applications, staging<br />
areas, and the infrastructure required to support migrations<br />
Slide<br />
107<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
C<br />
Example<br />
Application/Migration Diagram<br />
Slide<br />
108<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 54
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
C<br />
Software Distribution<br />
Diagram<br />
• This diagram is a composite of the Software Engineering<br />
diagram and the Application-User Location diagram.<br />
• Depending on the circumstances, this diagram alone may<br />
be sufficient, or may not be needed.<br />
Slide<br />
109<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Technology Architecture<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
<strong>Catalogs</strong><br />
• Technology Standards catalog<br />
• Technology Portfolio catalog<br />
• Matrices<br />
• System/Technology matrix<br />
<strong>Diagrams</strong><br />
• Environments and Locations<br />
diagram<br />
• Platform Decomposition diagram<br />
• Processing diagram<br />
• Networked Computing/Hardware<br />
diagram<br />
• Communications Engineering<br />
diagram<br />
Slide<br />
110<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 55
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
<strong>Catalogs</strong><br />
• Technology Standards catalog<br />
• Technology Portfolio catalog<br />
Slide<br />
111<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Catalog<br />
Technology<br />
Standards<br />
Catalog<br />
Technology<br />
Portfolio<br />
Catalog<br />
<strong>Catalogs</strong><br />
Purpose<br />
This documents the agreed standards for technology across the enterprise<br />
covering technologies, and versions, the technology lifecycles, and the<br />
refresh cycles for the technology.<br />
It contains the following metamodel entities:<br />
•Platform Service, Logical Technology Component, Physical Technology<br />
Component<br />
The purpose of this catalog is to identify and maintain a list of all the<br />
technology in use across the enterprise, including hardware, infrastructure<br />
software, and application software. An agreed technology portfolio<br />
supports lifecycle management of technology products and versions and<br />
also forms the basis for definition of technology standards<br />
It contains the following metamodel entities:<br />
•Platform Service, Logical Technology Component, Physical Technology<br />
Component<br />
Slide<br />
112<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 56
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Matrices<br />
• System/Technology matrix<br />
Slide<br />
113<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
System/Technology Matrix<br />
• The System/Technology matrix documents the mapping of<br />
business systems to technology platform.<br />
• The System/Technology matrix shows:<br />
– Logical/Physical Application Components<br />
– Services, Logical Technology Components, and Physical<br />
Technology Components<br />
– Physical Technology Component realizes Physical Application<br />
Component relationships<br />
Slide<br />
114<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 57
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Example System/Technology Matrix<br />
LOGICAL<br />
APPLICATION<br />
COMPONENT<br />
PHYSICAL<br />
TECHNOLOGY<br />
COMPONENT<br />
SERVER ADDRESS<br />
IP ADDRESS<br />
ABM<br />
Web server - node 1<br />
F01ws001@host.com<br />
10.xx.xx.xx<br />
Web server - node 2<br />
F01ws002@host.com<br />
10.xx.xx.xx<br />
Web server - node 3<br />
F01ws003@host.com<br />
10.xx.xx.xx<br />
App server – node 1<br />
F02as001@host.com<br />
10.xx.xx.xx<br />
App server – node 2<br />
F02as002@host.com<br />
10.xx.xx.xx<br />
App server – node 3<br />
F02as003@host.com<br />
10.xx.xx.xx<br />
Database server<br />
(production)<br />
F02dbp001@host.com<br />
10.xx.xx.xx<br />
Database server (stating)<br />
F03dbs001@host.com<br />
10.xx.xx.xx<br />
Load balancer and<br />
Dispatcher<br />
Dispatcher server<br />
F03nd001@host.com<br />
242.xx.xx.xx<br />
Slide<br />
115<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Example System/Technology Matrix<br />
TECH<br />
FUNCTION<br />
HARDWARE<br />
LOGICAL<br />
HARDWARE<br />
PHYSICAL<br />
SOFTWARE<br />
LOGICAL<br />
SOFTWARE<br />
PHYSICAL<br />
Load balancing<br />
•Name – Balancer<br />
•Vendor - IBM<br />
•Server Type –<br />
eServer<br />
•Clustered – No<br />
•No. of Nodes – N/A<br />
•Server logical<br />
address -<br />
d04lb01@host.com<br />
•Maintenance Window<br />
– Sun 0100 to 0300<br />
•Model/Type – IBM<br />
P7xx<br />
•Serial Number –<br />
1S4568<br />
•Processor Type -<br />
RISC Power p5<br />
•Number of<br />
Processors - 4 way<br />
•Memory - 8GB<br />
•Hard drive - 4 TB<br />
•IP - 11.xx.xx.xx<br />
•Product- IBM Load<br />
balance manager<br />
•Vendor - IBM<br />
•OS – UNIX based<br />
•SW Components<br />
– LB v3.2 (list all<br />
the other<br />
components of the<br />
SW product)<br />
•AIX 10.2.1<br />
•License Type -<br />
•Enterprise wide<br />
license<br />
•License expiry<br />
date - 12/31/2011<br />
Slide<br />
116<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 58
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Example System/Technology Matrix<br />
APPLICATION COMPONENT<br />
DEPLOYMENT UNIT<br />
TECHNOLOGY COMPONENT<br />
•Load Balancer<br />
•Smart dispatch v1.2 (both<br />
installation and execution code)<br />
•Load balancing server<br />
(d03lb001@host.com)<br />
•Commerce pages<br />
•HTML code<br />
•Applets<br />
•JSP<br />
•Web Server cluster<br />
(d03ws001@host.com,<br />
d03ws002@host.com,<br />
d03ws003@host.com)<br />
•Commerce Engine<br />
•Order Entry (both installation and<br />
execution code)<br />
•Shopping Cart (both installation<br />
and execution code)<br />
•Application Server<br />
(d03as001@host.com,<br />
d03as002@host.com)<br />
Slide<br />
117<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
<strong>Diagrams</strong><br />
• Environments and Locations diagram<br />
• Platform Decomposition diagram<br />
• Processing diagram<br />
• Networked Computing/Hardware diagram<br />
• Communications Engineering diagram<br />
Slide<br />
118<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 59
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Environments and Locations Diagram<br />
• Depicts which locations host which applications<br />
• Identifies what technologies and/or applications are used at<br />
which locations<br />
• Identifies the locations from which business users typically<br />
interact with the applications.<br />
• It should also show the existence and location of different<br />
deployment environments<br />
– including non-production environments, such as development and<br />
pre production.<br />
Slide<br />
119<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Example Environments and Locations<br />
Diagram<br />
app-integration<br />
platform for<br />
suppliers(dexis<br />
)<br />
loc-<br />
Ludwigsburg<br />
loc-Italia<br />
app-<br />
CAD/CAE<br />
loc-<br />
Ludwigsburg<br />
app-R&D<br />
system of<br />
systems<br />
app-Project<br />
managment<br />
system<br />
loc-Japan<br />
tec-Windows<br />
XP<br />
tec-Windows<br />
Vista<br />
tec-RDB<br />
loc-<br />
Stuttgart<br />
tec-OCR<br />
loc-<br />
Ludwigsburg<br />
loc-USA<br />
loc-Italia<br />
loc-Japan<br />
app-<br />
Build-to-<br />
Order<br />
(BTO)<br />
Slide<br />
120<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 60
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Environments and Location<br />
Diagram<br />
Slide<br />
121<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Environments and Location<br />
Diagram<br />
Slide<br />
122<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 61
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Environments and Location<br />
Diagram<br />
Slide<br />
123<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Platform Decomposition<br />
Diagram<br />
• The Platform Decomposition diagram depicts the<br />
technology platform that supports the operations of the<br />
Information Systems Architecture.<br />
• The diagram covers all aspects of the infrastructure platform<br />
and provides an overview of the enterprise's technology<br />
platform.<br />
Slide<br />
124<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 62
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Example Platform<br />
Decomposition Diagram<br />
Platform Decomposition (Application Support)<br />
Hardware<br />
Software<br />
Logical Technology<br />
Components<br />
Physical Technology<br />
Components<br />
Logical Technology<br />
Components<br />
Physical Technology<br />
Components<br />
Tech Function<br />
Tech Function<br />
Tech Function<br />
Tech Function<br />
Web Server<br />
Layer<br />
Web server layer<br />
Web Server Layer<br />
Web Server Layer<br />
Application Layer<br />
Application Layer<br />
Application Layer<br />
Application Layer<br />
Database Layer<br />
Database Layer<br />
Database Layer<br />
Database Layer<br />
Attributes<br />
• Name<br />
• Model/Type<br />
• Clusters<br />
• Number of Components<br />
• Vendor<br />
• Server Type (mainframe, Mid range, RISC,<br />
Intel)<br />
• Server logical name<br />
• IP Address etc<br />
Attributes<br />
• Product Name<br />
• Vendor<br />
• OS<br />
• SW components<br />
• License Type<br />
• License Expiry etc<br />
Slide<br />
125<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Platform Decomposition<br />
Diagram<br />
Slide<br />
126<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 63
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Platform Decomposition<br />
Diagram<br />
Slide<br />
127<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Processing Diagram<br />
• The Processing diagram focuses on deployable units of<br />
code/configuration and how these are deployed onto the technology<br />
platform.<br />
• The Processing diagram addresses the following:<br />
– Which set of application components need to be grouped to form a<br />
deployment unit<br />
– How one deployment unit connects/interacts with another (LAN, WAN, and<br />
the applicable protocols)<br />
– How application configuration and usage patterns generate load or capacity<br />
requirements for different technology components<br />
• The organization and grouping of deployment units depends on<br />
separation concerns of the presentation, business logic, and data store<br />
layers and service-level requirements of the components.<br />
Slide<br />
128<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 64
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Example Processing Diagram<br />
Slide<br />
129<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Network Computing Hardware Diagram<br />
• The purpose of this diagram is to show the "as deployed" logical view of<br />
logical application components in a distributed network computing<br />
environment.<br />
• The diagram is useful for the following reasons:<br />
– Enable understanding of which application is deployed where<br />
– Establishing authorization, security, and access to these technology<br />
components<br />
– Understand the Technology Architecture that support the applications during<br />
problem resolution and troubleshooting<br />
– Isolate performance problems encountered and perform necessary upgrade<br />
to specific physical technology components<br />
– Identify areas of optimization<br />
– Enable application/technology auditing and prove compliance<br />
– Serve as an important tool supporting effective change management<br />
Slide<br />
130<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 65
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Example Network Computing Hardware<br />
Diagram<br />
DMZ<br />
Internet Zone<br />
Intranet Zone<br />
Load<br />
Balancer<br />
and<br />
Dispatcher<br />
Web<br />
server<br />
cluster Web<br />
server<br />
cluster<br />
Web<br />
server<br />
clusternode<br />
3<br />
(ABM)<br />
Application<br />
Server cluster<br />
Application (node 3)<br />
Server cluster<br />
(node App Server 3)<br />
cluster - node 3<br />
(ABM)<br />
DFS Distributed File<br />
System (html,<br />
images)<br />
Database<br />
(ABM<br />
Production)<br />
Database<br />
(ABM<br />
Staging)<br />
Load<br />
Balancer<br />
and<br />
Dispatcher<br />
Web server<br />
cluster<br />
Web server<br />
cluster-node<br />
2<br />
(eCommerce<br />
)<br />
Application<br />
Server (Order<br />
Engine)<br />
Database<br />
App<br />
Server<br />
DB<br />
App Server<br />
Slide<br />
131<br />
Firewall Firewall Firewall<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
D<br />
Communications Engineering Diagram<br />
• The Communications Engineering diagram describes the<br />
means of communication between assets in the Technology<br />
Architecture<br />
• It takes logical connections between client and server<br />
components and identifies network boundaries and network<br />
infrastructure required to physically implement those<br />
connections.<br />
• It does not describe the information format or content, but<br />
addresses protocol and capacity issues.<br />
Slide<br />
132<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 66
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
D<br />
Example Communications<br />
Engineering Diagram<br />
OBMG<br />
Proprietary<br />
Protocol<br />
(Encrypted)<br />
Auth Protocol<br />
Auth Protocol<br />
Slide<br />
133<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
E<br />
Opportunities & Solutions<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
<strong>Catalogs</strong><br />
Matrices<br />
<strong>Diagrams</strong><br />
• Project Context diagram<br />
• Benefits diagram<br />
Slide<br />
134<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 67
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
Project Context Diagram<br />
Slide<br />
135<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
Project Context Diagram<br />
Slide<br />
136<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 68
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
E<br />
Benefits Diagram<br />
Slide<br />
137<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
E<br />
Benefits Diagram<br />
Slide<br />
138<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 69
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
R<br />
Requirements Management<br />
<strong>Catalogs</strong>, Matrices and <strong>Diagrams</strong><br />
<strong>Catalogs</strong><br />
• Requirements Catalog<br />
<strong>Diagrams</strong><br />
Matrices<br />
Slide<br />
139<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
R<br />
<strong>Catalogs</strong><br />
Catalog<br />
Requirements<br />
Catalog<br />
Purpose<br />
The Requirements catalog captures things that the enterprise needs to do<br />
to meet its objectives. Requirements generated from architecture<br />
engagements are typically implemented through change initiatives<br />
identified and scoped during Phase E (Opportunities & Solutions).<br />
Requirements can also be used as a quality assurance tool to ensure that<br />
a particular architecture is fit-for-purpose (i.e., can the architecture meet all<br />
identified requirements).<br />
The Requirements catalog contains the following metamodel entities:<br />
* Requirement<br />
* Assumption<br />
* Constraint<br />
* Gap<br />
Slide<br />
140<br />
©2009-2011 The Open Group, All Rights Reserved<br />
Copyright © 2009-2011, The Open Group 70
Personal PDF Edition. For non-commercial use only<br />
<strong>TOGAF</strong> Standard Courseware <strong>V9</strong> Edition<br />
Resources<br />
• A full set of downloadable templates is available<br />
– http://www.opengroup.org/bookstore/catalog/i093.htm<br />
Slide<br />
141<br />
©2009-2011 The Open Group, All Rights Reserved<br />
© 2009-2011 The Open Group, All Rights Reserved<br />
<strong>Sample</strong><br />
<strong>Catalogs</strong>,<br />
Matrices and<br />
<strong>Diagrams</strong><br />
Slide<br />
142<br />
©2009-2011 The Open Group, All Rights Reserved<br />
<strong>TOGAF</strong> is a registered trademark of The<br />
Open Group in the United States and other<br />
countries<br />
Copyright © 2009-2011, The Open Group 71