TOGAF Deep Dive: Deliverables and Artifacts

Introduction Key Concepts Deliverables Artifacts Best Practices FAQ

Introduction

In the context of Enterprise Architecture Frameworks, particularly TOGAF (The Open Group Architecture Framework), deliverables and artifacts play a crucial role in the successful implementation of architecture projects. This lesson provides an in-depth exploration of these concepts.

Key Concepts

Definitions

Deliverables: Tangible outcomes or outputs produced during the architecture development process, including reports, models, and specifications.
Artifacts: Supporting documents and materials that provide evidence of the architecture process and decisions made.

Deliverables

Deliverables in TOGAF are categorized into several phases of the Architecture Development Method (ADM). Each phase results in specific deliverables that contribute to the overall architecture.

Examples of Deliverables

Architecture Vision Document
Business Architecture Document
Information Systems Architecture Document
Technology Architecture Document
Implementation and Migration Plan

Artifacts

Artifacts are essential for documenting the architecture process and outcomes, ensuring that stakeholders have the necessary information to make informed decisions.

Common Artifacts

Architecture Models (e.g., UML diagrams, flowcharts)
Architecture Principles Document
Stakeholder Concerns List
Capability Models

Best Practices for Deliverables and Artifacts

Tip: Always ensure that deliverables and artifacts are aligned with business goals and stakeholder needs.

Here are some best practices to consider:

Engage stakeholders early and often to gather requirements.
Maintain a clear structure and format for deliverables and artifacts.
Regularly review and update documents to ensure relevance.
Utilize templates to maintain consistency across projects.

FAQ

What is the difference between deliverables and artifacts?

Deliverables are the final outputs of architecture work, while artifacts are the materials that support and document that work.

How often should deliverables be updated?

Deliverables should be updated regularly, especially at the end of each ADM phase or if significant changes occur.

Can artifacts be reused across different projects?

Yes, well-documented artifacts can often be reused in different projects, saving time and effort.

Deliverables and Artifacts Flowchart


                graph TD;
                    A[Start] --> B[Identify Stakeholders];
                    B --> C[Gather Requirements];
                    C --> D{Phase of ADM};
                    D -->|Architecture Vision| E[Create Vision Document];
                    D -->|Business Architecture| F[Create Business Document];
                    D -->|Information Systems| G[Create Info Systems Document];
                    D -->|Technology| H[Create Technology Document];
                    E --> I[Review Deliverables];
                    F --> I;
                    G --> I;
                    H --> I;
                    I --> J[Finalize and Distribute];
                    J --> K[End];