TOGAF Sample Matrices, Catalogs and Diagrams from the Open Group
- 1. ©2009 The Open Group, All Rights Reserved1 Sample Catalogs, Matrices and Diagrams Draft v2: 14 September 2009 The Open Group gratefully acknowledges the contributions from SAP and Capgemini
- 2. ©2009 The Open Group, All Rights Reserved2 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.
- 3. ©2009 The Open Group, All Rights Reserved3 TOGAF 9 Catalogs, Matrices and Diagrams Phase A, Architecture Vision • Stakeholder Map matrix • Value Chain diagram • Solution Concept diagram Requirements Management • Requirements catalog Phase C, Application Architecture • Application Portfolio catalog • Interface catalog • System/Organization matrix • Role/System matrix • System/Function matrix • Application Interaction matrix • Application Communication diagram • Application and User Location diagram • System Use-Case diagram • Enterprise Manageability diagram • Process/System Realization diagram • Software Engineering diagram • Application Migration diagram • Software Distribution diagram Phase E. Opportunities & Solutions • Project Context diagram • Benefits diagram Phase C, Data Architecture • Data Entity/Data Component catalog • Data Entity/Business Function matrix • System/Data matrix • Class diagram • Data Dissemination diagram • Data Security diagram • Class Hierarchy diagram • Data Migration diagram • Data Lifecycle diagram Phase D, Technology Architecture • Technology Standards catalog • Technology Portfolio catalog • System/Technology matrix • Environments and Locations diagram • Platform Decomposition diagram • Processing diagram • Networked Computing/Hardware diagram • Communications Engineering diagram Phase 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 • Use-Case diagram • Organization Decomposition diagram • Process Flow diagram • Event diagram Preliminary Phase • Principles catalog
- 4. ©2009 The Open Group, All Rights Reserved4 Preliminary Phase Catalogs, Matrices and Diagrams Catalogs • Principles Catalog Matrices Diagrams P
- 5. ©2009 The Open Group, All Rights Reserved5 CatalogsP The Principles catalog captures principles of the business and architecture principles that describe what a "good" solution or architecture should look like. Principles are used to evaluate and agree an outcome for architecture decision points. Principles are also used as a tool to assist in architectural governance of change initiatives. The Principles catalog contains the following metamodel entities: * Principle Principles Catalog PurposeCatalog
- 6. ©2009 The Open Group, All Rights Reserved6 Architecture Vision Catalogs, Matrices and Diagrams Catalogs Matrices • Stakeholder Map Matrix Diagrams • Value Chain Diagram • Solution Concept Diagram A
- 7. ©2009 The Open Group, All Rights Reserved7 Example Stakeholder Map Matrix Roadmaps Business Footprint Application Communication Functional Decomposition Keep Satisfied This stakeholder group is interested in prioritizing, funding, and aligning change activity. An understanding of project content and technical dependencies adds a further dimension of richness to portfolio management and decision making. Program Management Office Organization Chart Organization/Actor/ Location Keep Informed Key features of the enterprise architecture are roles and Actors that support the functions, applications, and technology of the organization. HR are important stakeholders in ensuring that the correct roles and actors are represented. HR Business Footprint Goal/Objective/Service Model Organization Chart Keep Satisfied This stakeholder group is interested in the high-level drivers, goals and objectives of the organization, and how these are translated into an effective process and IT architecture to advance the business CxO Relevant ArtifactsClassInvolvementStakeholder A
- 8. ©2009 The Open Group, All Rights Reserved8 Example Value Chain Diagram Source: Wikipedia.org A
- 9. ©2009 The Open Group, All Rights Reserved9 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 Certification Publications Customers Interest, consideration, Join, renew Reliable, 24x7, self service infrastructure A
- 10. ©2009 The Open Group, All Rights Reserved10 Business Architecture Catalogs, Matrices and Diagrams Catalogs • Organization/Actor catalog • Driver/Goal/Objective catalog • Role catalog • Business Service/Function catalog • Location catalog • Process/Event/Control/Product catalog • Contract/Measure catalog Matrices • Business Interaction matrix • Actor/Role matrix Diagrams • Business Footprint diagram • Business Service/Information diagram • Functional Decomposition diagram • Product Lifecycle diagram • Goal/Objective/Service diagram • Use-Case diagram • Organization Decomposition diagram • Process Flow diagram • Event diagram B
- 11. ©2009 The Open Group, All Rights Reserved11 Catalogs The purpose of the Role catalog is to provide a listing of all authorization levels or zones within an enterprise. Frequently, application security or behavior is defined against locally understood concepts of authorization that create complex and unexpected consequences when combined on the user desktop. It contains the following metamodel entities: •Role Role Catalog A cross-organizational reference of how an organization meets its drivers in practical terms through goals, objectives, and (optionally) measures. It contains the following metamodel entities: •Organization Unit, Driver, Goal, Objective, Measure (may optionally be included) Driver/Goal/ Objective Catalog A definitive listing of all participants that interact with IT, including users and owners of IT systems. It contains the following metamodel entities: •Organization Unit, Actor Location (may be included in this catalog if an independent Location catalog is not maintained) Organization/ Actor Catalog PurposeCatalog B
- 12. ©2009 The Open Group, All Rights Reserved12 Catalogs The Process/Event/Control/Product catalog provides a hierarchy of processes, events that trigger processes, outputs from processes, and controls applied to the execution of processes. This catalog provides a supplement to any Process Flow diagrams that are created and allows an enterprise to filter, report, and query across organizations and processes to identify scope, commonality, or impact. It contains the following metamodel entities: •Process, Event, Control, Product Process/ Event/ Control/ Product Catalog A listing of all locations where an enterprise carries out business operations or houses architecturally relevant assets, such as data centers or end-user computing equipment. It contains the following metamodel entities: •Location Location Catalog A functional decomposition in a form that can be filtered, reported on, and queried, as a supplement to graphical Functional Decomposition diagrams. It contains the following metamodel entities: •Organization Unit,Business Function, Business Service, Information System Service (may optionally be included here) Business Service / Function Catalog PurposeCatalog B
- 13. ©2009 The Open Group, All Rights Reserved13 Catalogs A listing of all agreed service contracts and (optionally) the measures attached to those contracts. It forms the master list of service levels agreed to across the enterprise. It contains the following metamodel entities: •Business Service •Information System Service (optionally) •Contract •Measure Contract/ Measure Catalog PurposeCatalog B
- 14. ©2009 The Open Group, All Rights Reserved14 Matrices • Business Interaction matrix • Actor/Role matrix B
- 15. ©2009 The Open Group, All Rights Reserved15 Business Interaction Matrix • The purpose of this matrix is to depict the relationship interactions between organizations and business functions across the enterprise. Consuming Business Services Engineering Procurement Manufacturing Sales and Distribution Customer Service Engineering Procurement Manufacturing Contract for supply of materials Contract for supply of sales forecasts Sales and Distribution Contract for supply of product specification Contract for supply of product Customer Service Contract for fulfillment of customer orders Providing Business Services B
- 16. ©2009 The Open Group, All Rights Reserved16 Actor/role Matrix • The purpose of this matrix is to show which actors perform which roles, supporting definition of security and skills requirements. CIO EnterpriseArchitect EnterpriseDesignAuthority TechnicalDesignAuthority ITManagementForum BusinessUnitHead BusinessUnitServiceOwner BusinessUnitApplicationArchitect HeadofStrategyandArchitecture InfrastructureStrategist InfrastructureSolutionArchitect ArchitectureConfigurationManager EnterpriseInfrastructureArchitect HeadofImplementation InfrastructureDesigner Strategy Lifecycle Roles Architecture Refresh I R A I C C R C C C I I R I C C Architecture Roadmap I C A I R C C I C R I I R C C I C Benefits Assessment I I I I I I I I I R R I C A Change Management C I A I I I R I I I R R C Framework Refresh C C C C C I C A I I I R C C I Project Lifecycle Roles Solution Architecture Vision I I I A I I C C I I R I C C R Logical Solution Architecture A I I C C I I R I C C C R Physical Solution Architecture A I I C C I I R I C R C R Design Governance A I I C C I I R I C R C C Architecture Configuration Management C I I R R R A 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 ExternalVendors/Suppliers Strategy and Architecture Actors Infrastructure Implementation Actors ITOperations Office of CIO Actors Steering Group Actors Business Unit Actors ProjectManager B
- 17. ©2009 The Open Group, All Rights Reserved17 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 B
- 18. ©2009 The Open Group, All Rights Reserved18 Business Footprint Diagram • Describes the links between business goals, organizational units, business functions, and services, and maps these functions to the technical components delivering the required capability. • Demonstrates only the key facts linking organization unit functions to delivery services and is utilized as a communication platform for senior-level (CxO) stakeholders B
- 19. ©2009 The Open Group, All Rights Reserved19 Example Business Footprint Diagram B
- 20. ©2009 The Open Group, All Rights Reserved20 Business Service/Information Diagram • Shows the information needed to support one or more business services. • Shows what data is consumed by or produced by a business service and may also show the source of information. • Shows an initial representation of the information present within the architecture and therefore forms a basis for elaboration and refinement within Phase C (Data Architecture). B
- 21. ©2009 The Open Group, All Rights Reserved21 Example Business Service/Information Diagram Complaint Handling Service Complaint Common Faults Customer Details Customer Details Complaint Resolution Basic example B
- 22. ©2009 The Open Group, All Rights Reserved22 Example Business Service/Information Diagram Customer Complaint Handling Service Complaint Fault Management Service Common Faults Lead Management Service Customer Details Customer Details Complaint Resolution Extended example showing actors and service interactions B
- 23. ©2009 The Open Group, All Rights Reserved23 Functional Decomposition Diagram • It shows on a single page the capabilities of an organization that are relevant to the consideration of an architecture. • By examining the capabilities of an organization from a functional perspective, it is possible to quickly develop models of what the organization does without being dragged into extended debate on how the organization does it. B
- 24. ©2009 The Open Group, All Rights Reserved24 Example Functional Decomposition Diagram B
- 25. ©2009 The Open Group, All Rights Reserved25 Product Lifecycle Diagram • This assists in understanding the lifecycles of key entities within the enterprise. • Understanding product lifecycles is becoming increasingly important with respect to environmental concerns, legislation, and regulation where products must be tracked from manufacture to disposal. • Equally, organizations that create products that involve personal or sensitive information must have a detailed understanding of the product lifecycle during the development of Business Architecture in order to ensure rigor in design of controls, processes, and procedures. Examples of this include credit cards, debit cards, store/loyalty cards, smart cards, user identity credentials (identity cards, passports, etc.). B
- 26. ©2009 The Open Group, All Rights Reserved26 Example Product Lifecycle Diagram Source: Kotler and Armstrong, 2004 B
- 27. ©2009 The Open Group, All Rights Reserved27 Goal/Objective/Service Diagram • This defines the ways in which a service contributes to the achievement of a business vision or strategy. • Services are associated with the drivers, goals, objectives, and measures that they support, allowing the enterprise to understand which services contribute to similar aspects of business performance. • This also provides qualitative input on what constitutes high performance for a particular service. B
- 28. ©2009 The Open Group, All Rights Reserved28 Example Goal/Objective/ Service Diagram gol-Increase revenues obj-creating new line of cars by the end of... obj-"aftersales" market Function- sales and marketing cap- Market in g cap-Sales cap-Pre- Owned ve hica... cap- ca mpaign cap-Pre-sale cap-Order- to-Delivery rol-CFO rol-VP Salesrol-VP Marketing B
- 29. ©2009 The Open Group, All Rights Reserved29 Business Use-case Diagram • This displays the relationships between consumers and providers of business services. • Business services are consumed by actors or other business services and the Business Use-Case diagram provides added richness in describing business capability by illustrating how and when that capability is used. • They help to describe and validate the interaction between actors and their roles to processes and functions. • As the architecture progresses, the use-case can evolve from the business level to include data, application, and technology details. Architectural business use-cases can also be re-used in systems design work. B
- 30. ©2009 The Open Group, All Rights Reserved30 Example Use-case DiagramB
- 31. ©2009 The Open Group, All Rights Reserved31 Organization Decomposition Diagram • This describes the links between actor, roles, and location within an organization tree. • An organization map should provide a chain of command of owners and decision-makers in the organization. B
- 32. ©2009 The Open Group, All Rights Reserved32 Example Organization Decomposition Diagram org-Worldwide Public Affairs and Policy rol-CEO rol-Wolrdwide Communications rol-Philanthropy/Stakeholder Advocacy rol-Worldwide Policy rol-Federal Government relations rol-Field Based Govt. Relations rol-Wolrdwide Medical rol-Safety Risk Management rol-Science Advocacy org-Chief Medical Officer rol-Wolrdwide Research rol-Worldwide Development rol-Worldwide Research Affairs org-Global Research & Development rol-Vice Chairman rol-Global Manufacturing rol-CFO rol-Worlwide Strategic Planning rol-Animal Health rol-Worldwide Licensing and Business Develoment rol-Wolrdwide Technology rol-Business Services rol-Wolrdwide Investor Development rol-Internal Audit rol-Financial Strategy rol-Human Resources rol-Site Leader(s) rol-Wolrdwide Pharmaceutical Operations loc-US loc-Japan/ASIA loc-Europe loc-Middle East loc-Canada org-Wolrdwide talent Development and HR rol-Talent Development rol-HealthWelness rol-Planning rol-Diversity and Inclusion rol-compensation and Benefits org-General Counsel rol-Intellectual Property rol-Employment Law rol-Line Support rol-Litigation/Regulatory rol-Business Transactions rol-Complinace Officer B
- 33. ©2009 The Open Group, All Rights Reserved33 Process Flow Diagram • This depicts all models and mappings related to the process metamodel entity. • It shows sequential flow of control between activities and may utilize swim-lane techniques to represent ownership and realization of process steps. • In addition to showing a sequence of activity, process flows can also be used to detail the controls that apply to a process, the events that trigger or result from completion of a process, and also the products that are generated from process execution. B
- 34. ©2009 The Open Group, All Rights Reserved34 Example Process Flow Diagram Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 6 Step 6 STOP Start B
- 35. ©2009 The Open Group, All Rights Reserved35 Example Process Flow Diagram Sales Rep Technical Support Team Custom app CRM MS Word MS Excel Email email Consolidation Tool Spreadsheet Custom Bid Approver IWF Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 6 Step 6 STOP Start Pricer Pricer Customer Rep Customer Rep Customer Rep Process Flow (w/Roles & Applications) B
- 36. ©2009 The Open Group, All Rights Reserved36 Events Diagram • This depicts the relationship between events and process. • Certain events - such as arrival of information (e.g. a customer’s sales order) or a point in time (e.g. end of fiscal quarter) cause work and actions to be undertaken within the business. B
- 37. ©2009 The Open Group, All Rights Reserved37 Example Events Diagram Event Process Triggers Impacts/Generates (e.g. End of Fiscal Quarter) (e.g. Financial Reporting Process) Business result (e.g. 1Q results reported to Government Agencies) B
- 38. ©2009 The Open Group, All Rights Reserved38 Example Events Matrix Financial report generated Financial reporting processEnd of quarter Custom product configured Customer contract signed Custom product configuration Capture requirements from customer Define custom specifications Price custom configuration Negotiate with customer Secure approval from customer regarding configuration and price Customer submits request for custom product Sales order captured in order book Sales order processing Create & save sales order Generate acknowledgement Confirm receipt of customer order Begin order fulfilment activities Customer submits sales order BUSINESS RESULT(S)PROCESS TRIGGEREDEVENT B
- 39. ©2009 The Open Group, All Rights Reserved39 Data Architecture Catalogs, Matrices and Diagrams Catalogs • Data Entity/Data Component catalog Matrices • Data Entity/Business Function matrix • System/Data matrix Diagrams • Class diagram • Data Dissemination diagram • Data Security diagram • Class Hierarchy diagram • Data Migration diagram • Data Lifecycle diagram C
- 40. ©2009 The Open Group, All Rights Reserved40 Catalogs To identify and maintain a list of all the data use across the enterprise, including data entities and also the data components where data entities are stored. It contains the following metamodel entities: •Data Entity •Logical Data Component •Physical Data Component •Data Entity/ Data Component Catalog PurposeCatalog C
- 41. ©2009 The Open Group, All Rights Reserved41 Matrices • Data Entity/Business Function matrix • System/Data matrix C
- 42. ©2009 The Open Group, All Rights Reserved42 Data Entity/Business Function Matrix • The purpose of the Data Entity/Business Function matrix is to depict the relationship between data entities and business functions within the enterprise. • The mapping of the Data Entity-Business Function relationship enables the following to take place: – Assignment of ownership of data entities to organizations – Understand the data and information exchange requirements business services – Support the gap analysis and determine whether any data entities are missing and need to be created – Define system of origin, system of record, and system of reference for data entities – Enable development of data governance programs across the enterprise (establish data steward, develop data standards pertinent to the business function, etc.) C
- 43. ©2009 The Open Group, All Rights Reserved43 Example Data Entity/Business Function Matrix Product data management service Owner – Global product development organization N/A N/A Customer Requirement Processing Service Owner – Supply Chain Manager Supply Chain Management N/A Lead Processing Service Owner – Customer Relationship Manager Function can only Create, read, update customer leads Business partner data management service Owner of data entity (person or organization) Function can Create, read, update and delete Business partner data management service Owner – Sales & Marketing business unit executive Function can Create, read, update and delete customer master data Customer Relationship Management PRODUCT MASTER CUSTOMER LEADS BUSINESS PARTNER CUSTOMER MASTER BUSINESS FUNCTION (Y-AXIS) AND DATA ENTITY (X-AXIS) C
- 44. ©2009 The Open Group, All Rights Reserved44 System/Data Matrix • The purpose of the System/Data matrix is to depict the relationship between systems (i.e., application components) and the data entities that are accessed and updated by them. • Systems will create, read, update, and delete specific data entities that are associated with them. For example, a CRM application will create, read, update, and delete customer entity information. C
- 45. ©2009 The Open Group, All Rights Reserved45 Example System/Data Matrix Historical dataIntersection of multiple data entities (e.g. All sales orders by customer XYZ and by month for 2006) Warehouse and data mart that supports North American region Sales Business Warehouse Transactional dataSales ordersSystem of record for order book Commerce Engine Master dataCustomer dataSystem of record for customer master data CRM DATA ENTITY TYPEDATA ENTITY DESCRIPTION OR COMMENTS APPLICATION (Y- AXIS) AND DATA (X-AXIS) C
- 46. ©2009 The Open Group, All Rights Reserved46 Diagrams • Class diagram • Data Dissemination diagram • Data Security diagram • Class Hierarchy diagram • Data Migration diagram • Data Lifecycle diagram C
- 47. ©2009 The Open Group, All Rights Reserved47 Class Diagram • The purpose is to depict the relationships among the critical data entities (or classes) within the enterprise. Information Customer Information Customer Actor Trigger Payment Update Account ProcessContact Service Request Appeal Enquiry Complaint Account Agent Customer Profile I.C2 I.A1 I.C1 P.A12 P.CS13 P.CS5 A.C2 A.A4 T.P8 T.C19 T.C16 T.C1 C
- 48. ©2009 The Open Group, All Rights Reserved48 Data Dissemination Diagram • The purpose of the Data Dissemination diagram is to show the relationship between data entity, business service, and application components. • The diagram should show how the logical entities are to be physically realized by application components. • Additionally, the diagram may show data replication and system ownership of the master reference for data. C
- 49. ©2009 The Open Group, All Rights Reserved49 Example Data Dissemination Diagram Warehouse Warehouse Customer Order History Stock Warehouse Warehouse Customer Order History Stock Billing Billing Customer Account Balance Invoice History Billing Billing Customer Account Balance Invoice History Online Account Self Service Online Account Self Service ApplicationData EntitiesBusiness Service BillingInvoice History BillingAccount Balance WarehouseStock WarehouseOrder History Warehouse Billing CustomerOnline Account Self Service C
- 50. ©2009 The Open Group, All Rights Reserved50 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. New Dispatched New Closed Archived Deleted Fulfilled Invoiced Paid Closed Archived Deleted Fulfilment Order Customer Order C
- 51. ©2009 The Open Group, All Rights Reserved51 Data Security Diagram • The purpose of the Data Security diagram is to depict which actor (person, organization, or system) can access which enterprise data. • This relationship can also be shown in a matrix form between two objects or can be shown as a mapping. C
- 52. ©2009 The Open Group, All Rights Reserved52 Example Data Security Diagram Business Function Business Service Process Logical Application Component Actor Location Class of Roles (by job function) Physical Access Single Sign-on or Access Control Access Control (levels of granularity) Access Control (levels of granularity) C
- 53. ©2009 The Open Group, All Rights Reserved53 Example Data Security Matrix Access Control WW (all Geos)Supplier Portal Service WW Direct Procurement Geo Brand ManagersWW Product Development (Org Unit) Access control (system to system) LASupplier Portal Service WW Direct Procurement Not applicableWW Contracts System (application) Access control NA (US Midwest) Supplier portal Service WW Direct Procurement Procurement Management and Control Procurement & Spend Analyst Physical Access Control (tables xyz only) NA (US, CA) EMEA (UK, DE) APJ SOA portfolio serviceFinancial AnalysisSOA Portfolio Financial Analyst Financial Analyst TYPE OF ACCESS LOCATION BUSINESS SERVICE FUNCTION CLASS OF ROLES (JOB FUNCTION) ACTOR C
- 54. ©2009 The Open Group, All Rights Reserved54 Data Migration Diagram • The purpose of the Data Migration diagram is to show the flow of data from the source to the target applications. • The diagram will provide a visual representation of the spread of sources/targets and serve as a tool for data auditing and establishing traceability. C
- 55. ©2009 The Open Group, All Rights Reserved55 Example Data Migration Diagram ABM CRM ERP SRM CCB BDW MRPA VLC (one per geo) Source Staging Transformation & Data Quality Target Staging System of Record for Vendor Master & Contracts System of Record for Material Master & Order history System of Record for Customer Master Source of Customer records Source of order history Source of Material data Source of vendor data “Baseline” application components Data migration technology components “Target” application components C
- 56. ©2009 The Open Group, All Rights Reserved56 Example Data Migration Mapping CUSTTELEPHONECust_Tele CUSTCONTACTCust_ContactName CUSTADDR_LINE3Cust_Street_Addr CUSTADDR_LINE2Cust_Street_Addr CUSTADDR_LINE1Cust_Street_Addr CUSTNAMECRMCust_NameABM TARGET DATA ELEMENT TARGET LOGICAL APPLICATION COMPONENT SOURCE DATA ELEMENT SOURCE LOGICAL APPLICATION COMPONENT C
- 57. ©2009 The Open Group, All Rights Reserved57 Class Hierarchy Diagram • The purpose of the Class Hierarchy diagram is to show the technical stakeholders a perspective of the class hierarchy. • This diagram gives the stakeholders an idea of who is using the data, how, why, and when. C
- 58. ©2009 The Open Group, All Rights Reserved58 Example Class Hierarchy Diagram Authorised User Authorised User Vehicle TesterVehicle Tester Trainer/Booker Trainer/Booker IndividualIndividual Keeper Keeper Purchaser/NomineePurchaser/NomineeCustomerCustomer DriverDriver OrganisationOrganisation Driving InstructorDriving Instructor Taxi Driver Taxi Driver Driving Examiner Driving Examiner ManufacturerManufacturer OperatorOperator Dealing Dealing Driving ExaminerDriving Examiner C
- 59. ©2009 The Open Group, All Rights Reserved59 Application Architecture Catalogs, Matrices and Diagrams Catalogs • Application Portfolio catalog • Interface catalog Matrices • System/Organization matrix • Role/System matrix • System/Function matrix • Application Interaction matrix Diagrams • Application Communication diagram • Application and User Location diagram • System Use-Case diagram • Enterprise Manageability diagram • Process/System Realization diagram • Software Engineering diagram • Application Migration diagram • Software Distribution diagram C
- 60. ©2009 The Open Group, All Rights Reserved60 Catalogs The purpose of the Interface catalog is to scope and document the interfaces between applications to enable the overall dependencies between applications to be scoped as early as possible. It contains the following metamodel entities: •Logical Application Component •Physical Application Component •Application communicates with application relationship Interface Catalog To identify and maintain a list of all the applications in the enterprise. This list helps to define the horizontal scope of change initiatives that may impact particular kinds of applications. An agreed Application Portfolio allows a standard set of applications to be defined and governed. It contains the following metamodel entities: •Information System Service •Logical Application Component •Physical Application Component Application Portfolio Catalog PurposeCatalog C
- 61. ©2009 The Open Group, All Rights Reserved61 Matrices • System/Organization matrix • Role/System matrix • System/Function matrix • Application Interaction matrix C
- 62. ©2009 The Open Group, All Rights Reserved62 System/Organization Matrix • The purpose of this matrix is to depict the relationship between systems (i.e., application components) and organizational units within the enterprise. • The mapping of the Application Component-Organization Unit relationship is an important step as it enables the following to take place: – Assign usage of applications to the organization units that perform business functions – Understand the application support requirements of the business services and processes carried out by an organization unit – Support the gap analysis and determine whether any of the applications are missing and as a result need to be created – Define the application set used by a particular organization unit C
- 63. ©2009 The Open Group, All Rights Reserved63 Example System/Organization Matrix XXPROCURESOFT XXXSAP FINANCIALS XXSIEBEL XXXSAP HR CORPORATE FINANCE HR PROCUREMENT AND WAREHOUSING CUSTOMER SERVICES APPLICATION (Y-AXIS) AND ORGANISATION UNIT (X-AXIS) C
- 64. ©2009 The Open Group, All Rights Reserved64 Role/System Matrix • The purpose of the Role/System matrix is to depict the relationship between systems (i.e., application components) and the business roles that use them within the enterprise. • The mapping of the Application Component-Role relationship is an important step as it enables the following to take place: – Assign usage of applications to the specific roles in the organization – Understand the application security requirements of the business services and processes supporting the function, and check these are in line with current policy – Support the gap analysis and determine whether any of the applications are missing and as a result need to be created – Define the application set used by a particular business role; essential in any move to role-based computing C
- 65. ©2009 The Open Group, All Rights Reserved65 Example Role/System Matrix XXPROCURESOFT XXXXSAP FINANCIALS XXSIEBEL XXXXSAP HR CHIEF ACCOUNTANT FINANCE ANALYST CALL CENTRE MANAGER CALL CENTRE OPERATOR APPLICATION (Y- AXIS) AND FUNCTION (X- AXIS) C
- 66. ©2009 The Open Group, All Rights Reserved66 System/Function Matrix • The purpose of the System/Function matrix is to depict the relationship between systems (i.e., application components) and business functions within the enterprise. • The mapping of the Application Component-Function relationship is an important step as it enables the following to take place: – Assign usage of applications to the business functions that are supported by them – Understand the application support requirements of the business services and processes carried out – Support the gap analysis and determine whether any of the applications are missing and as a result need to be created – Define the application set used by a particular business function C
- 67. ©2009 The Open Group, All Rights Reserved67 Example System/Function Matrix XXPROCURESOFT XXXSAP FINANCIALS XXSIEBEL XXXXSAP HR GENERAL LEDGER MAINTENANCE VACANCY FILLING WAREHOUSE CONTROL CALL CENTRE 1ST LINE APPLICATION (Y- AXIS) AND FUNCTION (X- AXIS) C
- 68. ©2009 The Open Group, All Rights Reserved68 Diagrams • Application Communication diagram • N2 model or Node Connectivity diagram • Application and User Location diagram • System Use-Case diagram • Enterprise Manageability diagram • Process/System Realization diagram • Software Engineering diagram • Application Migration diagram • Software Distribution diagram C
- 69. ©2009 The Open Group, All Rights Reserved69 Application Communication Diagram • The purpose of the Application Communication diagram is to depict all models and mappings related to communication between applications in the metamodel entity. • It shows application components and interfaces between components. • Communication should be logical and should only show intermediary technology where it is architecturally relevant. C
- 70. ©2009 The Open Group, All Rights Reserved70 Example Application Communication Diagram C
- 71. ©2009 The Open Group, All Rights Reserved71 N2 Model 1a 1b 1c 1d 2a 3a 3b 3c 3d 4b 4a ABC ABM CCD CRM IPC C
- 72. ©2009 The Open Group, All Rights Reserved72 Information Exchange Matrix Subscribe/Publi sh timer Product catalog CCD ABM2a Order created in the backend ERP system Sales order (confirm create) ABC ABM1b New sales order from front end Sales order (create request) ABM ABC1a EVENT TRIGGERED DATA ENTITYDESTINATIONSOURCELABEL C
- 73. ©2009 The Open Group, All Rights Reserved73 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 C
- 74. ©2009 The Open Group, All Rights Reserved74 Example Application & User Location Diagram (part 1) Manufacturing & logistics Beijing Manufacturing Plant InternalTest Engineers Mechanical Engineers Procurement managers SAP R/3 NA Sales & Marketing EMEA Sales Chicago Sears tower office Chicago Downtown office Middlesex, London NA Western Region EMEA Headquarters, UK InternalDeveloper Super User Administrator CRM ORG UNIT (USER BELONGS TO) LOCATION ADDRESS USER BUSINESS LOCATION INTERNAL, CUSTOMER OR PARTNER USER TYPEAPPLICATION C
- 75. ©2009 The Open Group, All Rights Reserved75 Example Application & User Location Diagram (part 2) C
- 76. ©2009 The Open Group, All Rights Reserved76 System Use Case Diagram Source: wikipedia.org C
- 77. ©2009 The Open Group, All Rights Reserved77 Enterprise Manageability Diagram • The Enterprise Manageability diagram shows how one or more applications interact with application and technology components that support operational management of a solution. • Analysis can reveal duplication and gaps, and opportunities in the IT service management operation of an organization. C
- 78. ©2009 The Open Group, All Rights Reserved78 Example Enterprise Manageability Diagram C
- 79. ©2009 The Open Group, All Rights Reserved79 Process/System Realization Diagram • The purpose of the Process/System Realization diagram is to clearly depict the sequence of events when multiple applications are involved in executing a business process. • It enhances the Application Communication diagram by augmenting it with any sequencing constraints, and hand-off points between batch and real-time processing. C
- 80. ©2009 The Open Group, All Rights Reserved80 Example Process/System Realization DiagramC
- 81. ©2009 The Open Group, All Rights Reserved81 Software Engineering Diagram • The Software Engineering diagram breaks applications into packages, modules, services, and operations from a development perspective. • It enables more detailed impact analysis when planning migration stages, and analyzing opportunities and solutions. • It is ideal for application development teams and application management teams when managing complex development environments. C
- 82. ©2009 The Open Group, All Rights Reserved82 Example Software Engineering Diagram C
- 83. ©2009 The Open Group, All Rights Reserved83 Application/Migration Diagram • The Application Migration diagram identifies application migration from baseline to target application components. • It enables a more accurate estimation of migration costs • It should be used to identify temporary applications, staging areas, and the infrastructure required to support migrations C
- 84. ©2009 The Open Group, All Rights Reserved84 Example Application/Migration Diagram C
- 85. ©2009 The Open Group, All Rights Reserved85 Software Distribution Diagram • This diagram is a composite of the Software Engineering diagram and the Application-User Location diagram. • Depending on the circumstances, this diagram alone may be sufficient, or may not be needed. C
- 86. ©2009 The Open Group, All Rights Reserved86 Technology Architecture Catalogs, Matrices and Diagrams Catalogs • Technology Standards catalog • Technology Portfolio catalog • Matrices • System/Technology matrix Diagrams • Environments and Locations diagram • Platform Decomposition diagram • Processing diagram • Networked Computing/Hardware diagram • Communications Engineering diagram D
- 87. ©2009 The Open Group, All Rights Reserved87 Catalogs • Technology Standards catalog • Technology Portfolio catalog D
- 88. ©2009 The Open Group, All Rights Reserved88 Catalogs The purpose of this catalog is to identify and maintain a list of all the technology in use across the enterprise, including hardware, infrastructure software, and application software. An agreed technology portfolio supports lifecycle management of technology products and versions and also forms the basis for definition of technology standards It contains the following metamodel entities: •Platform Service, Logical Technology Component, Physical Technology Component Technology Portfolio Catalog This documents the agreed standards for technology across the enterprise covering technologies, and versions, the technology lifecycles, and the refresh cycles for the technology. It contains the following metamodel entities: •Platform Service, Logical Technology Component, Physical Technology Component Technology Standards Catalog PurposeCatalog D
- 89. ©2009 The Open Group, All Rights Reserved89 Matrices • System/Technology matrix D
- 90. ©2009 The Open Group, All Rights Reserved90 System/Technology Matrix • The System/Technology matrix documents the mapping of business systems to technology platform. • The System/Technology matrix shows: – Logical/Physical Application Components – Services, Logical Technology Components, and Physical Technology Components – Physical Technology Component realizes Physical Application Component relationships D
- 91. ©2009 The Open Group, All Rights Reserved91 Example System/Technology Matrix [email protected] serverLoad balancer and Dispatcher [email protected] server (stating) [email protected] server (production) [email protected] server – node 3 [email protected] server – node 2 [email protected] server – node 1 [email protected] server - node 3 [email protected] server - node 2 [email protected] server - node 1ABM IP ADDRESSSERVER ADDRESS PHYSICAL TECHNOLOGY COMPONENT LOGICAL APPLICATION COMPONENT D
- 92. ©2009 The Open Group, All Rights Reserved92 Example System/Technology Matrix SW Components – LB v3.2 (list all the other components of the SW product) AIX 10.2.1 License Type - Enterprise wide license License expiry date - 12/31/2011 Product- IBM Load balance manager Vendor - IBM OS – UNIX based Model/Type – IBM P7xx Serial Number – 1S4568 Processor Type - RISC Power p5 Number of Processors - 4 way Memory - 8GB Hard drive - 4 TB IP - 11.xx.xx.xx Name – Balancer Vendor - IBM Server Type – eServer Clustered – No No. of Nodes – N/A Server logical address - [email protected] Maintenance Window – Sun 0100 to 0300 Load balancing SOFTWARE PHYSICAL SOFTWARE LOGICAL HARDWARE PHYSICAL HARDWARE LOGICAL TECH FUNCTION D
- 93. ©2009 The Open Group, All Rights Reserved93 Example System/Technology Matrix •Application Server ([email protected], [email protected]) •Order Entry (both installation and execution code) •Shopping Cart (both installation and execution code) Commerce Engine Web Server cluster ([email protected], [email protected], [email protected]) HTML code Applets JSP Commerce pages Load balancing server ([email protected]) Smart dispatch v1.2 (both installation and execution code) Load Balancer TECHNOLOGY COMPONENTDEPLOYMENT UNITAPPLICATION COMPONENT D
- 94. ©2009 The Open Group, All Rights Reserved94 Diagrams • Environments and Locations diagram • Platform Decomposition diagram • Processing diagram • Networked Computing/Hardware diagram • Communications Engineering diagram D
- 95. ©2009 The Open Group, All Rights Reserved95 Environments and Locations Diagram • Depicts which locations host which applications • Identifies what technologies and/or applications are used at which locations • Identifies the locations from which business users typically interact with the applications. • It should also show the existence and location of different deployment environments – including non-production environments, such as development and pre production. D
- 96. ©2009 The Open Group, All Rights Reserved96 Example Environments and Locations Diagram loc-Italia loc-Japan loc- Stuttgart loc-USA loc- Ludwigsburg tec-OCR tec-Windows XP tec-Windows Vista tec-RDB loc- Ludwigsburg app-Project managment systemapp- CAD/CAE app-R&D system of systems app-integration platform for suppliers(dexis ) loc-Italia loc-Japan loc- Ludwigsburg app- Build-to- Order (BTO) D
- 97. ©2009 The Open Group, All Rights Reserved97 Platform Decomposition Diagram • The Platform Decomposition diagram depicts the technology platform that supports the operations of the Information Systems Architecture. • The diagram covers all aspects of the infrastructure platform and provides an overview of the enterprise's technology platform. D
- 98. ©2009 The Open Group, All Rights Reserved98 Platform Decomposition (Application Support) Hardware Physical Technology Components Tech Function Example Platform Decomposition Diagram Logical Technology Components Tech Function Application Layer Database Layer Web server layer Application Layer Database Layer Attributes • Name • Model/Type • Clusters • Number of Components • Vendor • Server Type (mainframe, Mid range, RISC, Intel) • Server logical name • IP Address etc Software Logical Technology Components Physical Technology Components Tech Function Attributes Product Name Vendor OS SW components License Type License Expiry etc Web Server Layer Web Server Layer Application Layer Database Layer Tech Function Application Layer Web Server Layer Database Layer D
- 99. ©2009 The Open Group, All Rights Reserved99 Processing Diagram • The Processing diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform. • The Processing diagram addresses the following: – Which set of application components need to be grouped to form a deployment unit – How one deployment unit connects/interacts with another (LAN, WAN, and the applicable protocols) – How application configuration and usage patterns generate load or capacity requirements for different technology components • The organization and grouping of deployment units depends on separation concerns of the presentation, business logic, and data store layers and service-level requirements of the components. D
- 100. ©2009 The Open Group, All Rights Reserved100 Example Processing DiagramD
- 101. ©2009 The Open Group, All Rights Reserved101 Network Computing Hardware Diagram • The purpose of this diagram is to show the "as deployed" logical view of logical application components in a distributed network computing environment. • The diagram is useful for the following reasons: – Enable understanding of which application is deployed where – Establishing authorization, security, and access to these technology components – Understand the Technology Architecture that support the applications during problem resolution and troubleshooting – Isolate performance problems encountered and perform necessary upgrade to specific physical technology components – Identify areas of optimization – Enable application/technology auditing and prove compliance – Serve as an important tool supporting effective change management D
- 102. ©2009 The Open Group, All Rights Reserved102 Example Network Computing Hardware Diagram Load Balancer and Dispatcher Web server clusterWeb server cluster Web server cluster- node 3 (ABM) Application Server cluster (node 3)Application Server cluster (node 3)App Server cluster - node 3 (ABM) Database (ABM Production) Web server cluster Web server cluster-node 2 (eCommerce) Application Server (Order Engine) Database Database (ABM Staging) App Server Load Balancer and Dispatcher Intranet ZoneInternet ZoneDMZ DB App Server DFS Distributed File System (html, images) Firewall Firewall Firewall D
- 103. ©2009 The Open Group, All Rights Reserved103 Communications Engineering Diagram • The Communications Engineering diagram describes the means of communication between assets in the Technology Architecture • It takes logical connections between client and server components and identifies network boundaries and network infrastructure required to physically implement those connections. • It does not describe the information format or content, but addresses protocol and capacity issues. D
- 104. ©2009 The Open Group, All Rights Reserved104 DMZ LAN Internet Cradle / USB Cable Mobile Device OBMG Proprietary Protocol (Encrypted) OBMG Proprietary Protocol (Encrypted) MS Exchange Mail Synch Protocol OBMG DMZ Proxy GPRS (OBMG / Encrypted) Mobile Device Port xxx Opened on Firewall Port xxx Opened on Firewall OBMG Proprietary Protocol (Encrypted) Desktop PC (OBMG Desktop Proxy) OBMG Proprietary Protocol (Encrypted) Auth Protocol OBMG Server Auth Protocol Active Directory Microsoft Exchange KEY Network Networ k Area User Client PC Mobile Device Firewall Data Store Network Linking Device Server Example Communications Engineering Diagram D
- 105. ©2009 The Open Group, All Rights Reserved105 Requirements Management Catalogs, Matrices and Diagrams Catalogs • Requirements Catalog Matrices Diagrams R
- 106. ©2009 The Open Group, All Rights Reserved106 CatalogsR The Requirements catalog captures things that the enterprise needs to do to meet its objectives. Requirements generated from architecture engagements are typically implemented through change initiatives identified and scoped during Phase E (Opportunities & Solutions). Requirements can also be used as a quality assurance tool to ensure that a particular architecture is fit-for-purpose (i.e., can the architecture meet all identified requirements). The Requirements catalog contains the following metamodel entities: * Requirement * Assumption * Constraint * Gap Requirements Catalog PurposeCatalog