What is Architecture Artifacts in TOGAF ADM

Introduction

In TOGAF (The Open Group Architecture Framework) ADM (Architecture Development Method), architecture artifacts are the deliverables that capture and document the outputs of the various phases and steps in the architecture development process. These artifacts serve as a means of communication and documentation for different stakeholders involved in the architecture development.

Throughout the ADM cycle, architects create and refine these artifacts to ensure that the architecture work is well-documented and can be easily understood by others. Examples of architecture artifacts include:

1. Vision Statement: A concise description of the desired future state of the organization.
2. Business Architecture Artifacts: Business models, process diagrams, and organizational charts that represent the structure and operations of the business.
3. Data Architecture Artifacts: Data models, data flow diagrams, and data dictionaries that define how data is stored, processed, and accessed.
4. Application Architecture Artifacts: Descriptions of application components, interfaces, and interactions, often represented through diagrams.
5. Technology Architecture Artifacts: Descriptions of the technology infrastructure, including hardware, software, networks, and communication protocols.
6. Implementation and Migration Plan: A detailed plan outlining the steps and timeline for implementing the architecture.
7. Architecture Requirements Specification: A document that outlines the requirements that the architecture must address.
8. Risk Assessment: An analysis of potential risks and mitigation strategies associated with the architecture.

These artifacts provide a structured way to capture and communicate the architectural decisions and rationale, ensuring that the architecture aligns with business goals and objectives.

Architecture Deliverables vs Artifacts

In TOGAF ADM, deliverables and artifacts are closely related terms, and they refer to the tangible outputs and documentation that result from the different phases of the architecture development process. Let me break down the relationship between these two concepts:

 

Deliverables:

• Definition: Deliverables are the tangible results or outcomes of each phase in the ADM cycle.
• Purpose: They are created to provide specific inputs to subsequent phases or to meet the needs of stakeholders.
• Examples: Documents, models, plans, and other tangible outputs that convey information relevant to the architecture.

Artifacts:

• Definition: Artifacts, in the context of TOGAF, are the actual documents or models that capture and represent architectural information.
• Purpose: They serve as the tangible representations of the architecture, providing a means of communication and documentation.
• Examples: Vision statement, business models, data diagrams, technology matrices, etc.

Relationship:

Deliverables Produce Artifacts: Each phase in TOGAF ADM results in the creation of specific deliverables. These deliverables, in turn, often manifest as tangible artifacts. For example, the deliverable “Vision Statement” might be realized as an artifact in the form of a documented vision statement.

Artifacts as Inputs for Deliverables: Artifacts generated in earlier phases can serve as inputs for the creation of deliverables in subsequent phases. For instance, the business architecture artifacts may feed into the development of the Implementation and Migration Plan.

Traceability: There is a traceability relationship between deliverables and artifacts. Deliverables help ensure that the architecture development process is systematic, and artifacts provide the concrete evidence of the work done and decisions made.

Summary

Deliverables are the broader outcomes of each phase, and artifacts are the specific documents or models that embody and communicate the architectural information produced during those phases. The relationship between the two is iterative and interconnected, with artifacts often serving as both inputs and outputs in the ADM cycle.