This chapter provides descriptions of input and output items referenced in the Architecture Development Method (ADM).

Introduction

This section provides example descriptions of input and output items referenced in the ADM.

Note that not all the content described here need be contained in a particular input or output. Rather, it is recommended that external references be used where possible; for example, the strategic plans should not be copied into the 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.

Finally, note that versioning is used to indicate that input or output items may undergo change as the ADM is executed. As an input or output item is updated, a new version may be produced. In all cases, the TOGAF ADM numbering scheme is provided as an example. It should be adapted by the architect to meet the requirements of the organization and to work with the architecture tools and repositories employed by the organization.

Major Input Descriptions

Request for Architecture Work

• 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

Architecture Principles

See Part IV: Resource Base, Architecture Principles for guidelines and a detailed set of generic architecture principles, including:

• Business principles (Business Principles)
• Data principles (Data Principles)
• Application principles (Application Principles)
• Technology principles (Technology Principles)

Re-Usable Architecture Building Blocks

• Architecture documentation and models from the enterprise's Architecture Continuum

Product Information

• Functional descriptions of products that are candidates for the implementation
• Architectural descriptions of elements that are candidates for the implementation

New Technology Reports

• New developments in potentially relevant technology

Major Output Descriptions

Statement of Architecture Work

• Statement of work title
• Project request and background
• Project description and scope
• Architecture vision
• Managerial approach
• Change of scope procedures
• Responsibilities and deliverables
• Acceptance criteria and procedures
• Project plan and schedule
• Support of the Enterprise Continuum
• Signature approvals

Business Scenario/Architecture Vision

• Problem description
  • Purpose of scenario
• Detailed objectives
• Environment and process models
  • Process description
  • Process steps mapped to environment
  • Process steps mapped to people
  • Information flow
• Actors and their roles and responsibilities
  • Human actors and roles
  • Computer actors and roles
  • Requirements
• Resulting architecture model
  • Constraints
  • IT principles
  • Architecture supporting the process
  • Requirements mapped to architecture

Business Architecture

• Baseline Business Architecture
• Business goals, objectives, and constraints
  • Business requirements and key system and architecture drivers
  • Business return given required changes
  • Assumptions (e.g., business, financial, organizational, or required technical functionality)
  • Business Architecture principles
• Business Architecture models
  • Organization structure
  • Business functions
  • Business roles
  • Correlation of organization and functions
  • Business Architecture Building Blocks list (e.g., business services)
  • Business Architecture Building Blocks models
  • Candidate Solution Building Blocks list
  • Candidate Solution Building Blocks models
  • Relevant business process descriptions, including measures and deliverables
• Technical requirements (drivers for other architecture work)

Technology Architecture

• Baseline Technology Architecture
• Objectives and constraints
  • Technology requirements and key system and architecture drivers
  • Assumptions (e.g., business, financial, organizational, or required technical functionality)
• Technology Architecture model(s)
  • Architecture Building Block models of views (minimally model of functions and a model of services)
  • Architecture Building Block models of service portfolios (enterprise-specific framework)
• Technology Architecture specification
  • Per-Architecture Building Block:
    • Details of the technical functionality
    • Fully defined list of all the standards
    • Description of building block at the levels necessary to support implementation, enterprise-wide strategic decision-making, and further iterations of the architectural definition process
    • Rationale for decisions taken that relate to the building block, including rationales for decisions not to do something
    • Specification identifying the interworking with other building blocks and how they do so
    • Guidelines for procuring
  • Standards summary list
• Requirements traceability
  • Acceptance criteria
  • Criteria for choosing specifications
  • Criteria for selection of portfolios of specifications
  • Criteria to test merits of architecture (key question list)
  • Report on cost/benefit analyses
  • Report on how the proposed architecture meets the business goals and objectives
  • Criteria response answers to key question list to test merits of architecture
• Gap report
  • Report on gap analysis
  • Report of gap analysis matrix
• Mapping of the architectures in the Enterprise Continuum
  • Change requests for extensions or amendments to related architectures

Impact Analysis

• Project list
  • Name, description, and objectives of each impacted project
  • Prioritized list of impacted projects to implement the proposed architecture
• Time-oriented Migration Plan
  • Benefits of migration, determined (including mapping to business requirements)
  • Estimated costs of migration options
• Implementation recommendations
  • Criteria measures of effectiveness of projects
  • Risks and issues
  • Solution Building Blocks - description and model

Architecture Contract

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))

This contract is also used to manage changes to the enterprise architecture in Phase H (see Phase H: Architecture Change Management).

Requirements Impact Statement

• 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

The TOGAF document set is designed for use with frames. To navigate around the document:

• In the main Contents frame at the top of the page, click the relevant hyperlink (Part I, Part II, etc.) to load the Contents List for that Part of the TOGAF document into the Secondary Index frame in the left margin.
  
  
• Then click in that Contents List to load a page into this main frame.
  
  

Downloads of the TOGAF documentation, are available under license from the TOGAF information web site. The license is free to any organization wishing to use TOGAF entirely for internal purposes (for example, to develop an information system architecture for use within that organization). A hardcopy book is also available from The Open Group Bookstore as document G063.