Architecture Definition Document is one of the TOGAF deliverables you can create with the TOGAF software.
This document describes the baseline and target information systems architectures 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 Information Systems Architectures
Describe the responsibilities of stakeholders with regards to the information systems architectures
Describe the responsibilities of the stakeholders for the information systems architectures. The stakeholders were defined in a previous activity. You only need to fill-in their responsibilities here.
Step 2: Develop Baseline Data Architecture
Model the baseline data architecture
Define the current Data Architecture that is in scope for this exercise. 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.
Step 3: Develop Target Data Architecture
Model the target data architecture
Define the target Data Architecture that is in scope for this exercise. Again, you may create multiple diagrams for this purpose. The Target Data Architecture provides the details of a future state of an architecture being developed. Draw a diagram that shows how the logical entities are to be physically realized by application components. This allows you to validate whether the proposed target architecture will fulfill the business needs.
Step 4: Develop Baseline Application Architecture
Model the baseline application architecture
Define the current Application Architecture that is in scope for this exercise. 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.
Step 5: Develop Target Application Architecture
Model the target application architecture
Define the target Application Architecture that is in scope for this exercise. Again, you may create multiple diagrams for this purpose. The Target Application Architecture provides the details of a future state of an architecture being developed. This allows you to validate whether the proposed target architecture will fulfill the business needs.
Step 6: Perform Gap Analysis
Analyze and describe the gaps between baseline and target data and application architecture
Define the gap between the current (as-is) and target (to-be) state Data and Application Architectures. 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 data and application domain gap.
Step 7: Perform Impact Analysis
Describe the impacts associated with the data and application architecture
Assess and document the impact (on the organization) of the change required in order to transition from the current to the target state Data and Application Architectures. Make sure the description is sufficient enough for the organization to determine the change management requirements for program(s)/project(s).
Step 8: Finalize Architecture Definition Document
Complete the form of ‘Architecture Definition Document’
You are about to finish the development of Information Systems Architectures 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.