Sample Catalogs, Matrices and Diagrams v2.02: 7 April 2011 Download the bundle from

Transcription

1 Sample atalogs, Matrices and Diagrams v2.02: 7 April 2011 Download the bundle from V9 Edition opyright All rights reserved Published by The Open Group, 2011 The Open Group gratefully acknowledges the contributions from SAP and apgemini Sample atalogs, Matrices and Diagrams 2 TOGAF is a registered trademark of The Open Group in the United States and other countries opyright , The Open Group 1

2 Objectives The objectives of this presentation are to illustrate: TOGAF 9 atalogs, 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 Preliminary Phase Principles catalog TOGAF 9 atalogs, Matrices and Diagrams Phase A, Architecture Vision Stakeholder Map matrix Value hain diagram Solution oncept diagram Phase B, Business Architecture Organization/Actor catalog Driver/Goal/Objective catalog Role catalog Business Service/Function catalog Location catalog Process/Event/ontrol/Product catalog ontract/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-ase diagram Organization Decomposition diagram Process Flow diagram Event diagram Phase, Data Architecture Data Entity/Data omponent catalog Data Entity/Business Function matrix System/Data matrix lass diagram Data Dissemination diagram Data Security diagram lass Hierarchy diagram Data Migration diagram Data Lifecycle diagram Phase, Application Architecture Application Portfolio catalog Interface catalog System/Organization matrix Role/System matrix System/Function matrix Application Interaction matrix Application ommunication diagram Application and User Location diagram System Use-ase diagram Enterprise Manageability diagram Process/System 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 omputing/hardware diagram ommunications Engineering diagram Phase E. Opportunities & Solutions Project ontext diagram Benefits diagram Requirements Management Requirements catalog 4 opyright , The Open Group 2

3 P Preliminary Phase atalogs, Matrices and Diagrams atalogs Principles atalog Diagrams Matrices 5 P atalog Principles atalog atalogs Purpose The Principles catalog captures principles of the business and architecture principles that describe what a "good" solution or architecture should look like. Principles are used to evaluate and agree an outcome for architecture decision points. Principles are also used as a tool to assist in architectural governance of change initiatives. The Principles catalog contains the following metamodel entities: * Principle 6 opyright , The Open Group 3

4 A Architecture Vision atalogs, Matrices and Diagrams atalogs Matrices Stakeholder Map Matrix Diagrams Value hain Diagram Solution oncept Diagram 7 A Stakeholder xo Example Stakeholder Map Matrix Involvement 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 lass Keep Satisfied Relevant Artifacts Business Footprint Goal/Objective/Service Model Organization hart Program Management Office This stakeholder group is interested in prioritizing, funding, and aligning change activity. An understanding of project content and technical dependencies adds a further dimension of richness to portfolio management and decision making. Keep Satisfied Roadmaps Business Footprint Application ommunication Functional Decomposition HR Key features of the enterprise architecture are roles and Actors that support the functions, applications, and technology of the organization. HR are important stakeholders in ensuring that the correct roles and actors are represented. Keep Informed Organization hart Organization/Actor/ Location 8 opyright , The Open Group 4

5 A Example Value hain Diagram Source: Wikipedia.org 9 A Value hain Diagram Product & Offer Sales Fulfilment Payments Servicing 10 opyright , The Open Group 5

6 A Value hain Diagram 11 A Example Solution oncept Diagram A high-level representation of the solution envisaged A pencil sketch of the expected solution at the outset of the engagement ustomers Interest, consideration, join, re-new Membership onference Attendance ertification Publication Reliable, 24x7, self-service infrastructure 12 opyright , The Open Group 6

7 A Solution oncept Diagram 13 A Solution oncept Diagram Today s use of channels Tomorrow s use of channels High Value Tasks RM SERVIE TEAM RM From RM to ST SERVIE TEAM From Service From RM Team to to ALL ENTER ALL ENTER From all entre to Online From Service Team to Online From RM to Online SELF SERVIE INTERNET PORTAL SELF SERVIE INTERNET PORTAL Low Value Tasks 14 opyright , The Open Group 7

8 B Business Architecture atalogs, Matrices and Diagrams atalogs Organization/Actor catalog Driver/Goal/Objective catalog Role catalog Business Service/Function catalog Location catalog Process/Event/ontrol/Product catalog ontract/measure catalog Matrices Business Interaction matrix Actor/Role matrix Diagrams Business Footprint diagram Business Service/Information diagram Functional Decomposition diagram Product Lifecycle diagram Goal/Objective/Service diagram Business Use-ase diagram Organization Decomposition diagram Process Flow diagram Event diagram 15 B atalogs atalog Organization/ Actor atalog Driver/Goal/ Objective atalog Role atalog Purpose A definitive listing of all participants that interact with IT, including users and owners of IT systems. It contains the following metamodel entities: Organization Unit, Actor Location (may be included in this catalog if an independent Location catalog is not maintained) 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) 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 16 opyright , The Open Group 8

9 B atalog Business Service / Function atalog Location atalog Process/ Event/ ontrol/ Product atalog atalogs Purpose 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) 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 The Process/Event/ontrol/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, ontrol, Product 17 B atalog ontract/ Measure atalog atalogs Purpose A listing of all agreed service contracts and (optionally) the measures attached to those contracts. It forms the master list of service levels agreed to across the enterprise. It contains the following metamodel entities: Business Service Information System Service (optionally) ontract Measure 18 opyright , The Open Group 9

10 B Matrices Business Interaction matrix Actor/Role matrix 19 B Business Interaction Matrix The purpose of this matrix is to depict the relationship interactions between organizations and business functions across the enterprise. Providing Business Services onsuming Business Services Engineering Procurement Manufacturing Sales and Distribution ustomer Service Engineering Procurement Manufacturing Sales and Distribution ustomer Service ontract for supply of product specification ontract for supply of materials 20 ontract for supply of product ontract for supply of sales forecasts ontract for fulfillment of customer orders opyright , The Open Group 10

11 B Actor/role Matrix The purpose of this matrix is to show which actors perform which roles, supporting definition of security and skills requirements. Office of IO Actors Steering Group Actors Business Unit Actors Strategy and Architecture Actors Infrastructure Implementation Actors IO Enterprise Architect Enterprise Design Authority Technical Design Authority IT Management Forum Business Unit Head R = Responsible for carrying out the role A = Accountable for actors carrying out the role = onsulted in carrying out the role I = Informed in carrying out the role Strategy Lifecycle Roles Architecture Refresh I R A I R I I R I Architecture Roadmap I A I R I R I I R I Benefits Assessment I I I I I I I I I R R I A hange Management I A I I I R I I I R R Framework Refresh I A I I I R I Project Lifecycle Roles Solution Architecture Vision I I I A I I I I R I R Logical Solution Architecture A I I I I R I R Physical Solution Architecture A I I I I R I R R Design Governance A I I I I R I R Architecture onfiguration Management I I R R R A Business Unit Service Owner Business Unit Application Architect Head of Strategy and Architecture Infrastructure Strategist Infrastructure Solution Architect Architecture onfiguration Manager Enterprise Infrastructure Architect Head of Implementation Infrastructure Designer IT Operations Project Manager External Vendors / Suppliers 21 B Diagrams Business Footprint diagram Business Service/Information diagram Functional Decomposition diagram Product Lifecycle diagram Goal/Objective/Service diagram Business Use-ase diagram Organization Decomposition diagram Process Flow diagram Event diagram 22 opyright , The Open Group 11

12 B Business Footprint Diagram Describes the links between business goals, organizational units, business functions, and services, and maps these functions to the technical components delivering the required capability. Demonstrates only the key facts linking organization unit functions to delivery services and is utilized as a communication platform for senior-level (xo) stakeholders 23 B Example Business Footprint Diagram 24 opyright , The Open Group 12

13 B Business Footprint Diagram Business Process Integration Layer 0 Orderto-ash Order Manage Receive Process Distribute Invoice Accounts Order Order Goods / Services ustomer Receivable ash Store Operations Support Services Supply hain Mgmt Functional Services Layer User Management Layer Buyer Portal Employee Portal Exchanges Supplier Portal ustomer Portal Partner Portal Others 25 B Business Footprint Diagram S1 Plan & manage the demand S2 Plan sales & operations S3 Establish inventory plan S4 Define manufacturing plan S5 - Plan goods movements and resources in the distribution network S6 Schedule & execute goods movements, storage and transportation decisions S11 - Monthly Forecast Generation S12 - Monthly Forecast ollaboration S17 Forecast Weekly Update S16 Demand explosion for assembly S13 Planned demand consumption by customer order S14 Allocation Definition Rules for ATP (monthly) S15 Allocation Definition Rules for ATP (daily) S0 - Referential S22 ross-uot Demand & Supply Balancing S51 Logistics apacity S61 Warehouse and LP S&OP validation Planning Management S52 Distribution Supply Planning mid- S62 Long Distance S21 UOT and LPS Tactical Supply Planning Term Transportation S42 Multi-Plant S53 Distribution S32 Inventory Planning Supply Planning short- S63 Short-Distance Management Rules Term Transportation Parameter Definition S54 - Distribution shortage management GFB57- Process steps S41 Plant traceability Production Planning S55 Deployment S65 Transportation S56 Intra-group administration exchanges management GFB58 Product S57 Procurement Traceability exchanges management S70 - Inventory Management (physical and planned inventory including internal transfer orders) S04 - Inventory Norms Definition GFB64 - Supply hain osts & Margin Referential GFB63 Demand Planning Referential GFB61 Supply hain Referential Logistics GFB62 Supply hain Referential Production Process Model Resource GFB65 - Supply hain Referential Production & Distribution & Ship to ustomer Network S9 -BI S91 Demand BI / Reporting S92 Tactical Planning BI / Reporting GFB59 Product & Services lient atalog GFB50 Product & Services Referential GFB51 - lient Referential S93 Inventory BI / S94 Plant Planning BI Reporting / Reporting GFB70 Global ross-domain Reporting & Analysis 26 S95 Distribution Planning BI / Reporting S96 Logistics BI / Reporting opyright , The Open Group 13

14 B Business Footprint Diagram 27 B 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 (Data Architecture). 28 opyright , The Open Group 14

15 B Example Business Service/Information Diagram Basic example 29 B Example Business Service/Information Diagram Extended example showing actors and service interactions 30 opyright , The Open Group 15

16 Business Services and Information Diagram 31 Business Services and Information Diagram 32 opyright , The Open Group 16

17 B Functional Decomposition Diagram It shows on a single page the capabilities of an organization that are relevant to the consideration of an architecture. By examining the capabilities of an organization from a functional perspective, it is possible to quickly develop models of what the organization does without being dragged into extended debate on how the organization does it. 33 B Example Functional Decomposition Diagram 34 opyright , The Open Group 17

18 B Functional Decomposition Diagram Support Primary Admin Finance Human Business Marketing Resources Planning & Engineering Inventory Manufacturing Distribution Sales Manage Public Relations Develop & Track Financial Plan Plan Human Resources Formulate Strategy Develop New Business Research and Develop Technology Plan Material Requirements Plan Manufacturing Requirements Engineer Packages Provide Legal Services Appropriate Funds Acquire Human Resources Develop and Maintain Business Plan Establish ustomer Requirements Engineer and Design Products Procure Equipment Material & Tools Perform Quality Engineering Ship Products Perform Audit & ontrols Develop & Manage Product ost Develop Employees Obtain Sales ommitments Engineer and Design Processes Manage Suppliers onvert Resources to Product Manage Transportation Manage Payables Provide Employee Services Provide ustomer Support Design Tools and Equipment Manage Inventory ontrol Production Maintain Facilities Manage Receivables Manage Union Activities Manage Engineering hanges Maintain Plant Equipment & Tools Provide Administrative Services Manage Assets Terminate Active Employment Manage Warranty Activities 35 B Product Lifecycle Diagram This assists in understanding the lifecycles of key entities within the enterprise. Understanding product lifecycles is becoming increasingly important with respect to environmental concerns, legislation, and regulation where products must be tracked from manufacture to disposal. Equally, organizations that create products that involve personal or sensitive information must have a detailed understanding of the product lifecycle during the development of Business Architecture in order to ensure rigor in design of controls, processes, and procedures. Examples of this include credit cards, debit cards, store/loyalty cards, smart cards, user identity credentials (identity cards, passports, etc.). 36 opyright , The Open Group 18

19 B Example Product Lifecycle Diagram Source: Kotler and Armstrong, B Example Product Lifecycle Diagram 38 opyright , The Open Group 19

20 B Goal/Objective/Service Diagram This defines the ways in which a service contributes to the achievement of a business vision or strategy. Services are associated with the drivers, goals, objectives, and measures that they support, allowing the enterprise to understand which services contribute to similar aspects of business performance. This also provides qualitative input on what constitutes high performance for a particular service. 39 B Example Goal/Objective/ Service Diagram gol-increase revenues rol-fo rol-vp Marketing rol-vp Sales obj-"aftersales" market obj-creating new line of cars by the end of... Functionsales and marketing c a p - M a rk e t in g cap-pre- O w n e d ve h ic a... c a p - ca m paign c a p - S a l e s cap-pre-sale 40 c a p - O r d e r- to - D e live r y opyright , The Open Group 20

21 B Business Use-case Diagram This displays the relationships between consumers and providers of business services. Business services are consumed by actors or other business services and the Business Use-ase 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. 41 B Example Use-case Diagram 42 opyright , The Open Group 21

22 B 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. 43 B Example Organization Decomposition Diagram rol-eo org-worldwide Public Affairs and Policy org-hief Medical Officer org-global Research & Development rol-vice hairman rol-wolrdwide Pharmaceutical Operations org-wolrdwide talent Development and HR org-general ounsel rol-field Based Govt. Relations rol-wolrdwide Medical rol-wolrdwide Research rol-global Manufacturing loc-us rol-talent Development rol-intellectual Property rol-fo rol-wolrdwide ommunications rol-safety Risk Management rol-worldwide Development rol-worlwide Strategic Planning loc-japan/asia rol-healthwelness rol-employment Law rol-philanthropy/stakeholder Advocacy rol-science Advocacy rol-worldwide Research Affairs rol-animal Health loc-europe rol-planning rol-line Support rol-worldwide Policy rol-financial Strategy rol-worldwide Licensing and Business Develoment rol-diversity and Inclusion rol-litigation/regulatory rol-federal Government relations rol-human Resources rol-wolrdwide Technology loc-middle East rol-compensation and Benefits rol-business Transactions rol-business Services rol-omplinace Officer loc-anada rol-site Leader(s) rol-wolrdwide Investor Development rol-internal Audit 44 opyright , The Open Group 22

23 B Process Flow Diagram This depicts all models and mappings related to the process metamodel entity. It shows sequential flow of control between activities and may utilize swim-lane techniques to represent ownership and realization of process steps. In addition to showing a sequence of activity, process flows can also be used to detail the controls that apply to a process, the events that trigger or result from completion of a process, and also the products that are generated from process execution. 45 B Example Process Flow Diagram Start Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 6 Step 6 STOP 46 opyright , The Open Group 23

24 B Technical Support Team Example Process Flow Diagram Sales Rep Pricer Pricer Start Step 1 Step 2 Step 3 Step 4 ustom app RM MS Word MS Excel ustom Bid Approver ustomer Rep ustomer Rep ustomer Rep Step 5 Step 6 Step 6 Step 6 STOP IWF onsolidation Tool Spreadsheet Process Flow (w/roles & Applications) 47 B Events Diagram This depicts the relationship between events and process. ertain 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. 48 opyright , The Open Group 24

25 B Example Events Diagram Event Triggers Process Impacts/Generates Business result (e.g. End of Fiscal Quarter) (e.g. Financial Reporting Process) (e.g. 1Q results reported to Government Agencies) 49 B Example Events Matrix EVENT PROESS TRIGGERED BUSINESS RESULT(S) ustomer submits sales order Sales order processing reate & save sales order Generate acknowledgement onfirm receipt of customer order Begin order fulfilment activities Sales order captured in order book ustomer submits request for custom product ustom product configuration apture requirements from customer Define custom specifications Price custom configuration Negotiate with customer Secure approval from customer regarding configuration and price ustom product configured ustomer contract signed End of quarter Financial reporting process Financial report generated 50 opyright , The Open Group 25

26 Data Architecture atalogs, Matrices and Diagrams atalogs Data Entity/Data omponent catalog Matrices Data Entity/Business Function matrix System/Data matrix Diagrams lass diagram Data Dissemination diagram Data Security diagram lass Hierarchy diagram Data Migration diagram Data Lifecycle diagram 51 atalogs atalog Data Entity/Data omponent atalog Purpose To identify and maintain a list of all the data use across the enterprise, including data entities and also the data components where data entities are stored. It contains the following metamodel entities: Data Entity Logical Data omponent Physical Data omponent 52 opyright , The Open Group 26

27 Matrices Data Entity/Business Function matrix System/Data matrix 53 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.) 54 opyright , The Open Group 27

28 Example Data Entity/Business Function Matrix BUSINESS FUNTION (Y-AXIS) AND DATA ENTITY (X-AXIS) USTOMER MASTER BUSINESS PARTNER USTOMER LEADS PRODUT MASTER ustomer Relationship Management Business partner data management service Owner Sales & Marketing business unit executive Function can reate, read, update and delete customer master data Business partner data management service Owner of data entity (person or organization) Function can reate, read, update and delete Lead Processing Service Owner ustomer Relationship Manager Function can only reate, read, update customer leads N/A Supply hain Management ustomer Requirement Processing Service Owner Supply hain Manager N/A N/A Product data management service Owner Global product development organization 55 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 RM application will create, read, update, and delete customer entity information. 56 opyright , The Open Group 28

29 Example System/Data Matrix APPLIATION (Y- AXIS) AND DATA (X-AXIS) DESRIPTION OR OMMENTS DATA ENTITY DATA ENTITY TYPE RM System of record for customer master data ustomer data Master data ommerce Engine System of record for order book Sales orders Transactional data Sales Business Warehouse Warehouse and data mart that supports North American region Intersection of multiple data entities (e.g. All sales orders by customer XYZ and by month for 2006) Historical data 57 Diagrams lass diagram Data Dissemination diagram Data Security diagram lass Hierarchy diagram Data Migration diagram Data Lifecycle diagram 58 opyright , The Open Group 29

30 lass Diagram The purpose is to depict the relationships among the critical data entities (or classes) within the enterprise. Account I.A1 Information Update Account P.A12 ustomer Profile I.2 Actor Trigger ontact P.S13 Payment T.P8 Agent A.A4 ustomer A.2 ustomer Information I.1 59 P.S5 Service Request Appeal T.19 Process Enquiry omplaint T.1 T.16 lass Diagram 60 opyright , The Open Group 30

31 lass Diagram 61 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. 62 opyright , The Open Group 31

32 Example Data Dissemination Diagram Warehouse Warehouse ustomer Order History Stock Online Online Account Account Self Service Self Service Billing Billing ustomer Account Balance Invoice History Business Service Online Account Self Service Data Entities ustomer Order History Stock Account Balance Invoice History Application Warehouse Billing Warehouse Warehouse Billing Billing 63 Data Dissemination Diagram 64 opyright , The Open Group 32

33 Data Dissemination Diagram 65 Data Dissemination Diagram 66 opyright , The Open Group 33

34 Data Lifecycle Diagram The Data Lifecycle diagram is an essential part of managing business data throughout its lifecycle from conception until disposal within the constraints of the business process. Fulfilment Order New Fulfilled Invoiced Paid losed Archived Deleted ustomer Order New Dispatched losed Archived Deleted 67 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. 68 opyright , The Open Group 34

35 Example Data Security Diagram lass of Roles (by job function) Actor Business Function Process Physical Access Single Sign-on or Access ontrol Location Business Service Access ontrol (levels of granularity) Access ontrol (levels of granularity) Logical Application omponent 69 Example Data Security Matrix ATOR LASS OF ROLES (JOB FUNTION) FUNTION BUSINESS SERVIE LOATION TYPE OF AESS Financial Analyst SOA Portfolio Financial Analyst Financial Analysis SOA portfolio service NA (US, A) EMEA (UK, DE) APJ Physical Access ontrol (tables xyz only) Procurement & Spend Analyst Procurement Management and ontrol WW Direct Procurement Supplier portal Service NA (US Midwest) Access control WW ontracts System (application) Not applicable WW Direct Procurement Supplier Portal Service LA Access control (system to system) WW Product Development (Org Unit) Geo Brand Managers WW Direct Procurement Supplier Portal Service WW (all Geos) Access ontrol 70 opyright , The Open Group 35

36 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. 71 Example Data Migration Diagram Baseline application components ABM Source of ustomer records B Data migration technology components Target application components RM System of Record for ustomer Master 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 VL (one per geo) Source of vendor data System of Record for Vendor Master & ontracts 72 opyright , The Open Group 36

37 Example Data Migration Mapping SOURE LOGIAL APPLIATION OMPONENT SOURE DATA ELEMENT TARGET LOGIAL APPLIATION OMPONENT TARGET DATA ELEMENT ABM ust_name RM USTNAME ust_street_addr USTADDR_LINE1 ust_street_addr USTADDR_LINE2 ust_street_addr USTADDR_LINE3 ust_ontactname USTONTAT ust_tele USTTELEPHONE 73 lass Hierarchy Diagram The purpose of the lass 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. 74 opyright , The Open Group 37

38 Example lass Hierarchy Diagram Authorised User Authorised User Keeper Keeper Vehicle Tester Vehicle Tester Individual Individual ustomer ustomer Purchaser/Nominee Purchaser/Nominee Trainer/Booker Trainer/Booker Driver Driver Organisation Organisation Manufacturer Manufacturer Driving Driving Instructor Instructor Operator Operator Taxi Driver Taxi Driver Dealing Dealing Driving Examiner Driving Examiner Driving Examiner Driving Examiner 75 Application Architecture atalogs, Matrices and Diagrams atalogs Application Portfolio catalog Interface catalog Matrices System/Organization matrix Role/System matrix System/Function matrix Application Interaction matrix Diagrams Application ommunication diagram Application and User Location diagram System Use-ase diagram Enterprise Manageability diagram Process/System Realization diagram Software Engineering diagram Application Migration diagram Software Distribution diagram 76 opyright , The Open Group 38