Architecting and designing : TOGAF : Building deliverables for the TOGAF Architecture Development Method : Building deliverables for phase B: Business architecture
  
Building deliverables for phase B: Business architecture
In phase B of the TOGAF Architecture Development Method (ADM) you establish the Business Architecture of the organization.
Prerequisite
See the TOGAF documentation at:
http://www.opengroup.org/architecture/togaf9-doc/arch/
Required inputs
The following inputs are required to build phase B:
Request for architecture work
Approved Statement of Architecture Work
Project definition, including scope, constraints, and the plan for the architectural work
Refined statements of Business Principles (see Principle), Business Goals (see Relating Business Goals to Business Objectives by using a matrix), and Business Drivers (see Business driver)
Architecture Principles (see Principle)
Enterprise Continuum
Architecture Vision, as specified within Statement of Architecture Work definition
Architecture Vision or Business scenario, including:
Business Baseline version 1
Technical Baseline version 1
Business Architecture version 1 (see Business architecture)
Technical architecture version 1
The objectives of building the business architecture are to understand, describe, and model the current (or baseline, or 'as is') business architecture, and then develop target, or to be business architectures. In System Architect, you can use workspaces (see Creating a workspace) to enable baseline and target architectures.
Procedure
1 Referring to step 1 of the TOGAF online documentation, select the Business Architecture resources, viewpoints, and modeling tools to use.
Select the required catalogs of your business Building Blocks.
The following catalogs are represented by definition types, accessible in the applicable grouping in the Explorer.
Organization/Actor
Driver/Goal/Objective
Role
Business Service/Function
Location
Process/Event/Control/Product
Contract/Measure
Select the required matrices.
To view or specify a matrix of Organizational Unit versus Function definition types, you can open the Business Interaction matrix.
To view or specify a matrix of Actor versus Role definition types, you can open the Business Interaction matrix.
Identify the required diagrams. You can select from the following diagrams:
Core diagrams:
Creating business footprint diagrams
Creating business service information diagrams
Functional Decomposition diagram: you can use a Functional Hierarchy diagram for this.
Product Lifecycle diagram: Assist 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.
Extension diagrams:
Creating goal/objective/service diagrams
Use Case diagram
Organization Decomposition diagram: use an Organization Chart (see Organization charts for enterprise architectures)
Process Flow diagram: use a BPMN diagram (see Introduction to BPMN)
Creating event diagrams
2 Referring to the TOGAF documentation for steps 2 and 3 of this phase, develop the baseline and target Business architecture definitions.
3 Referring to the TOGAF documentation for steps 2 through 4 of this phase, identify the architecture building blocks (see Architecture building block).
Building blocks can be represented visually in the business architecture diagram.
4 For each business architecture viewpoint, create the required models.
To document the organizational structure, identifying business locations and relating them to organizational units, create an Organizational Chart diagram.
Document Business goals and objectives for each organizational unit.
Identify and define business functions and business services by creating the associated definitions.
To document business processes, including measures and deliverables, select one of the following techniques and notations:
Enterprise Architecture Process Charts: Process charts model the business processes of the organization.
BPMN: Business Process Modeling Notation (BPMN) is a standard notation established by the Business Process Management Initiative (BPMI.org).
UML Use Cases and Activity Diagrams: All diagrams of the Unified Modeling Language (UML) are supported.
IDEF3 Process Flow diagrams: Diagrams of the IDEF methodology are supported. These are integrated with IDEF0 Functional Decomposition diagrams and IDEF1X data models.
DoDAF
Specify business roles, and related competencies, by creating Role definitions.
Specify a matrix of Organizational Unit versus Function definition types using the Business Interaction matrix.
5 Referring to the TOGAF documentation for steps 5 through 9 of this phase, finalize the business architecture by creating these diagrams:
Business footprint diagram
Business service diagram
Business architecture diagram
(see Business Architecture diagram elements and Creating business architecture diagrams for TOGAF)
See also
Diagram types for TOGAF