Architecting and designing : TOGAF : Building deliverables for the TOGAF Architecture Development Method : Building deliverables for phase B: Business architecture : Creating business footprint diagrams
  
Creating business footprint diagrams
The business footprint diagram is built during Phase B: Business Architecture of the TOGAF ADM. It provides a high-level view of the people and technologies involved with key business functions.
Prerequisite
This diagram presents a global picture of the interrelationships of the following artifacts; before building this diagram, you should already have created the following definition types as part of your architecture:
▪Business Services
▪Organizational Function (see Organizational Functions in functional hierarchy diagrams)
▪Business Goal (see Relating Business Goals to Business Objectives by using a matrix)
▪Logical Technology Components
▪Organizational Unit (see Organizational Units in enterprise architecture modeling)
▪Physical Technology Components
▪Technology component
Relate the artifacts above to one another appropriately, using properties within their definition, and also by using the following matrices:
▪Goal to Organization Unit
▪Organization Unit owns Functions
▪Organization Unit owns Business Services
Within the business footprint diagram, you establish a global look of the following items:
▪who owns or governs your Business Functions, Services, and Goals
▪how your Business Functions, Services, and Goals are implemented on Logical Technology Components
▪how your Logical Technology Components are related to Physical Technology Components.
Procedure
1 Create a new diagram of type Explorer using standard techniques to create a new diagram.
2 In the TOGAF 9 Viewpoint property, select Business Footprint Diagram from the list.
3 With the diagram open and in focus, select View > Heat Map Manager to access the sets of analytics that you can run on the diagram to build the view.
4 Populate the diagram with pertinent artifacts by running one or more of the provided Explorer Object Reports. For this diagram, the following are available:
▪Business Services
▪Organizational Function (see Organizational Functions in functional hierarchy diagrams)
▪Business Goal (see Relating Business Goals to Business Objectives by using a matrix)
▪Logical Technology Components
▪Organizational Unit (see Organizational Units in enterprise architecture modeling)
▪Physical Technology Components
▪Technology component
5 Show interrelationships between artifacts by running one or all of the following Explorer Relationship Reports from the Heat Map Manager:
▪Business Service to Technology Component
▪Function to Logical Technology Component
▪Function to Organization Unit
▪Function to Physical Technology Component
▪Function to Technology Component
▪Goal to Logical Technology Component
▪Goal to Physical Technology Component
▪Goal to Technology Component
▪Organization Unit to Business Service
Next
You can generate ancillary Explorer Relationship reports. The following reports are generic and are available in the Heat Map Manager of all Explorer diagrams:
▪All Immediate Uses Relationships
▪Business Processes Related to Org Units
▪Diagram Depicts
▪IDEF0 Hierarchies