Chapter 31. TOGAF ADM Guide-Through

  1. Home
  2. Docs
  3. Chapter 31. TOGAF ADM Guide-Through
  4. 7. Phase D – Technology Architecture
  5. Architecture Definition Document

Architecture Definition Document

Architecture Definition Document is one of the TOGAF deliverables you can create with the TOGAF software.

This document describes the baseline and target technology architecture, and gap analysis for your project. It contains the core architectural artifacts created during a project.

The Architecture Definition Documents produces in phase B, C and D span all architecture domains (business, data, application, and technology) and also examines all relevant states of the architecture (baseline, interim state(s), and target).

The Architecture Definition Documents are a companion to the Architecture Requirements Specification, with a complementary objective:

  • The Architecture Definition Documents provide a qualitative view of the solution and aims to communicate the intent of the architects.
  • The Architecture Requirements Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture.

Step 1: Identify the Responsibilities of Stakeholders for the Technology Architecture

Describe the responsibilities of stakeholders with regards to the technology architecture

Describe the responsibilities of the stakeholders for the technology architecture. The stakeholders were defined in a previous activity. You only need to fill-in their responsibilities here.

Step 2: Develop Baseline Technology Architecture

Model the baseline technology architecture

Define the current Technology Architecture that is in scope for this exercise. You may create an ArchiMate Diagram to serve this purpose. While it’s more common to use ArchiMate Diagram to visualize an architecture, you can add other types of diagrams you want to present the architecture information from a set of different perspectives (viewpoints) according to the requirements of the stakeholders.

TOGAF Architecture Definition: Baseline Technology Architecture

Step 3: Develop Target Technology Architecture

Model the target technology architecture

Define the target Data Architecture that is in scope for this exercise. Draw an Architecture Diagram to illustrate the deployment models and platforms to be installed and the environments that the platforms required to operate.

TOGAF Architecture Definition: Target Technology Architecture

Analyze and describe the gaps between baseline and target technology architecture

Define the gap between the current (as-is) and target (to-be) state Technology Architecture. The gap defined here will aid in the definition of the scope of work that needs to be undertaken in order to transition from the current to the target Technology Architecture. You are required to describe the gap by mean of an ArchiMate diagram, and to fill-in a form that explains the gap from various potential sources of technology domain gap.

TOGAF Architecture Definition: Technology Domain Gap Analysis

Step 5: Perform Impact Analysis

Describe the impacts associated with the technology architecture

Assess and document the impact (on the organization) of the change required in order to transition from the current to the target state Technology Architecture. Make sure the description is sufficient enough for the organization to determine the change management requirements for program(s)/project(s).

Step 6: Finalize Architecture Definition Document

Complete the form of ‘Architecture Definition Document’

You are about to finish the development of Technology Architecture portion of the Architecture Definition Document. To end, complete the form of Architecture Definition Document by providing the information required, such as the architecture objectives, stakeholders, constraints and compliance details. Information that had been provided in previous phases and activities are pre-populated. You only need to fill-in the empty fields and make necessary modifications on those pre-populated fields.