TOGAF® Standard Courseware V9.

1 Edition

Personal PDF Edition. For non-commercial use only

Sample Catalogs, Matrices and Diagrams
v3: December 2011 Download the template bundle from http://www.opengroup.org/bookstore/catalog/i093.htm
V9.1 Edition Copyright © 2009-2011

All rights Slide 1 reserved

Published by The Open Group,All 2011 ©2009-2011 The Open Group, Rights Reserved

The Open Group gratefully acknowledges the contributions 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

TOGAF® Standard Courseware V9.1 Edition

Personal PDF Edition. For non-commercial use only

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
Preliminary Phase • Principles catalog Requirements Management

TOGAF 9 Artifacts
• Requirements catalog Phase C, Data Architecture • Data Entity/Data Component catalog • Data Entity/Business Function matrix • Application/Data matrix • Logical Data diagram • Data Dissemination diagram • Data Security diagram • Class Hierarchy diagram • Data Migration diagram • Data Lifecycle diagram

Phase A, Architecture Vision • Stakeholder Map Matrix •

Solution Concept diagram

Value Chain 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 C, Application Architecture • Application Portfolio catalog • Interface catalog • Application/Organization matrix • Role/Application matrix • Application/Function matrix • Application Interaction matrix • Application Communication diagram • Application and User Location diagram • Application Use-Case diagram • Enterprise Manageability diagram • Process/Application Realization diagram • Software Engineering diagram • Application Migration diagram • Software Distribution 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

Slide 4 • Benefits diagram

Phase E. Opportunities & Solutions • Project Context diagram
©2009-2011 The Open Group, All Rights Reserved

TOGAF 9 Artifacts

Copyright © 2009-2011, The Open Group

2

TOGAF® Standard Courseware V9.1 Edition

Personal PDF Edition. For non-commercial use only

Phase C
Preliminary Phase – Catalogs, Matrices and Diagrams

TOGAF is a registered trademark of The Open Group in the United States and other countries

Slide 5

©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

P

Preliminary Phase Catalogs, Matrices and Diagrams
Diagrams

Catalogs • Principles Catalog Matrices

Slide 6

©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group

3

All Rights Reserved Phase C Phase A: Architecture Vision – Catalogs. All Rights Reserved Copyright © 2009-2011. For non-commercial use only 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. The Open Group 4 . Matrices and Diagrams TOGAF is a registered trademark of The Open Group in the United States and other countries Slide 8 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9.1 Edition Personal PDF Edition. The Principles catalog contains the following metamodel entities: * Principle Slide 7 ©2009-2011 The Open Group. 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. All Rights Reserved © 2009-2011 The Open Group.

All Rights Reserved Stakeholder Map Stakeholder CxO Key Concerns The high-level drivers. and how these are translated into an effective process and IT architecture to advance the business Prioritizing. applications. For non-commercial use only A Architecture Vision Catalogs.TOGAF® Standard Courseware V9. funding. An understanding of project content and technical dependencies adds a further dimension of richness to portfolio management and decision making. HR are important stakeholders in ensuring that the correct roles and actors are represented. The Open Group 5 . and technology of the organization. and aligning change activity. Class Keep Satisfied Catalogs.1 Edition Personal PDF Edition. Matrices and Diagrams Diagrams • Value Chain Diagram • Solution Concept Diagram Catalogs Matrices • Stakeholder Map Matrix Slide 9 ©2009-2011 The Open Group. Keep Informed Slide 10 ©2009-2011 The Open Group. goals and objectives of the organization. Matrices and Diagrams Business Footprint diagram Goal/Objective/Service diagram Organization Decomposition diagram Project Context diagram Business Footprint diagram Application Communication diagram Functional Decomposition diagram Organization Decomposition diagram Organization/Actor catalog Location catalog Program Management Office Keep Satisfied HR The roles and Actors that support the functions. All Rights Reserved Copyright © 2009-2011. All Rights Reserved © 2009-2011 The Open Group.

All Rights Reserved © 2009-2011 The Open Group.TOGAF® Standard Courseware V9. For non-commercial use only Value Chain Diagram Source: Wikipedia.1 Edition Personal PDF Edition. All Rights Reserved Example Value Chain Diagrams Product & Offer Sales Fulfilment Payments Servicing Slide 12 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.org Slide 11 ©2009-2011 The Open Group. The Open Group 6 .

All Rights Reserved Example Solution Concept Diagrams Today’s use of channels Tomorrow’s use of channels High Value Tasks RM RM From RM to ST SERVICE TEAM SERVICE TEAM From Service Team to CC From RM to CC CALL CENTER CALL CENTER From Call Centre to Online From Service Team to Online From RM to Online SELF SERVICE INTERNET PORTAL SELF SERVICE INTERNET PORTAL Low Value Tasks Slide 14 ©2009-2011 The Open Group. The Open Group 7 .TOGAF® Standard Courseware V9. For non-commercial use only 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. 24x7. All Rights Reserved © 2009-2011 The Open Group. join.1 Edition Personal PDF Edition. re-new Certification Publication Reliable. All Rights Reserved Copyright © 2009-2011. self-service infrastructure Slide 13 ©2009-2011 The Open Group.

Matrices and Diagrams TOGAF is a registered trademark of The Open Group in the United States and other countries Slide 15 ©2009-2011 The Open Group. All Rights Reserved B Catalogs. For non-commercial use only Phase C Phase B: Business Architecture – Catalogs. The Open Group 8 . All Rights Reserved Copyright © 2009-2011. Matrices and Diagrams Diagrams • Business Footprint diagram • Business Service/Information diagram • Functional Decomposition diagram • Product Lifecycle diagram • Goal/Objective/Service diagram • Use-Case diagram • Organization Decomposition diagram • Process Flow diagram • Event diagram 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 Slide 16 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9. All Rights Reserved © 2009-2011 The Open Group.1 Edition Personal PDF Edition.

Business Function. Measure (may optionally be included) The purpose of the Role catalog is to provide a listing of all authorization levels or zones within an enterprise. It contains the following metamodel entities: •Location The Process/Event/Control/Product catalog provides a hierarchy of processes. It contains the following metamodel entities: •Organization Unit. application security or behavior is defined against locally understood concepts of authorization that create complex and unexpected consequences when combined on the user desktop. or impact. All Rights Reserved Copyright © 2009-2011.TOGAF® Standard Courseware V9. Business Service. reported on. such as data centers or end-user computing equipment. and query across organizations and processes to identify scope. and controls applied to the execution of processes. Goal. It contains the following metamodel entities: •Process. Information System Service (may optionally be included here) A listing of all locations where an enterprise carries out business operations or houses architecturally relevant assets. All Rights Reserved © 2009-2011 The Open Group. Driver. Product ©2009-2011 The Open Group. commonality. This catalog provides a supplement to any Process Flow diagrams that are created and allows an enterprise to filter. It contains the following metamodel entities: •Organization Unit. as a supplement to graphical Functional Decomposition diagrams. outputs from processes.1 Edition Personal PDF Edition. and (optionally) measures. All Rights Reserved Catalogs Catalog Business Service / Function Catalog Location Catalog Process/ Event/ Control/ Product Catalog Slide 18 Purpose A functional decomposition in a form that can be filtered. For non-commercial use only Catalogs Catalog Organization/ Actor Catalog Driver/Goal/ Objective Catalog Role Catalog Purpose A definitive listing of all participants that interact with IT. It contains the following metamodel entities: •Role Slide 17 ©2009-2011 The Open Group. Control. including users and owners of IT systems. Objective. report. and queried. It contains the following metamodel entities: •Organization Unit. The Open Group 9 . Event. events that trigger processes. Frequently. Actor Location (may be included in this catalog if an independent Location catalog is not maintained) A cross-organizational reference of how an organization meets its drivers in practical terms through goals. objectives.

TOGAF® Standard Courseware V9. All Rights Reserved Matrices • Business Interaction matrix • Actor/Role matrix Slide 20 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. All Rights Reserved © 2009-2011 The Open Group. For non-commercial use only Catalogs Catalog Contract/ Measure Catalog Purpose A listing of all agreed service contracts and (optionally) the measures attached to those contracts. The Open Group 10 . It contains the following metamodel entities: •Business Service •Information System Service (optionally) •Contract •Measure Slide 19 ©2009-2011 The Open Group.1 Edition Personal PDF Edition. It forms the master list of service levels agreed to across the enterprise.

supporting definition of security and skills requirements.TOGAF® Standard Courseware V9. All Rights Reserved Copyright © 2009-2011. All Rights Reserved Actor/role Matrix • This matrix show which actors perform which roles. Office of CIO Actors Steering Group Actors Business Unit Actors Strategy and Architecture Actors Enterprise Infrastructure Architect Infrastructure Implementation Actors Business Unit Application Architect Head of Strategy and Architecture Infrastructure Solution Architect Architecture Configuration Mgr Business Unit Service Owner Enterprise Design Authority Technical Design Authority Head of Implementation Infrastructure Strategist Infrastructure Designer IT Management Forum Enterprise Architect Business Unit Head 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 I I I R C I C C I A A I C I I I I I C A A A A C C R I A C I I I I C C I I C I I I I R C I I I C C C C C I I C C C C C C C I R A I I I I I C R I I I I I I I I I I R I I R R R R R I I I I I I I I R R R R R R C C C C R I C I R C IT Operations C C C C C C C C C Project Manager I A I R R R C A CIO I C R R Slide 22 ©2009-2011 The Open Group. Providing Business Services Consuming Business Services Engineering Procurement Manufacturing Contract for supply of product specification Contract for supply of materials Contract for supply of product Contract for fulfillment of customer orders Contract for supply of sales forecasts Engineering Procurement Manufacturing Sales and Distribution Customer Service Sales and Distribution Customer Service Slide 21 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group. For non-commercial use only Business Interaction Matrix • The purpose of this matrix is to depict the relationship interactions between organizations and business functions across the enterprise.1 Edition Personal PDF Edition. The Open Group External Vendors / Suppliers C C 11 .

and services. All Rights Reserved Business Footprint Diagram • Describes the links between business goals. organizational units. For non-commercial use only Diagrams • • • • • • • • • Business Footprint diagram Business Service/Information diagram Functional Decomposition diagram Product Lifecycle diagram Goal/Objective/Service diagram Use-Case diagram Organization Decomposition diagram Process Flow diagram Event diagram Slide 23 ©2009-2011 The Open Group. business functions.TOGAF® Standard Courseware V9. and maps these functions to the technical components delivering the required capability.1 Edition Personal PDF Edition. • Demonstrates only the key facts linking organization unit functions to delivery services and is utilized as a communication platform for senior-level (CxO) stakeholders Slide 24 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group. The Open Group 12 . All Rights Reserved Copyright © 2009-2011.

For non-commercial use only Example Business Footprint Diagram Slide 25 ©2009-2011 The Open Group. The Open Group 13 .TOGAF® Standard Courseware V9. • 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).1 Edition Personal PDF Edition. All Rights Reserved Business Service/Information Diagram • Shows the information needed to support one or more business services. • Shows what data is consumed by or produced by a business service and may also show the source of information. All Rights Reserved © 2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. Slide 26 ©2009-2011 The Open Group.

All Rights Reserved © 2009-2011 The Open Group. For non-commercial use only Example Business Service/Information Diagram Basic example Slide 27 ©2009-2011 The Open Group. All Rights Reserved Example Business Service/Information Diagram Complaint Complaint Handling Service Customer Details Customer Complaint Resolution Common Faults Fault Management Service Customer Details Lead Management Service Extended example showing actors and service interactions Slide 28 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. The Open Group 14 .TOGAF® Standard Courseware V9.1 Edition Personal PDF Edition.

All Rights Reserved Copyright © 2009-2011. The Open Group 15 .TOGAF® Standard Courseware V9. • By examining the capabilities of an organization from a functional perspective. All Rights Reserved © 2009-2011 The Open Group. Slide 29 ©2009-2011 The Open Group. All Rights Reserved Example Functional Decomposition Diagram Slide 30 ©2009-2011 The Open Group. it is possible to quickly develop models of what the organization does without being dragged into extended debate on how the organization does it.1 Edition Personal PDF Edition. For non-commercial use only Functional Decomposition Diagram • It shows on a single page the capabilities of an organization that are relevant to the consideration of an architecture.

legislation.1 Edition Personal PDF Edition. user identity credentials (identity cards. All Rights Reserved © 2009-2011 The Open Group. passports. store/loyalty cards. debit cards. and regulation where products must be tracked from manufacture to disposal.). etc. All Rights Reserved Copyright © 2009-2011. and procedures. For non-commercial use only 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. Slide 31 ©2009-2011 The Open Group. processes. smart cards. • Equally. The Open Group 16 . 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.TOGAF® Standard Courseware V9. Examples of this include credit cards. All Rights Reserved Example Product Lifecycle Diagram Slide 32 ©2009-2011 The Open Group.

The Open Group 17 . and measures that they support. objectives. All Rights Reserved © 2009-2011 The Open Group. 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.1 Edition Personal PDF Edition. For non-commercial use only Goal/Objective/Service Diagram • This defines the ways in which a service contributes to the achievement of a business vision or strategy.TOGAF® Standard Courseware V9. Slide 33 ©2009-2011 The Open Group. • Services are associated with the drivers. goals. All Rights Reserved Copyright © 2009-2011. All Rights Reserved Example Goal/Objective/Service Diagram Goal:Increase Revenues Role:CFO Role: VP Marketing Objective: After Sales Market Role: VP Sales Objective: Creating new line of cars by end of… Function: Sales and Marketing Service: Marketing Service: Preowned vehiclesService: Campaign Service: Sales Service: Pre-Sales Service: Order To Delivery Slide 34 ©2009-2011 The Open Group.

All Rights Reserved Copyright © 2009-2011. Slide 35 ©2009-2011 The Open Group. and technology details.TOGAF® Standard Courseware V9. All Rights Reserved © 2009-2011 The Open Group. Architectural business use-cases can also be re-used in systems design work. For non-commercial use only Business Use-case Diagram • This displays the relationships between consumers and providers of business services. application. The Open Group 18 . All Rights Reserved Example Business Use-case Diagram Slide 36 ©2009-2011 The Open Group.1 Edition Personal PDF Edition. • 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. the use-case can evolve from the business level to include data. • As the architecture progresses. • They help to describe and validate the interaction between actors and their roles to processes and functions.

All Rights Reserved © 2009-2011 The Open Group. All Rights Reserved Example Organization Decomposition Diagram Slide 38 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. For non-commercial use only Organization Decomposition Diagram • This describes the links between actor.1 Edition Personal PDF Edition. The Open Group 19 . and location within an organization tree. Slide 37 ©2009-2011 The Open Group. • An organization map should provide a chain of command of owners and decision-makers in the organization.TOGAF® Standard Courseware V9. roles.

All Rights Reserved Example Process Flow Diagram Start Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 6 Step 6 STOP Slide 40 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.TOGAF® Standard Courseware V9.1 Edition Personal PDF Edition. • It shows sequential flow of control between activities and may utilize swim-lane techniques to represent ownership and realization of process steps. the events that trigger or result from completion of a process. • In addition to showing a sequence of activity. process flows can also be used to detail the controls that apply to a process. and also the products that are generated from process execution. Slide 39 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group. The Open Group 20 . For non-commercial use only Process Flow Diagram • This depicts all models and mappings related to the process metamodel entity.

For non-commercial use only Example Process Flow Diagram Technical Support Team Sales Rep Pricer Pricer Start Step 1 Step 2 Step 3 Step 4 Custom app Email CRM MS Word MS Excel Custom Bid Approver Customer Rep Customer Rep Customer Rep Step 5 Step 6 Step 6 Step 6 STOP IWF email Consolidation Tool Spreadsheet Process Flow (w/Roles & Applications) Slide 41 ©2009-2011 The Open Group. All Rights Reserved Events Diagram • This depicts the relationship between events and process.1 Edition Personal PDF Edition. end of fiscal quarter) cause work and actions to be undertaken within the business. Slide 42 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.g.g.TOGAF® Standard Courseware V9. The Open Group 21 .such as arrival of information (e. All Rights Reserved © 2009-2011 The Open Group. a customer’s sales order) or a point in time (e. • Certain events .

1 Edition Personal PDF Edition. End of Fiscal Quarter) Triggers Impacts/Generates Process Business result (e. For non-commercial use only Example Events Diagram Event (e. All Rights Reserved © 2009-2011 The Open Group. Financial Reporting Process) Slide 43 ©2009-2011 The Open Group.g.TOGAF® Standard Courseware V9. 1Q results reported to Government Agencies) (e.g. All Rights Reserved Copyright © 2009-2011. All Rights Reserved Example Events Matrix EVENT Customer submits sales order PROCESS TRIGGERED Sales order processing ƒ Create & save sales order ƒ Generate acknowledgement ƒ Confirm receipt of customer order ƒ Begin order fulfillment activities Custom product configuration ƒ Capture requirements from customer ƒ Define custom specifications ƒ Price custom configuration ƒ Negotiate with customer ƒ Secure approval from customer regarding configuration and price Financial reporting process ƒ BUSINESS RESULT(S) Sales order captured in order book Customer submits request for custom product ƒ ƒ Custom product configured Customer contract signed End of quarter ƒ Financial report generated Slide 44 ©2009-2011 The Open Group. The Open Group 22 .g.

For non-commercial use only Phase C Phase C: Data Architecture – Catalogs. The Open Group 23 .1 Edition Personal PDF Edition.TOGAF® Standard Courseware V9. Matrices and Diagrams Diagrams • Class diagram • Data Dissemination diagram • Data Security diagram • Class Hierarchy diagram • Data Migration diagram • Data Lifecycle diagram Catalogs • Data Entity/Data Component catalog Matrices • Data Entity/Business Function matrix • System/Data matrix Slide 46 ©2009-2011 The Open Group. All Rights Reserved C Catalogs. All Rights Reserved Copyright © 2009-2011. Matrices and Diagrams TOGAF is a registered trademark of The Open Group in the United States and other countries Slide 45 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group.

1 Edition Personal PDF Edition. For non-commercial use only Catalogs Catalog •Data Entity/Data Component Catalog Purpose To identify and maintain a list of all the data use across the enterprise.TOGAF® Standard Courseware V9. including data entities and also the data components where data entities are stored. The Open Group 24 . All Rights Reserved © 2009-2011 The Open Group. It contains the following metamodel entities: •Data Entity •Logical Data Component •Physical Data Component Slide 47 ©2009-2011 The Open Group. All Rights Reserved Matrices • Data Entity/Business Function matrix • Application/Data matrix Slide 48 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.

1 Edition Personal PDF Edition.) Slide 49 ©2009-2011 The Open Group. All Rights Reserved Example Data Entity/Business Function Matrix BUSINESS FUNCTION (Y-AXIS) / DATA ENTITY (XAXIS) Customer Relationship Management ƒ ƒ ƒ CUSTOMER MASTER BUSINESS PARTNER CUSTOMER LEADS PRODUCT MASTER Business partner data management service Owner – Sales & Marketing business unit executive Function can Create.TOGAF® Standard Courseware V9. update customer leads N/A ƒ N/A Supply Chain Management ƒ ƒ Customer Requirement Processing Service Owner – Supply Chain Manager ƒ ƒ ƒ ƒ Product data management service Owner – Global product development organization Slide 50 ©2009-2011 The Open Group. update and delete N/A ƒ ƒ ƒ Lead Processing Service Owner – Customer Relationship Manager Function can only Create. update and delete customer master data ƒ ƒ ƒ Business partner data management service Owner of data entity (person or organization) Function can Create. and system of reference for data entities – Enable development of data governance programs across the enterprise (establish data steward. All Rights Reserved Copyright © 2009-2011. develop data standards pertinent to the business function. etc. • 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. read. For non-commercial use only 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. All Rights Reserved © 2009-2011 The Open Group. read. read. The Open Group 25 . system of record.

All Rights Reserved © 2009-2011 The Open Group. read. update. • Applications will create. The Open Group 26 . All sales orders by customer XYZ and by month for 2006) ƒHistorical data Slide 52 ©2009-2011 The Open Group. All Rights Reserved Example Application/Data Matrix APPLICATION (YAXIS) AND DATA (XAXIS) 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 Rights Reserved Copyright © 2009-2011. a CRM application will create. – For example. read. and delete customer entity information. For non-commercial use only Application/Data Matrix • The purpose of the Application/Data matrix is to depict the relationship between applications and the data entities that are accessed and updated by them.TOGAF® Standard Courseware V9. update.1 Edition Personal PDF Edition. and delete specific data entities that are associated with them. Slide 51 ©2009-2011 The Open Group.

Account I.C1 Slide 54 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.A1 Information Customer Profile I.C2 Customer Information I. All Rights Reserved Conceptual Data Diagram • The purpose is to depict the relationships among the critical data entities (or classes) within the enterprise.TOGAF® Standard Courseware V9. All Rights Reserved © 2009-2011 The Open Group.A12 Enquiry T.CS13 Payment T. For non-commercial use only Diagrams • • • • • • Conceptual Data diagram Logical Data diagram Data Dissemination diagram Data Security diagram Data Migration diagram Data Lifecycle diagram Slide 53 ©2009-2011 The Open Group.C1 Appeal T.A4 Customer A.C19 Complaint T. The Open Group 27 .C16 P.C2 Contact P.P8 Agent A.1 Edition Personal PDF Edition.CS5 Service Request Actor Trigger Process Update Account P.

1 Edition Personal PDF Edition. All Rights Reserved Copyright © 2009-2011. All Rights Reserved Data Dissemination Diagram • The purpose of the Data Dissemination diagram is to show the relationship between – data entity – business service – application components • The diagram should show how the logical entities are to be physically realized by application components. the diagram may show data replication and system ownership of the master reference for data. • Additionally. For non-commercial use only Logical Data Diagram • The purpose is to depict logical views relationships among the critical data entities (or classes) within the enterprise. The Open Group 28 . • The audience is – Application developers – Database designers Slide 55 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9. Slide 56 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group.

1 Edition Personal PDF Edition. All Rights Reserved Copyright © 2009-2011. All Rights Reserved © 2009-2011 The Open Group.TOGAF® Standard Courseware V9. All Rights Reserved 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. For non-commercial use only Example Data Dissemination Diagram Warehouse Warehouse Customer Order History Stock Online Account Online Account Self Service Self Service Billing Billing Customer Account Balance Invoice History Business Service Online Account Self Service Data Entities Customer Order History Stock Account Balance Invoice History Application ƒWarehouse ƒBilling ƒWarehouse ƒWarehouse ƒBilling ƒBilling Slide 57 ©2009-2011 The Open Group. The Open Group 29 . Fulfilment Order New Fulfilled Invoiced Paid Closed Archived Deleted Customer Order New Dispatched Closed Archived Deleted Slide 58 ©2009-2011 The Open Group.

All Rights Reserved Example Data Security Diagram Class of Roles (by job function) Actor Business Function Process Physical Access Single . For non-commercial use only Data Security Diagram • The purpose of the Data Security diagram is to depict which actor (person. organization. • This relationship can also be shown in a matrix form between two objects or can be shown as a mapping.1 Edition Personal PDF Edition. or system) can access which enterprise data. All Rights Reserved Copyright © 2009-2011. The Open Group 30 . All Rights Reserved © 2009-2011 The Open Group.Sign On or Access Control Location Business Service Access Control (levels of Granularity) Access Control (levels of Granularity) Logical Application Component Slide 60 ©2009-2011 The Open Group. Slide 59 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9.

Slide 62 ©2009-2011 The Open Group. For non-commercial use only Example Data Security Matrix ACTOR Financial Analyst CLASS OF ROLES (JOB FUNCTION) SOA Portfolio Financial Analyst FUNCTION Financial Analysis BUSINESS SERVICE SOA portfolio service ƒ ƒ ƒ Procurement & Spend Analyst Procurement Management and Control Not applicable WW Direct Procurement Supplier portal Service ƒ LOCATION NA (US. All Rights Reserved 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 Open Group 31 .1 Edition Personal PDF Edition.TOGAF® Standard Courseware V9. • The diagram will provide a visual representation of the spread of sources/targets and serve as a tool for data auditing and establishing traceability. DE) APJ NA (US Midwest) ƒ ƒ TYPE OF ACCESS Physical Access Control (tables xyz only) Access control ƒ WW Contracts System (application) WW Product Development (Org Unit) WW Direct Procurement Supplier Portal Service ƒ LA ƒ Access control (system to system) Access Control Geo Brand Managers WW Direct Procurement Supplier Portal Service ƒ WW (all Geos) ƒ Slide 61 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. CA) EMEA (UK.

All Rights Reserved Copyright © 2009-2011.TOGAF® Standard Courseware V9. For non-commercial use only Example Data Migration Diagram “Baseline” application components ABM Source of Customer records Data migration technology components “Target” application components CRM System of Record for Customer Master CCB BDW Source of order history ERP System of Record for Material Master & Order history MRPA Source of Material data Source Staging Transformation & Data Quality Target Staging SRM System of Record for Vendor Master & Contracts VLC (one per geo) Source of vendor data Slide 63 ©2009-2011 The Open Group. All Rights Reserved Example Data Migration Mapping SOURCE LOGICAL APPLICATION COMPONENT SOURCE DATA ELEMENT TARGET LOGICAL APPLICATION COMPONENT TARGET DATA ELEMENT ABM Cust_Name Cust_Street_Addr Cust_Street_Addr Cust_Street_Addr Cust_ContactName Cust_Tele CRM CUSTNAME CUSTADDR_LINE1 CUSTADDR_LINE2 CUSTADDR_LINE3 CUSTCONTACT CUSTTELEPHONE Slide 64 ©2009-2011 The Open Group. The Open Group 32 . All Rights Reserved © 2009-2011 The Open Group.1 Edition Personal PDF Edition.

All Rights Reserved C Catalogs.1 Edition Personal PDF Edition. Matrices and Diagrams Application Architecture TOGAF is a registered trademark of The Open Group in the United States and other countries Slide 65 ©2009-2011 The Open Group. Matrices and Diagrams Diagrams • Application Communication diagram • Application and User Location diagram • Application Use-Case diagram • Enterprise Manageability diagram • Process/Application Realization diagram • Software Engineering diagram • Application Migration diagram • Software Distribution diagram Catalogs • Application Portfolio catalog • Interface catalog Matrices • Application/Organization matrix • Role/Application matrix • Application/Function matrix • Application Interaction matrix Slide 66 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group. The Open Group 33 .TOGAF® Standard Courseware V9. All Rights Reserved Copyright © 2009-2011. For non-commercial use only Phase C Phase C: Application Architecture – Catalogs.

For non-commercial use only 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. All Rights Reserved Matrices • • • • Application/Organization matrix Role/Application matrix Application/Function matrix Application Interaction matrix Slide 68 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group. An agreed Application Portfolio allows a standard set of applications to be defined and governed.TOGAF® Standard Courseware V9. It contains the following metamodel entities: •Logical Application Component •Physical Application Component •Application communicates with application relationship Slide 67 ©2009-2011 The Open Group.1 Edition Personal PDF Edition. All Rights Reserved Copyright © 2009-2011. The Open Group 34 . 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.

For non-commercial use only Application/Organization Matrix • The purpose of this matrix is to depict the relationship between applications and organizational units within the enterprise.TOGAF® Standard Courseware V9. The Open Group 35 . All Rights Reserved © 2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. • The mapping of the Application Component-Organization Unit relationship is an important step as it enables the following to take place: – Assign usage of applications to the organization units that perform business functions – Understand the application support requirements of the business services and processes carried out by an organization unit – Support the gap analysis and determine whether any of the applications are missing and as a result need to be created – Define the application set used by a particular organization unit Slide 69 ©2009-2011 The Open Group.1 Edition Personal PDF Edition. All Rights Reserved Example Application/Organization Matrix APPLICATION (Y-AXIS) AND ORGANISATION UNIT (X-AXIS) CUSTOMER SERVICES PROCUREMENT AND WAREHOUSING HR CORPORATE FINANCE SAP HR X X X SIEBEL X X SAP FINANCIALS PROCURESOFT X X X X X Slide 70 ©2009-2011 The Open Group.

1 Edition Personal PDF Edition. 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. • 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. essential in any move to role-based computing Slide 71 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group. The Open Group 36 .TOGAF® Standard Courseware V9. All Rights Reserved Example Role/Application Matrix APPLICATION (YAXIS) AND FUNCTION (XAXIS) CALL CENTRE OPERATOR CALL CENTRE MANAGER FINANCE ANALYST CHIEF ACCOUNTANT SAP HR SIEBEL X X X X X X SAP FINANCIALS PROCURESOFT X X X X X X Slide 72 ©2009-2011 The Open Group. For non-commercial use only Role/Application Matrix • The purpose of this matrix is to depict the relationship between applications and the business roles that use them within the enterprise. All Rights Reserved Copyright © 2009-2011.

TOGAF® Standard Courseware V9. The Open Group 37 .1 Edition Personal PDF Edition. For non-commercial use only Application/Function Matrix • The purpose of this matrix is to depict the relationship between applications and business functions within the enterprise. All Rights Reserved Copyright © 2009-2011. All Rights Reserved © 2009-2011 The Open Group. All Rights Reserved Example Application/Function Matrix APPLICATION (YAXIS) AND FUNCTION (XAXIS) CALL CENTRE 1ST LINE WAREHOUSE CONTROL VACANCY FILLING GENERAL LEDGER MAINTENANCE SAP HR SIEBEL X X X X X X SAP FINANCIALS PROCURESOFT X X X X X Slide 74 ©2009-2011 The Open Group. • The mapping of the Application Component-Function relationship is an important step as it enables the following to take place: – Assign usage of applications to the business functions that are supported by them – Understand the application support requirements of the business services and processes carried out – Support the gap analysis and determine whether any of the applications are missing and as a result need to be created – Define the application set used by a particular business function Slide 73 ©2009-2011 The Open Group.

The Open Group 38 . • Communication should be logical and should only show intermediary technology where it is architecturally relevant.1 Edition Personal PDF Edition. All Rights Reserved Copyright © 2009-2011. • It shows application components and interfaces between components. All Rights Reserved © 2009-2011 The Open Group. For non-commercial use only Diagrams • • • • • • • • • Application Communication diagram N2 model or Node Connectivity diagram Application and User Location diagram System Use-Case diagram Enterprise Manageability diagram Process/Application Realization diagram Software Engineering diagram Application Migration diagram Software Distribution diagram Slide 75 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9. All Rights Reserved Application Communication Diagram • The purpose of this diagram is to depict all models and mappings related to communication between applications in the metamodel entity. Slide 76 ©2009-2011 The Open Group.

TOGAF® Standard Courseware V9.1 Edition

Personal PDF Edition. For non-commercial use only

Application Communication Diagram

Slide 77

©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

N2 Model
ABC
1a 1c

1b

ABM

2a 3c

CCD

3a

4a 3b 1d 4b 3d

CRM IPC

Slide 78

©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group

39

TOGAF® Standard Courseware V9.1 Edition

Personal PDF Edition. For non-commercial use only

Information Exchange Matrix
LABEL SOURCE DESTINATION DATA ENTITY EVENT TRIGGERED

1a

ƒ

ABC

ƒ

ABM

ƒ

Sales order (create request) Sales order (confirm create) Product catalog

ƒ

New sales order from front end Order created in the backend ERP system Subscribe/ Publish timer

1b

ƒ

ABM

ƒ

ABC

ƒ

ƒ

2a

ƒ

ABM

ƒ

CCD

ƒ

ƒ

Slide 79

©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

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

©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group

40

TOGAF® Standard Courseware V9.1 Edition

Personal PDF Edition. For non-commercial use only

Example 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 Headquarter s, UK SAP R/3 Test Engineers Mechanical Engineers Procurement managers Internal Beijing Manufacturin g Plant LOCATION ADDRESS Chicago Sears tower office Chicago Downtown office Middlesex, London ORG UNIT (USER
BELONGS TO)

NA Sales & Marketing EMEA Sales

Manufacturing & logistics

Slide 81

©2009-2011 The Open Group, All Rights Reserved

© 2009-2011 The Open Group, All Rights Reserved

Example Application & User Location Diagram (part 2)

Slide 82

©2009-2011 The Open Group, All Rights Reserved

Copyright © 2009-2011, The Open Group

41

Slide 84 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9. All Rights Reserved Copyright © 2009-2011.1 Edition Personal PDF Edition. All Rights Reserved 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. For non-commercial use only Application Use Case Diagram Source: wikipedia.org Slide 83 ©2009-2011 The Open Group. and opportunities in the IT service management operation of an organization. The Open Group 42 . All Rights Reserved © 2009-2011 The Open Group.

For non-commercial use only Example Enterprise Manageability Diagram Slide 85 ©2009-2011 The Open Group. Slide 86 ©2009-2011 The Open Group. The Open Group 43 .1 Edition Personal PDF Edition. All Rights Reserved Process/Application Realization Diagram • The purpose of this diagram is to depict the sequence of events when multiple applications are involved in executing a business process. • It enhances the Application Communication diagram by augmenting it with any sequencing constraints. All Rights Reserved © 2009-2011 The Open Group. and handoff points between batch and real-time processing. All Rights Reserved Copyright © 2009-2011.TOGAF® Standard Courseware V9.

and operations from a development perspective. Slide 88 ©2009-2011 The Open Group. For non-commercial use only Example Process/Application Realization Diagram Slide 87 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. All Rights Reserved Software Engineering Diagram • The Software Engineering diagram breaks applications into packages. and analyzing opportunities and solutions. The Open Group 44 . modules.1 Edition Personal PDF Edition. • It enables more detailed impact analysis when planning migration stages.TOGAF® Standard Courseware V9. All Rights Reserved © 2009-2011 The Open Group. services. • It is ideal for application development teams and application management teams when managing complex development environments.

and the infrastructure required to support migrations Slide 90 ©2009-2011 The Open Group. staging areas.1 Edition Personal PDF Edition.TOGAF® Standard Courseware V9. All Rights Reserved © 2009-2011 The Open Group. • It enables a more accurate estimation of migration costs • It should be used to identify temporary applications. For non-commercial use only Example Software Engineering Diagram Slide 89 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. All Rights Reserved Application/Migration Diagram • The Application Migration diagram identifies application migration from baseline to target application components. The Open Group 45 .

The Open Group 46 . All Rights Reserved Software Distribution Diagram • This diagram is a composite of the Software Engineering diagram and the Application-User Location diagram. or may not be needed. For non-commercial use only Example Application/Migration Diagram Slide 91 ©2009-2011 The Open Group.1 Edition Personal PDF Edition.TOGAF® Standard Courseware V9. All Rights Reserved © 2009-2011 The Open Group. • Depending on the circumstances. Slide 92 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. this diagram alone may be sufficient.

1 Edition Personal PDF Edition. Matrices and Diagrams Diagrams • Environments and Locations diagram • Platform Decomposition diagram • Processing diagram • Networked Computing/Hardware diagram • Communications Engineering diagram Catalogs • Technology Standards catalog • Technology Portfolio catalog • Matrices • Application/Technology matrix Slide 94 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011. For non-commercial use only Phase C Phase D: Technology Architecture – Catalogs. All Rights Reserved D Catalogs. All Rights Reserved © 2009-2011 The Open Group.TOGAF® Standard Courseware V9. Matrices and Diagrams TOGAF is a registered trademark of The Open Group in the United States and other countries Slide 93 ©2009-2011 The Open Group. The Open Group 47 .

infrastructure software. Physical Technology Component Technology Portfolio Catalog This catalog identifies and list all the technology in use across the enterprise.1 Edition Personal PDF Edition. and versions. 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. the technology lifecycles. All Rights Reserved © 2009-2011 The Open Group. The Open Group 48 . All Rights Reserved Copyright © 2009-2011. Logical Technology Component. All Rights Reserved Catalogs Catalog Technology Standards Catalog Purpose This documents the agreed standards for technology across the enterprise covering technologies. and the refresh cycles for the technology. and application software. Logical Technology Component. Physical Technology Component Slide 96 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9. including hardware. For non-commercial use only Catalogs • Technology Standards catalog • Technology Portfolio catalog Slide 95 ©2009-2011 The Open Group. It can be implemented as an extension to the Technology Portfolio Catalog and thus will share the same metamodel entities: •Platform Service.

All Rights Reserved Application/Technology Matrix • The Application/Technology matrix documents the mapping of applications to the technology platform. All Rights Reserved © 2009-2011 The Open Group. Logical Technology Components. • The Application/Technology matrix shows: – Logical/Physical Application Components – Services.TOGAF® Standard Courseware V9.1 Edition Personal PDF Edition. The Open Group 49 . For non-commercial use only Matrices • Application/Technology matrix Slide 97 ©2009-2011 The Open Group. and Physical Technology Components – Physical Technology Component realizes Physical Application Component relationships Slide 98 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.

com 10.node 3 App server – node 1 App server – node 2 App server – node 3 Database server (production) Database server (stating) Load balancer and Dispatcher Dispatcher server SERVER ADDRESS F01ws001@host. All Rights Reserved © 2009-2011 The Open Group.xx.IBM Load balance manager ƒVendor .xx 242.xx.com F02as001@host.com F01ws002@host.40 GB ƒIP .xx.node 2 Web server .xx.TOGAF® Standard Courseware V9.xx 10.2 (list all the other components of the SW product) ƒAIX 10.xx 10.node 1 Web server .xx 10.xx IP ADDRESS Slide 99 ©2009-2011 The Open Group.xx.xx.xx. The Open Group 50 .xx 10. For non-commercial use only Example Application/Technology Matrix LOGICAL APPLICATION COMPONENT ABM PHYSICAL TECHNOLOGY COMPONENT Web server .1 ƒLicense Type ƒEnterprise wide license ƒLicense expiry date .xx.com F01ws003@host.xx 10.xx.xx.xx.xx 10. All Rights Reserved Copyright © 2009-2011.xx.11.com F03dbs001@host.xx SOFTWARE LOGICAL ƒProduct.com F03nd001@host.com F02dbp001@host.xx.8 way ƒMemory .com F02as002@host.xx.1GB ƒHard drive .xx.1 Edition Personal PDF Edition.IBM ƒOS – UNIX SOFTWARE PHYSICAL ƒSW Components – LB v3.com F02as003@host.xx.12/31/2014 Slide 100 ©2009-2011 The Open Group.xx.IBM ƒServer Type – eServer ƒClustered – No ƒNo.xx. All Rights Reserved Example Application/Technology Matrix TECH FUNCTION Load balancing HARDWARE LOGICAL ƒName – Balancer ƒVendor . of Nodes – N/A ƒServer logical address d04lb01@host.xx.xx 10.com ƒMaintenance Window – Sun 0100 to 0300 HARDWARE PHYSICAL ƒModel/Type – IBM P7xx ƒSerial Number – 1S4568 ƒProcessor Type RISC Power p5 ƒNumber of Processors .xx.2.

2 (both installation and execution code) ƒHTML code ƒApplets ƒJSP TECHNOLOGY COMPONENT ƒLoad balancing server (d03lb001@host. d03ws003@host.com) •Application Server (d03as001@host. All Rights Reserved Copyright © 2009-2011. d03as002@host. For non-commercial use only Example System/Technology Matrix APPLICATION COMPONENT ƒLoad Balancer DEPLOYMENT UNIT ƒSmart dispatch v1.TOGAF® Standard Courseware V9. All Rights Reserved Diagrams • • • • • Environments and Locations diagram Platform Decomposition diagram Processing diagram Networked Computing/Hardware diagram Communications Engineering diagram Slide 102 ©2009-2011 The Open Group.com) ƒCommerce pages ƒCommerce Engine •Order Entry (both installation and execution code) •Shopping Cart (both installation and execution code) Slide 101 ©2009-2011 The Open Group. d03ws002@host. All Rights Reserved © 2009-2011 The Open Group.com.com.com) ƒWeb Server cluster (d03ws001@host. The Open Group 51 .1 Edition Personal PDF Edition.com.

TOGAF® Standard Courseware V9. The Open Group 52 . All Rights Reserved © 2009-2011 The Open Group. All Rights Reserved Example Environments and Locations Diagram Slide 104 ©2009-2011 The Open Group. Slide 103 ©2009-2011 The Open Group. such as development and pre production. For non-commercial use only Environments and Locations Diagram • Depicts which locations host which applications • Identifies what technologies and/or applications are used at which locations • Identifies the locations from which business users typically interact with the applications. All Rights Reserved Copyright © 2009-2011. • It should also show the existence and location of different deployment environments – including non-production environments.1 Edition Personal PDF Edition.

RISC. Intel) Server logical name IP Address etc Attributes ƒ ƒ ƒ ƒ ƒ ƒ Product Name Vendor OS SW components License Type License Expiry etc Slide 106 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.TOGAF® Standard Courseware V9. • The diagram covers all aspects of the infrastructure platform and provides an overview of the enterprise's technology platform.1 Edition Personal PDF Edition. All Rights Reserved Example Platform Decomposition Diagram Platform Decomposition Hardware Logical Technology Components Tech Function Web Server Layer (Application Support) Software Logical Technology Components Tech Function Physical Technology Components Tech Function Physical Technology Components Tech Function Web server layer Web Server Layer Web Server Layer Application Layer Application Layer Application Layer Application Layer Database Layer Database Layer Database Layer Database Layer Attributes • • • • • • • • Name Model/Type Clusters Number of Components Vendor Server Type (mainframe. The Open Group 53 . All Rights Reserved © 2009-2011 The Open Group. Mid range. For non-commercial use only Platform Decomposition Diagram • The Platform Decomposition diagram depicts the technology platform that supports the operations of the Information Systems Architecture. Slide 105 ©2009-2011 The Open Group.

All Rights Reserved Copyright © 2009-2011. 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. Images (DFS Distributed File System Server) Order capture (DB server) HTML Code (Web server cluster with 2 nodes) Order Entry & Shopping Cart (Application Server cluster with 2 nodes) Messaging Server Load Balancer Code App Server DB Over LAN HTTP Firewall Firewall Firewall Slide 108 ©2009-2011 The Open Group.1 Edition Personal PDF Edition. All Rights Reserved © 2009-2011 The Open Group. and data store layers and service-level requirements of the components. HTML. WAN. The Open Group 54 . • 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. Slide 107 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9. For non-commercial use only Processing Diagram • The Processing diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform. business logic. All Rights Reserved Example Processing Diagram Open Internet DMZ Internet Zone Intranet Zone File Explorer.

and access to these technology components – Understand the Technology Architecture that support the applications during problem resolution and troubleshooting – Isolate performance problems encountered and perform necessary upgrade to specific physical technology components – Identify areas of optimization – Enable application/technology auditing and prove compliance – Serve as an important tool supporting effective change management Slide 109 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9. • The diagram is useful for the following reasons: – Enable understanding of which application is deployed where – Establishing authorization. For non-commercial use only Network Computing Hardware Diagram • The purpose of this diagram is to show the "as deployed" logical view of logical application components in a distributed network computing environment. security.node 3 (ABM) DFS Distributed File System (html. All Rights Reserved © 2009-2011 The Open Group.1 Edition Personal PDF Edition. All Rights Reserved Example Network Computing Hardware Diagram DMZ Internet Zone Intranet Zone Web server Web cluster server cluster Web server clusternode 3 (ABM) Application Server cluster Application (node 3) Server cluster (node 3) App Server cluster . The Open Group 55 . All Rights Reserved Copyright © 2009-2011. images) Load Balancer and Dispatcher Database (ABM Production) Database (ABM Staging) Load Balancer and Dispatcher Web server cluster Web server cluster-node 2 (eCommerce) Application Server (Order Engine) Database App Server DB App Server Firewall Firewall Firewall Slide 110 ©2009-2011 The Open Group.

Slide 111 ©2009-2011 The Open Group. but addresses protocol and capacity issues.1 Edition Personal PDF Edition. All Rights Reserved 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 112 ©2009-2011 The Open Group. For non-commercial use only Communications Engineering Diagram • The Communications Engineering diagram describes the means of communication between assets in the Technology Architecture • It takes logical connections between client and server components and identifies network boundaries and network infrastructure required to physically implement those connections.TOGAF® Standard Courseware V9. All Rights Reserved Copyright © 2009-2011. • It does not describe the information format or content. All Rights Reserved © 2009-2011 The Open Group. The Open Group 56 .

Matrices and Diagrams Diagrams • Project Context diagram • Benefits diagram Catalogs Matrices Slide 114 ©2009-2011 The Open Group. The Open Group 57 . All Rights Reserved E Opportunities & Solutions Catalogs. All Rights Reserved © 2009-2011 The Open Group.1 Edition Personal PDF Edition. For non-commercial use only Phase C Phase E: Opportunities & Solutions – Catalogs. All Rights Reserved Copyright © 2009-2011. Matrices and Diagrams TOGAF is a registered trademark of The Open Group in the United States and other countries Slide 113 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9.

All Rights Reserved © 2009-2011 The Open Group. For non-commercial use only Project Context Diagram Slide 115 ©2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.1 Edition Personal PDF Edition. The Open Group 58 . All Rights Reserved Project Context Diagram Slide 116 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9.

1 Edition Personal PDF Edition. Matrices and Diagrams TOGAF is a registered trademark of The Open Group in the United States and other countries Slide 118 ©2009-2011 The Open Group. All Rights Reserved Phase C Requirements Management – Catalogs. All Rights Reserved © 2009-2011 The Open Group. For non-commercial use only Benefits Diagram Slide 117 ©2009-2011 The Open Group. The Open Group 59 . All Rights Reserved Copyright © 2009-2011.TOGAF® Standard Courseware V9.

e. All Rights Reserved Catalogs Catalog Requirements Catalog Purpose The Requirements catalog captures things that the enterprise needs to do to meet its objectives. For non-commercial use only R Requirements Management Catalogs. Requirements can also be used as a quality assurance tool to ensure that a particular architecture is fit-for-purpose (i.. The Requirements catalog contains the following metamodel entities: * Requirement * Assumption * Constraint * Gap Slide 120 ©2009-2011 The Open Group. can the architecture meet all identified requirements).TOGAF® Standard Courseware V9. The Open Group 60 .1 Edition Personal PDF Edition. Requirements generated from architecture engagements are typically implemented through change initiatives identified and scoped during Phase E (Opportunities & Solutions). Matrices and Diagrams Diagrams Catalogs • Requirements Catalog Matrices Slide 119 ©2009-2011 The Open Group. All Rights Reserved © 2009-2011 The Open Group. All Rights Reserved Copyright © 2009-2011.

For non-commercial use only Resources • A set of downloadable templates is available – http://www.org/bookstore/catalog/i093. All Rights Reserved © 2009-2011 The Open Group.htm Slide 121 ©2009-2011 The Open Group.TOGAF® Standard Courseware V9.1 Edition Personal PDF Edition. Matrices and Diagrams TOGAF is a registered trademark of The Open Group in the United States and other countries Slide 122 ©2009-2011 The Open Group.opengroup. All Rights Reserved Sample Catalogs. The Open Group 61 . All Rights Reserved Copyright © 2009-2011.

Sign up to vote on this title
UsefulNot useful