The Architecture Development Method: Personal PDF Edition

®
The Architecture
Development Method
REFERENCE CARDS
Personal PDF Edition

®
The Architecture
Development
Method
N181 Reference Cards: The TOGAF Standard, Version 9.2 ADM Copyright © 2018 The Open Group. All Rights Reserved.
Personal PDF Edition TOGAF® is a registered trademark of The Open Group.
®
Introduction to the TOGAF Standard
The TOGAF standard is a framework for Enterprise Architecture. Put simply, it is a

standard approach for assisting in the acceptance, production, use, and maintenance
of Enterprise Architectures. It is based on an iterative process model supported by best
practices and a re-usable set of existing architectural assets.
The TOGAF standard is developed and maintained by members of The Open Group,
working within the Architecture Forum. The original development of the TOGAF standard
in 1995, was based on the US Department of Defense Technical Architecture Framework
for Information Management (TAFIM). Starting from this sound foundation, The Open
Group Architecture Forum has developed successive versions of the TOGAF standard at
regular intervals and published each one on The Open Group public website.
The TOGAF standard can be used for developing a broad range of different Enterprise
Architectures. It complements, and can be used in conjunction with, other frameworks
that are more focused on specific deliverables for particular vertical sectors such as
Government, Telecommunications, Manufacturing, Defense, and Finance. A key part of the
TOGAF standard is the method – the TOGAF Architecture Development Method (ADM) –
for developing an Enterprise Architecture that addresses business needs.
®
The TOGAF Standard

The TOGAF standard is divided into six parts, as summarized in Table 1.
Table 1: Structure of the TOGAF Standard
Part I: Introduction This part provides a high-level introduction to the key concepts of Enterprise Architecture
and, in particular, to the TOGAF approach. It contains the definitions of terms used
throughout the standard.
Part II: Architecture This part is the core of the TOGAF framework. It describes the TOGAF Architecture
Development Method Development Method (ADM) – a step-by-step approach to developing an Enterprise
Architecture.
Part III: ADM Guidelines This part contains a collection of guidelines and techniques available for use in applying
and Techniques the TOGAF approach and the TOGAF ADM. Additional guidelines and techniques are
also in the TOGAF Library.
Part IV: Architecture This part describes the TOGAF content framework, including a structured metamodel for
Content Framework architectural artifacts, the use of re-usable Architecture Building Blocks (ABBs), and an
overview of typical architecture deliverables.
Part V: Enterprise This part discusses appropriate taxonomies and tools to categorize and store the outputs
Continuum and Tools of architecture activity within an enterprise.
Part VI: Architecture This part discusses the organization, processes, skills, roles, and responsibilities required
Capability Framework to establish and operate an architecture practice within an enterprise.
®
The TOGAF Library

The TOGAF Library is a reference library containing guidelines, templates, patterns, and other
forms of reference material to accelerate the creation of new architectures for the enterprise.
It is structured as follows:
Section 1: Base Documents Broadly applicable information relating to the subject of the
TOGAF framework or Enterprise Architecture.
Section 2: Generic Guidance Information describing architecture styles and how the TOGAF
and Techniques framework and Enterprise Architecture can be adapted to exploit
the characteristics of a more specific context.
Section 3: Industry-Specific Information describing how the TOGAF framework and Enterprise
Guidance and Techniques Architecture can be applied to meet the specific needs of a
vertical industry segment.
Section 4: Organization- Information describing how the TOGAF framework and Enterprise
Specific Guidance and Architecture have been applied to meet the needs of specific
Techniques enterprises.
The TOGAF Library: www.opengroup.org/togaf-library
®
P Preliminary Phase
Preliminary Phase
Objectives Steps Inputs Outputs
Determine the Architecture Capability Scope the enterprise organizations The TOGAF Library Organizational Model for Enterprise
desired by the organization: impacted Other architecture framework(s) Architecture
Confirm governance and support Board strategies, business plans, Tailored Architecture Framework,
• Review the organizational context for frameworks including Architecture Principles
conducting Enterprise Architecture business strategy, IT Strategy, business
• Identify and scope the elements of Define and establish Enterprise principles, business goals, and business Initial Architecture Repository
the enterprise organizations affected Architecture team and organization drivers Restatement of, or reference to,
by the Architecture Capability Identify and establish Architecture Major frameworks operating in the business principles, business goals, and
• Identify the established frameworks, Principles business business drivers
methods, and processes that intersect Tailor the TOGAF framework and, if any, Governance and legal frameworks Request for Architecture Work
with the Architecture Capability other selected architecture frameworks
• Establish Capability Maturity target Architecture Capability Architecture Governance Framework
Develop strategy and implementation Partnership and contract agreements
Establish the Architecture Capability: plans for tools and techniques
Existing organizational model for
Enterprise Architecture
• Define and establish the
Organizational Model for Enterprise Existing architecture framework, if any,
Architecture including:
• Define and establish the detailed
process and resources for • Architecture method
Architecture Governance • Architecture content
• Select and implement tools that • Configured and deployed tools
support the Architecture Capability • Architecture Principles
• Define the Architecture Principles • Architecture Repository
®
R Requirements Management
Requirements Management
Ensure that the Requirements Identify/document requirements The inputs to the Requirements Changed requirements
Management process is sustained and Baseline requirements Management process are the Requirements Impact Assessment,
operates for all relevant ADM phases Monitor baseline requirements requirements-related outputs from each which identifies the phases of the ADM
Manage architecture requirements ADM phase that need to be revisited to address any
Identify changed requirements; remove,
identified during any execution of the add, modify, and re-assess priorities The first high-level requirements are changes
ADM cycle or a phase produced as part of the Architecture The final version must include the full
Identify changed requirements and Vision
Ensure that relevant architecture record priorities; identify and resolve implications of the requirements (e.g.,
requirements are available for use by conflicts; generate requirements impact Each architecture domain then costs, timescales, and business metrics)
each phase as the phase is executed statements generates detailed requirements
Assess impact of changed requirements Deliverables in later ADM phases

on current and previous ADM phases contain mappings to new types of
requirements (for example, conformance
Implement requirements arising from requirements)
Phase H
Update the Architecture Requirements
Repository
Implement change in the current phase
Assess and revise gap analysis for past
phases
®
A Architecture Vision
Architecture Vision
Develop a high-level aspirational Establish the architecture project Request for Architecture Work Approved Statement of Architecture Work
vision of the capabilities and Identify stakeholders, concerns, and Business principles, business goals, Refined statements of business principles,
business value to be delivered as business requirements and business drivers business goals, and business drivers
a result of the proposed Enterprise
Architecture Confirm and elaborate business Organizational Model for Enterprise Architecture Principles Capability Assessment
goals, business drivers, and Architecture Tailored Architecture Framework Architecture
Obtain approval for a Statement of constraints
Architecture Work that defines a Tailored Architecture Framework, Vision, including:
program of works to develop and Evaluate capabilities including tailored architecture method, • Refined key high-level stakeholder
deploy the architecture outlined in Assess readiness for business architecture content, architecture requirements
the Architecture Vision transformation principles, configured and deployed
tools Draft Architecture Definition Document, including
Define scope (when in scope):
Populated Architecture Repository; that
Confirm and elaborate architecture is, existing architecture documentation • Baseline Business Architecture (high-level)
principles, including business (framework description, architecture • Baseline Data Architecture (high-level)
principles descriptions, existing baseline • Baseline Application Architecture (high-level)
Develop Architecture Vision descriptions, etc.) • Baseline Technology Architecture (high-level)
• Target Business Architecture (high-level)
Define the Target Architecture value • Target Data Architecture (high-level)
propositions and KPIs • Target Application Architecture (high-level)
Identify business transformation risks • Target Technology Architecture (high-level)
and mitigation activities • Communications Plan
Develop Statement of Architecture • Additional content populating the Architecture
Work; secure approval Repository
®
B Business Architecture
Phase B: Business Architecture
Develop the Target Business Select reference models, Request for Architecture Work Statement of Architecture Work,
Architecture that describes how the viewpoints, and tools Business principles, business goals, and business updated if necessary
enterprise needs to operate to achieve Develop Baseline Business drivers Validated business principles, business
the business goals, and respond to Architecture Description goals, and business drivers
the strategic drivers set out in the Capability Assessment
Architecture Vision in a way that Develop Target Business Communications Plan Refined and updated Architecture
addresses the Statement of Architecture Architecture Description Principles, if applicable
Organizational Model for Enterprise Architecture
Work and stakeholder concerns Perform gap analysis Draft Architecture Definition Document
Tailored Architecture Framework containing content updates:
Identify candidate Architecture Roadmap Define candidate roadmap
components based upon gaps between components Approved Statement of Architecture Work • Baseline Business Architecture
the Baseline and Target Business Architecture Principles, including business (detailed), if appropriate
Resolve impacts across the • Target Business Architecture
Architectures Architecture Landscape principles, when pre-existing
(detailed with Business Capabilities,
Conduct formal stakeholder Enterprise Continuum Architecture Repository Value Streams, and Organization
review Architecture Vision, including: Map as core artifacts)
Finalize the Business • Refined key high-level stakeholder • Views corresponding to selected
Architecture requirements Draft Architecture Definition viewpoints addressing key
Document, including: stakeholder concerns
Create Architecture Definition
Document • Baseline Business Architecture (high-level) Draft Architecture Requirements
• Baseline Data Architecture (high-level) Specification including content
• Baseline Application Architecture (high-level) updates:
• Baseline Technology Architecture (high-level) • Gap analysis results
• Target Business Architecture (high-level) • Technical requirements
• Target Data Architecture (high-level) • Updated business requirements
• Target Application Architecture (high-level) • Business Architecture components
• Target Technology Architecture (high-level) of an Architecture Roadmap
®
C Data Architecture
Phase C: Information Systems Architectures – Data Architecture
Develop the Target Data Select reference models, Request for Architecture Work Statement of Architecture Work, updated if
Architecture that enables the viewpoints, and tools Capability Assessment necessary
Business Architecture and the Develop Baseline Data Validated data principles, or new data
Architecture Vision, in a way Communications Plan principles
Architecture Description
that addresses the Statement Organizational Model for Enterprise Architecture Tailored Draft Architecture Definition Document
of Architecture Work and Develop Target Data Architecture Framework containing content updates:
stakeholder concerns Architecture Description • Baseline Data Architecture
Data principles
Identify candidate Architecture Perform gap analysis • Target Data Architecture
Statement of Architecture Work • DataArchitectureviews corresponding to
Roadmap components based Define candidate roadmap
upon gaps between the components Architecture Vision the selected viewpoints, addressing key
Baseline and Target Data Architecture Repository stakeholder concerns
Resolve impacts across the
Architectures Architecture Landscape Draft Architecture Definition Document containing: Draft Architecture Requirements
• Baseline Business Architecture (detailed) Specification including content updates:
Conduct formal stakeholder • Gap analysis results
review • Target Business Architecture (detailed)
• Baseline Data Architecture (high-level) • Data interoperability requirements
Finalize the Data Architecture • Target Data Architecture (high-level) • Relevant technical requirements that will
Create Architecture Definition • Baseline Application Architecture (detailed or high- apply to this evolution of the architecture
Document level) development cycle
• Target Application Architecture (detailed or high-level) • Constraints on the Technology
• Baseline Technology Architecture (high-level) Architecture
• Target Technology Architecture (high-level) • Updated business requirements
• Updated application requirements
Draft Architecture Requirements Specification
• including: Data Architecture components of an
• Gapanalysisresults Architecture Roadmap
• Relevanttechnicalrequirements
• Business Architecture components of an Architecture
Roadmap
®
C Application Architecture
Phase C: Information Systems Architectures – Application Architecture
Develop the Target Select reference models, Request for Architecture Work Statement of Architecture Work, updated if
Application Architecture viewpoints, and tools Capability Assessment necessary
that enables the Business Develop Baseline Application Validated application principles, or new
Architecture and the Communications Plan
Architecture Description application principles
Architecture Vision, in a way Organizational Model for Enterprise Architecture
that addresses the Statement Develop Target Application Draft Architecture Definition Document
Architecture Description Tailored Architecture Framework containing content updates:
of Architecture Work and
stakeholder concerns Perform gap analysis Application Principles • Baseline Application Architecture
Statement of Architecture Work • Target Application Architecture
Identify candidate Architecture Define candidate roadmap • Application Architecture views
Roadmap components components Architecture Vision corresponding to the selected
based upon gaps between Resolve impacts across the Architecture Repository viewpoints, addressing key stakeholder
the Baseline and Target Architecture Landscape concerns
Application Architectures Draft Architecture Definition Document containing:
Conduct formal stakeholder • Baseline Business Architecture (detailed) Draft Architecture Requirements
review • Target Business Architecture (detailed) Specification including content updates:
Finalize the Application • Baseline Data Architecture (detailed or high-level) • Gap analysis results
Architecture • Target Data Architecture (detailed or high-level) • Application interoperability requirements
• Baseline Application Architecture (high-level) • Relevant technical requirements that will
Create Architecture Definition • Target Application Architecture (high-level) apply to this evolution of the architecture
Document • Baseline Technology Architecture (high-level) development cycle
• Target Technology Architecture (high-level) • Constraints on the Technology
Draft Architecture Requirements Specification including: Architecture
• Gap analysis results • Updated business requirements
• Relevant technical requirements • Updated data requirements
• Business and Data Architecture components of an Application Architecture components of an
Architecture Roadmap Architecture Roadmap
®
D Technology Architecture
Phase D: Technology Architecture
Develop the Target Select reference models, Request for Architecture Work Statement of Architecture Work, updated if
Technology Architecture that viewpoints, and tools Capability Assessment necessary
enables the Architecture Develop Baseline Technology Validated technology principles or new
Vision, target business, data, Communications Plan
Architecture Description technology principles (if generated here)
and application building Organizational Model for Enterprise Architecture
blocks to be delivered through Develop Target Technology Draft Architecture Definition Document
Architecture Description Tailored Architecture Framework containing content updates:
technology components and
technology services, in a way Perform gap analysis Technology principles • Baseline Technology Architecture, if
that addresses the Statement Statement of Architecture Work appropriate
Define candidate roadmap • Target Technology Architecture
of Architecture Work and components Architecture Vision
stakeholder concerns • Technology Architecture views
Resolve impacts across the Architecture Repository corresponding to the selected
Identify candidate Architecture Architecture Landscape viewpoints, addressing key stakeholder
Draft Architecture Definition Document containing:
Roadmap components Conduct formal stakeholder • Baseline Business Architecture (detailed) concerns
based upon gaps between review • Target Business Architecture (detailed) Draft Architecture Requirements
the Baseline and Target • Baseline Data Architecture (detailed) Specification including content updates:
Technology Architectures Finalize the Technology
Architecture • Target Data Architecture (detailed) • Gap analysis results
• Baseline Application Architecture (detailed) • Requirements output from Phases B
Create Architecture Definition • Target Application Architecture (detailed) and C
Document • Baseline Technology Architecture (high-level) • Updated technology requirements
• Target Technology Architecture (high-level) Technology Architecture components of an
Draft Architecture Requirements Specification including: Architecture Roadmap
• Gap analysis results
• Relevant technical requirements
• Business, Data, and Application Architecture
components of an Architecture Roadmap
®
E Opportunities & Solutions
Phase E: Opportunities & Solutions
Generate the initial complete Determine/confirm key corporate Product information Statement of Architecture Work, updated if
version of the Architecture change attributes Request for Architecture Work necessary
Roadmap, based upon the Determine business constraints for Architecture Vision, updated if necessary
gap analysis and candidate Capability Assessment
implementation Draft Architecture Definition Document, including:
Architecture Roadmap Communications Plan
components from Phases B, Review and consolidate gap analysis • Transition Architectures, number and scope, if
results from Phases B to D Planning methodologies any
C, and D
Review consolidated requirements Organizational model for Enterprise Draft Architecture Requirements Specification,
Determine whether an Architecture
incremental approach is across related business functions updated if necessary
required, and if so identify Consolidate and reconcile Governance models and frameworks Capability Assessment, including:
Transition Architectures interoperability requirements Tailored Architecture Framework • Business Capability
that will deliver continuous Refine and validate dependencies Statement of Architecture Work • IT Capability
business value Architecture Roadmap, including:
Confirm readiness and risk for Architecture Vision
Define the overall Solution business transformation • Work Package portfolio
Building Blocks (SBBs) to Architecture Repository • Identification of Transition Architectures, if any
finalize the Target Architecture Formulate Implementation and Draft Architecture Definition Document • Implementation recommendations
based on the Architecture Migration Strategy
Draft Architecture Requirements Implementation and Migration Plan (outline),
Building Blocks (ABBs) Identify and group major work Specification including:
packages • Implementation and Migration Strategy
Change Requests for existing programs
Identify Transition Architectures and projects
Create Architecture Roadmap & Candidate Architecture Roadmap
Implementation and Migration Plan components from Phases B, C, and D
®
F Migration Planning
Phase F: Migration Planning
Finalize the Architecture Confirm management framework Request for Architecture Work Implementation and Migration Plan (detailed),
Roadmap and the supporting interactions for Implementation and Communications Plan including:
Implementation and Migration Migration Plan • Implementation and Migration Strategy
Plan Organizational Model for Enterprise • Project and portfolio breakdown of the
Assign a business value to each work Architecture
Ensure that the package implementation
Implementation and Migration Governance models and frameworks • Project charters (optional)
Estimate resource requirements,
Plan is coordinated with the project timings, and availability/ Tailored Architecture Framework Finalized Architecture Definition Document,
enterprise’s approach to delivery vehicle Statement of Architecture Work including:
managing and implementing • Finalized Transition Architectures, if any
change in the enterprise’s Prioritize the migration projects Architecture Vision
through the conduct of a cost/benefit Finalized Architecture Requirements Specification
overall change portfolio Architecture Repository
assessment and risk validation Finalized Architecture Roadmap
Ensure that the business Draft Architecture Definition Document,
value and cost of work Confirm Architecture Roadmap including: Re-Usable Architecture Building Blocks
packages and Transition and update Architecture Definition • Transition Architectures, if any Requests for Architecture Work for a new
Architectures is understood Document iteration of the ADM cycle (if any)Implementation
Draft Architecture Requirements
by key stakeholders Complete the Implementation and Specification Governance Model
Migration Plan Change Requests for the Architecture
Change Requests for existing programs
Complete the architecture and projects Capability arising from lessons learned
development cycle and document
lessons learned Architecture Roadmap
Capability Assessment, including:
• Business Capability
• IT Capability
Implementation and Migration Plan
(outline), including:
• High-level Implementation and
Migration Strategy
®
G Implementation Governance
Phase G: Implementation Governance
Ensure conformance with Confirm scope and priorities for Request for Architecture Work Architecture Contract (signed)
the Target Architecture by deployment with development Capability Assessment Compliance Assessments
implementation projects management
Organizational Model for Enterprise Change Requests
Perform appropriate Identify deployment resources and Architecture
Architecture Governance skills Architecture-compliant solutions deployed,
functions for the solution Tailored Architecture Framework including:
Guide development of solutions • The architecture-compliant implemented system
and any implementation- deployment Statement of Architecture Work
driven architecture Change • Populated Architecture Repository
Perform enterprise architecture Architecture Vision • Architecture compliance recommendations and
Requests
compliance reviews Architecture Repository dispensations
Implement business and IT operations Architecture Definition Document • Recommendations on service delivery
requirements
Perform post-implementation review Architecture Requirements Specification • Recommendations on performance metrics
and close the implementation Architecture Roadmap • Service Level Agreements (SLAs)
Implementation Governance Model • Architecture Vision, updated post-
implementation
Architecture Contract • Architecture Definition Document, updated post-
Request for Architecture Work identified in implementation
Phases E and F • Business and IT operating models for the
Implementation and Migration Plan implemented solution
®
H Architecture Change
Management
Phase H: Architecture Change Management
Ensure that the architecture Establish value realization process Request for Architecture Work Architecture updates
lifecycle is maintained Deploy monitoring tools Capability Assessment Changes to architecture framework and
Ensure that the Architecture Manage risks Organizational Model for Enterprise Architecture principles
Governance Framework is New Request for Architecture Work, to
executed Provide analysis for architecture Tailored Architecture Framework
change management initiate another cycle of the ADM
Ensure that the Enterprise Statement of Architecture Work
Develop change requirements to meet Statement of Architecture Work, updated
Architecture Capability meets Architecture Vision if necessary
current requirements performance targets
Architecture Repository Architecture Contract, updated if
Manage governance process
Architecture Definition Document necessary
Activate the process to implement
change Architecture Requirements Specification Compliance Assessments, updated if
Architecture Roadmap necessary
Implementation Governance Model

Architecture Contract
Request for Architecture Work identified in Phases
E and F
Implementation and Migration Plan
®
About The Open Group
Leading the development of open, vendor-neutral technology standards and certifications

The Open Group is a global consortium that enables the achievement of business objectives through
technology standards. The Open Group works with customers, suppliers, consortia, and other standards
bodies. Its role is to capture, understand, and address current and emerging requirements, establish
policies, and share best practices; to facilitate interoperability, develop consensus, and evolve and integrate
specifications and open source technologies; and to operate the industry’s premier certification service.
Keys facts include:
• Over 585 member organizations, with 43,000+ participants in The Open Group activities from 126
countries - our Platinum Members are DXC Technology, Fujitsu, HCL, Huawei, IBM, Micro Focus, Oracle,
and Philips
• Services provided include strategy, management, innovation and research, standards, certification, and
test development
• Vision of Boundaryless Information Flow™, with Enterprise Architecture as a critical element for making
the vision a reality; the TOGAF® Architecture Development Method (ADM) provides an important toolset
Further information on The Open Group can be found at www.opengroup.org.
ArchiMate®, DirecNet®, Making Standards Work®, OpenPegasus®, Platform 3.0®, The Open Group®, TOGAF®, UNIX®,
UNIXWARE®, X/Open®, and the Open Brand X® logo are registered trademarks and Boundaryless Information FlowTM, Build
with Integrity Buy with ConfidenceTM, Dependability Through AssurednessTM, EMMMTM, FACETM, the FACETM logo, IT4ITTM,
the IT4ITTM logo, O-DEFTM, O-PASTM, Open FAIRTM, Open Platform 3.0TM, Open Process AutomationTM, Open Trusted
Technology ProviderTM, SOSATM, the Open OTM logo, and The Open Group Certification logo (Open O and checkTM) are
trademarks of The Open Group.
Copyright © 2018 The Open Group. All Rights Reserved.
Personal PDF Edition

The Architecture Development Method: Personal PDF Edition

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

The Architecture Development Method: Personal PDF Edition

Uploaded by

Copyright:

Available Formats

®

Personal PDF Edition

Introduction to the TOGAF Standard

The TOGAF standard is a framework for Enterprise Architecture. Put simply, it is a

The TOGAF Standard

Table 1: Structure of the TOGAF Standard

The TOGAF Library

The TOGAF Library: www.opengroup.org/togaf-library

Assess impact of changed requirements Deliverables in later ADM phases

Implementation Governance Model

About The Open Group

Leading the development of open, vendor-neutral technology standards and certifications

Personal PDF Edition

You might also like