This chapter provides descriptions of deliverables referenced in the Architecture Development Method (ADM).

32.1 Introduction

This chapter defines the deliverables that will typically be consumed and produced across the TOGAF ADM cycle. As deliverables are typically the contractual or formal work products of an architecture project, it is likely that these deliverables will be constrained or altered by any overarching project or process management for the enterprise (such as CMMI, PRINCE2, PMBOK, or MSP).

This chapter therefore is intended to provide a typical baseline of architecture deliverables in order to better define the activities required in the ADM and act as a starting point for tailoring within a specific organization.

The TOGAF Content Framework (see Part IV, 29. Introduction to Part IV) identifies deliverables that are produced as outputs from executing the ADM cycle and potentially consumed as inputs at other points in the ADM. Other deliverables may be produced elsewhere and consumed by the ADM.

Deliverables produced by executing the ADM are shown in the table below.

32.2 Deliverable Descriptions

The following sections provide example descriptions of deliverables referenced in the ADM.

Note that not all the content described here need be contained in a particular deliverable. Rather, it is recommended that external references be used where possible; for example, the strategic plans of a business should not be copied into a Request for Architecture Work, but rather the title of the strategic plans should be referenced.

Also, it is not suggested that these descriptions should be followed to the letter. However, each element should be considered carefully; ignoring any input or output item may cause problems downstream.

32.2.1 Architecture Building Blocks

Architecture documentation and models from the enterprise's Architecture Repository; see Part IV, 33. Building Blocks .

32.2.2 Architecture Contract

Purpose

Architecture Contracts are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture. Successful implementation of these agreements will be delivered through effective Architecture Governance (see Part VI, 44. Architecture Governance). By implementing a governed approach to the management of contracts, the following will be ensured:

• A system of continuous monitoring to check integrity, changes, decision-making, and audit of all architecture-related activities within the organization
• Adherence to the principles, standards, and requirements of the existing or developing architectures
• Identification of risks in all aspects of the development and implementation of the architecture(s) covering the internal development against accepted standards, policies, technologies, and products as well as the operational aspects of the architectures such that the organization can continue its business within a resilient environment
• A set of processes and practices that ensure accountability, responsibility, and discipline with regard to the development and usage of all architectural artifacts
• A formal understanding of the governance organization responsible for the contract, their level of authority, and scope of the architecture under the governance of this body

Content

Typical contents of an Architecture Design and Development Contract are:

• Introduction and background
• The nature of the agreement
• Scope of the architecture
• Architecture and strategic principles and requirements
• Conformance requirements
• Architecture development and management process and roles
• Target Architecture measures
• Defined phases of deliverables
• Prioritized joint workplan
• Time window(s)
• Architecture delivery and business metrics

Typical contents of a Business Users' Architecture Contract are:

• Introduction and background
• The nature of the agreement
• Scope
• Strategic requirements
• Conformance requirements
• Architecture adopters
• Time window
• Architecture business metrics
• Service architecture (includes Service Level Agreement (SLA))

For more detail on the use of Architecture Contracts, see Part VI, 43. Architecture Contracts .

32.2.3 Architecture Definition Document

Purpose

The Architecture Definition Document is the deliverable container for the core architectural artifacts created during a project and for important related information. The Architecture Definition Document spans all architecture domains (business, data, application, and technology) and also examines all relevant states of the architecture (baseline, transition, and target).

A Transition Architecture shows the enterprise at an architecturally significant state between the Baseline and Target Architectures. Transition Architectures are used to describe transitional Target Architectures necessary for effective realization of the Target Architecture.

The Architecture Definition Document is a companion to the Architecture Requirements Specification, with a complementary objective:

• The Architecture Definition Document provides 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

Content

Typical contents of an Architecture Definition Document are:

• Scope
• Goals, objectives, and constraints
• Architecture Principles
• Baseline Architecture
• Architecture models (for each state to be modeled):
  • Business Architecture models
  • Data Architecture models
  • Application Architecture models
  • Technology Architecture models
• Rationale and justification for architectural approach
• Mapping to Architecture Repository:
  • Mapping to Architecture Landscape
  • Mapping to reference models
  • Mapping to standards
  • Re-use assessment
• Gap analysis
• Impact assessment
• Transition Architecture:
  • Definition of transition states
  • Business Architecture for each transition state
  • Data Architecture for each transition state
  • Application Architecture for each transition state
  • Technology Architecture for each transition state

32.2.4 Architecture Principles

Purpose

Principles are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission.

In their turn, principles may be just one element in a structured set of ideas that collectively define and guide the organization, from values through to actions and results.

Content

See Part III, 20. Architecture Principles for guidelines and a detailed set of generic Architecture Principles, including:

• Business principles (see 20.6.1 Business Principles)
• Data principles (see 20.6.2 Data Principles)
• Application principles (see 20.6.3 Application Principles)
• Technology principles (see 20.6.4 Technology Principles)

32.2.5 Architecture Repository

Purpose

The Architecture Repository acts as a holding area for all architecture-related projects within the enterprise. The repository allows projects to manage their deliverables, locate re-usable assets, and publish outputs to stakeholders and other interested parties.

Content

See Part V, 37. Architecture Repository for a detailed description of the content of an Architecture Repository.

32.2.6 Architecture Requirements Specification

Purpose

The Architecture Requirements Specification provides a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture. An Architecture Requirements Specification will typically form a major component of an implementation contract or contract for more detailed Architecture Definition.

As mentioned above, the Architecture Requirements Specification is a companion to the Architecture Definition Document, with a complementary objective:

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

Content

Typical contents of an Architecture Requirements Specification are:

• Success measures
• Architecture requirements
• Business service contracts
• Application service contracts
• Implementation guidelines
• Implementation specifications
• Implementation standards
• Interoperability requirements
• IT Service Management requirements
• Constraints
• Assumptions

32.2.7 Architecture Roadmap

Purpose

The Architecture Roadmap lists individual work packages that will realize the Target Architecture and lays them out on a timeline to show progression from the Baseline Architecture to the Target Architecture. The Architecture Roadmap highlights individual work packages' business value at each stage. Transition Architectures necessary to effectively realize the Target Architecture are identified as intermediate steps. The Architecture Roadmap is incrementally developed throughout Phases E and F, and informed by readily identifiable roadmap components from Phase B, C, and D within the ADM.

Content

Typical contents of an Architecture Roadmap are:

• Work package portfolio:
  • Work package description (name, description, objectives, deliverables)
  • Functional requirements
  • Dependencies
  • Relationship to opportunity
  • Relationship to Architecture Definition Document and Architecture Requirements Specification
  • Business value
• Implementation Factor Assessment and Deduction matrix, including:
  • Risks
  • Issues
  • Assumptions
  • Dependencies
  • Actions
  • Inputs
• Consolidated Gaps, Solutions, and Dependencies matrix, including:
  • Architecture domain
  • Gap
  • Potential solutions
  • Dependencies
• Any Transition Architectures
• Implementation recommendations:
  • Criteria measures of effectiveness of projects
  • Risks and issues
  • Solution Building Blocks (SBBs)

32.2.8 Architecture Vision

Purpose

The Architecture Vision is created early on in the ADM cycle. It provides a summary of the changes to the enterprise that will accrue from successful deployment of the Target Architecture. The purpose of the Architecture Vision is to provide key stakeholders with a formally agreed outcome. Early agreement on the outcome enables the architects to focus on the detail necessary to validate feasibility. Providing an Architecture Vision also supports stakeholder communication by providing a summary version of the full Architecture Definition.

Content

Typical contents of an Architecture Vision are:

• Problem description:
  • Stakeholders and their concerns
  • List of issues/scenarios to be addressed
• Objective of the Statement of Architecture Work
• Summary views necessary for the Request for Architecture Work and the Version 0.1 Business, Application, Data, and Technology Architectures created; typically including:
  • Value Chain diagram
  • Solution Concept diagram
• Mapped requirements
• Reference to Draft Architecture Definition Document

32.2.9 Business Principles, Business Goals, and Business Drivers

Purpose

Business principles, business goals, and business drivers provide context for architecture work, by describing the needs and ways of working employed by the enterprise. Many factors that lie outside the consideration of architecture discipline may nevertheless have significant implications for the way that architecture is developed.

Content

The content and structure of business context for architecture is likely to vary considerably from one organization to the next.

32.2.10 Capability Assessment

Purpose

Before embarking upon a detailed Architecture Definition, it is valuable to understand the baseline and target capability level of the enterprise. This Capability Assessment can be examined on several levels:

• What is the capability level of the enterprise as a whole? Where does the enterprise wish to increase or optimize capability? What are the architectural focus areas that will support the desired development of the enterprise?
• What is the capability or maturity level of the IT function within the enterprise? What are the likely implications of conducting the architecture project in terms of design governance, operational governance, skills, and organization structure? What is an appropriate style, level of formality, and amount of detail for the architecture project to fit with the culture and capability of the IT organization?
• What is the capability and maturity of the architecture function within the enterprise? What architectural assets are currently in existence? Are they maintained and accurate? What standards and reference models need to be considered? Are there likely to be opportunities to create re-usable assets during the architecture project?
• Where capability gaps exist, to what extent is the business ready to transform in order to reach the target capability? What are the risks to transformation, cultural barriers, and other considerations to be addressed beyond the basic capability gap?

Content

Typical contents of a Capability Assessment are:

• Business Capability Assessment, including:
  • Capabilities of the business
  • Baseline state assessment of the performance level of each capability
  • Future state aspiration for the performance level of each capability
  • Baseline state assessment of how each capability is realized
  • Future state aspiration for how each capability should be realized
  • Assessment of likely impacts to the business organization resulting from the successful deployment of the Target Architecture
• IT Capability Assessment, including:
  • Baseline and target maturity level of change process
  • Baseline and target maturity level of operational processes
  • Baseline capability and capacity assessment
  • Assessment of the likely impacts to the IT organization resulting from the successful deployment of the Target Architecture
• Architecture maturity assessment, including:
  • Architecture Governance processes, organization, roles, and responsibilities
  • Architecture skills assessment
  • Breadth, depth, and quality of landscape definition with the Architecture Repository
  • Breadth, depth, and quality of standards definition with the Architecture Repository
  • Breadth, depth, and quality of reference model definition with the Architecture Repository
  • Assessment of re-use potential
• Business Transformation Readiness Assessment, including:
  • Readiness factors
  • Vision for each readiness factor
  • Current and target readiness ratings
  • Readiness risks

32.2.11 Change Request

Purpose

During implementation of an architecture, as more facts become known, it is possible that the original Architecture Definition and requirements are not suitable or are not sufficient to complete the implementation of a solution. In these circumstances, it is necessary for implementation projects to either deviate from the suggested architectural approach or to request scope extensions. Additionally, external factors - such as market factors, changes in business strategy, and new technology opportunities - may open up opportunities to extend and refine the architecture.

In these circumstances, a Change Request may be submitted in order to kick-start a further cycle of architecture work.

Content

Typical contents of a Change Request are:

• Description of the proposed change
• Rationale for the proposed change
• Impact assessment of the proposed change, including:
  • Reference to specific requirements
  • Stakeholder priority of the requirements to date
  • Phases to be revisited
  • Phase to lead on requirements prioritization
  • Results of phase investigations and revised priorities
  • Recommendations on management of requirements
• Repository reference number

32.2.12 Communications Plan

Purpose

Enterprise Architectures contain large volumes of complex and inter-dependent information. Effective communication of targeted information to the right stakeholders at the right time is a Critical Success Factor (CSF) for Enterprise Architecture. Development of a Communications Plan for architecture allows for this communication to be carried out within a planned and managed process.

Content

Typical contents of a Communications Plan are:

• Identification of stakeholders and grouping by communication requirements
• Identification of communication needs, key messages in relation to the Architecture Vision, communication risks, and CSFs
• Identification of mechanisms that will be used to communicate with stakeholders and allow access to architecture information, such as meetings, newsletters, repositories, etc.
• Identification of a communications timetable, showing which communications will occur with which stakeholder groups at what time and in what location

32.2.13 Compliance Assessment

Purpose

Once an architecture has been defined, it is necessary to govern that architecture through implementation to ensure that the original Architecture Vision is appropriately realized and that any implementation learnings are fed back into the architecture process. Periodic compliance reviews of implementation projects provide a mechanism to review project progress and ensure that the design and implementation is proceeding in line with the strategic and architectural objectives.

Content

Typical contents of a Compliance Assessment are:

• Overview of project progress and status
• Overview of project architecture/design
• Completed architecture checklists:
  • Hardware and operating system checklist
  • Software services and middleware checklist
  • Applications checklists
  • Information management checklists
  • Security checklists
  • System management checklists
    
  • System engineering checklists
  • Methods and tools checklists

32.2.14 Implementation and Migration Plan

Purpose

The Implementation and Migration Plan provides a schedule of the projects that will realize the Target Architecture. The Implementation and Migration Plan includes executable projects grouped into managed portfolios and programs. The Implementation and Migration Strategy identifying the approach to change is a key element of the Implementation and Migration Plan.

Content

Typical contents of an Implementation and Migration Plan are:

• Implementation and Migration Strategy:
  • Strategic implementation direction
  • Implementation sequencing approach
• Project and portfolio breakdown of implementation:
  • Allocation of work packages to project and portfolio
  • Capabilities delivered by projects
  • Milestones and timing
  • Work breakdown structure
  • May include impact on existing portfolio, program, and projects

It may contain:

• Project charters:
  • Included work packages
  • Business value
  • Risk, issues, assumptions, dependencies
  • Resource requirements and costs
  • Benefits of migration, determined (including mapping to business requirements)
  • Estimated costs of migration options

32.2.15 Implementation Governance Model

Purpose

Once an architecture has been defined, it is necessary to plan how the Transition Architecture that implements the architecture will be governed through implementation. Within organizations that have established architecture functions, there is likely to be a governance framework already in place, but specific processes, organizations, roles, responsibilities, and measures may need to be defined on a project-by-project basis.

The Implementation Governance Model ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance.

Content

Typical contents of an Implementation Governance Model are:

• Governance processes
• Governance organization structure
• Governance roles and responsibilities
• Governance checkpoints and success/failure criteria

32.2.16 Organizational Model for Enterprise Architecture

Purpose

In order for an architecture framework to be used successfully, it must be supported by the correct organization, roles, and responsibilities within the enterprise. Of particular importance is the definition of boundaries between different Enterprise Architecture practitioners and the governance relationships that span across these boundaries.

Content

Typical contents of an Organizational Model for Enterprise Architecture are:

• Scope of organizations impacted
• Maturity assessment, gaps, and resolution approach
• Roles and responsibilities for architecture team(s)
• Constraints on architecture work
• Budget requirements
• Governance and support strategy

32.2.17 Request for Architecture Work

Purpose

This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle. Requests for Architecture Work can be created as an output of the Preliminary Phase, a result of approved architecture Change Requests, or terms of reference for architecture work originating from migration planning.

In general, all the information in this document should be at a high level.

Content

Requests for Architecture Work typically include:

• Organization sponsors
• Organization's mission statement
• Business goals (and changes)
• Strategic plans of the business
• Time limits
• Changes in the business environment
• Organizational constraints
• Budget information, financial constraints
• External constraints, business constraints
• Current business system description
• Current architecture/IT system description
• Description of developing organization
• Description of resources available to developing organization

32.2.18 Requirements Impact Assessment

Purpose

Throughout the ADM, new information is collected relating to an architecture. As this information is gathered, new facts may come to light that invalidate existing aspects of the architecture. A Requirements Impact Assessment assesses the current architecture requirements and specification to identify changes that should be made and the implications of those changes.

Content

Typical contents of a Requirements Impact Assessment are:

• Reference to specific requirements
• Stakeholder priority of the requirements to date
• Phases to be revisited
• Phase to lead on requirements prioritization
• Results of phase investigations and revised priorities
• Recommendations on management of requirements
• Repository reference number

32.2.19 Solution Building Blocks

Implementation-specific building blocks from the enterprise's Architecture Repository; see Part IV, 33. Building Blocks .

32.2.20 Statement of Architecture Work

Purpose

The Statement of Architecture Work defines the scope and approach that will be used to complete an architecture development cycle. The Statement of Architecture Work is typically the document against which successful execution of the architecture project will be measured and may form the basis for a contractual agreement between the supplier and consumer of architecture services.

Content

Typical contents of a Statement of Architecture Work are:

• Title
• Architecture project request and background
• Architecture project description and scope
• Overview of Architecture Vision
• Specific change of scope procedures
• Roles, responsibilities, and deliverables
• Acceptance criteria and procedures
• Architecture project plan and schedule
• Approvals

32.2.21 Tailored Architecture Framework

Purpose

The TOGAF framework provides an industry standard for architecture that may be used in a wide variety of organizations. However, before the TOGAF framework can be effectively used within an architecture project, tailoring at two levels is necessary.

Firstly, it is necessary to tailor the TOGAF model for integration into the enterprise. This tailoring will include integration with management frameworks, customization of terminology, development of presentational styles, selection, configuration, and deployment of architecture tools, etc. The formality and detail of any frameworks adopted should also align with other contextual factors for the enterprise, such as culture, stakeholders, commercial models for Enterprise Architecture, and the existing level of Architecture Capability.

Once the framework has been tailored to the enterprise, further tailoring is necessary in order to tailor the framework for the specific architecture project. Tailoring at this level will select appropriate deliverables and artifacts to meet project and stakeholder needs.

See Part II, 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s) for further considerations when selecting and tailoring the architecture framework.

Content

Typical contents of a Tailored Architecture Framework are:

• Tailored architecture method
• Tailored architecture content (deliverables and artifacts)
• Configured and deployed tools
• Interfaces with governance models and other frameworks:
  • Corporate Business Planning
  • Enterprise Architecture
  • Portfolio, Program, Project Management
  • System Development/Engineering
  • Operations (Services)

return to top of page