N093 PDF

ADM
The Architecture
Development
Method
Copyright © 2009 The Open Group. All Rights Reserved.

N093 Reference Card: ADM TOGAF™ is a trademark of The Open Group.
P Preliminary Phase
Preliminary Phase
Objectives Steps Inputs Outputs
To review the organizational context for Scope the enterprise organizations TOGAF Organizational Model for Enterprise
conducting enterprise architecture impacted Other architecture framework(s) Architecture
To identify the stakeholders, their requirements, Confirm governance and support Business principles, business Tailored Architecture Framework,
and priorities frameworks goals, and business drivers including architecture principles
To confirm the commitment of the stakeholders Define and establish enterprise Architecture governance strategy Initial Architecture Repository
To identify and scope the elements of the architecture team and organization Restatement of, or reference to,
IT strategy
enterprise organizations affected and define the Identify and establish architecture business principles, business goals,
Existing organizational model for
constraints and assumptions; this is particularly principles and business drivers
enterprise architecture
important for large organizations with a federated Select and tailor architecture Request for Architecture Work
architecture environment Existing Architecture Framework, if
framework(s) Governance Framework
any
To define an organization's “architecture Implement architecture tools
footprint”; that is, the people responsible for Existing architecture principles, if
performing architecture work, where they are any
located, and their responsibilities Existing Architecture Repository, if
To define the framework and detailed any
methodologies to be used to develop the
enterprise architecture in the organization;
typically an adaptation of the ADM
To set up a governance and support framework
to provide business process and architecture
governance through the ADM cycle; confirm the
fitness-for-purpose and ongoing effectiveness of
the Target Architecture; and run an initial pilot
project
To select and implement supporting tools and
other infrastructure to support the activity
To define the constraining architecture principles

R Requirements Management
Requirements Management
To provide a process to manage Identify/document requirements The inputs to the Requirements Changed requirements
architecture requirements throughout Baseline requirements Management process are the Requirements Impact Assessment,
the phases of the ADM cycle requirements-related outputs from which identifies the phases of the ADM
Monitor baseline requirements
To identify requirements for the each ADM phase. that need to be revisited to address
Identify changed requirement; remove,
enterprise, store them, and feed them The first high-level requirements are any changes. The final version must
add, modify, and re-assess priorities
in and out of the relevant ADM phases, produced as part of the Architecture include the full implications of the
which dispose of, address, and Identify changed requirement and Vision. requirements (e.g., costs, timescales,
prioritize requirements record priorities; identify and resolve and business metrics).
Each architecture domain then
conflicts; generate Requirements
generates detailed requirements.
Impact Statements
Deliverables in later ADM phases
Assess impact of changed contain mappings to new types of
requirements on current and previous requirements (for example,
ADM phases conformance requirements).
Implement requirements arising from
Phase H
Update the requirements repository
Implement change in the current phase
Assess and revise gap analysis for
past phases

A Architecture Vision
Phase A: Architecture Vision
To obtain commitment for this Establish the architecture project Request for Architecture Work Approved Statement of Architecture Work
particular cycle of the ADM Identify stakeholders, concerns, and Business principles, business goals, Refined statements of business principles,
To define and organize an ADM cycle business requirements and business drivers business goals, and business drivers
To validate business principles, goals, Confirm and elaborate business goals, Organizational Model for Enterprise Architecture principles
drivers, and Key Performance business drivers, and constraints Architecture Capability Assessment
Indicators (KPIs) Evaluate business capabilities Tailored Architecture Framework, Tailored Architecture Framework
To define, scope, and prioritize Assess readiness for business including architecture principles
Architecture Vision, including:
architecture tasks transformation Populated Architecture Repository;
• Refined key high-level stakeholder
To identify stakeholders, their Define scope that is, existing architecture
requirements
concerns, and objectives documentation (framework
Confirm and elaborate architecture • Baseline Business Architecture (vision)
To define business requirements and description, architecture
principles, including business • Baseline Data Architecture (vision)
constraints descriptions, existing baseline
principles • Baseline Application Architecture
descriptions, etc.)
To articulate an Architecture Vision Develop Architecture Vision (vision)
and value proposition to respond to the • Baseline Technology Architecture
Define the Target Architecture value
requirements and constraints (vision)
propositions and KPIs
To create a comprehensive plan in line • Target Business Architecture (vision)
Identify business transformation risks
with the project management • Target Data Architecture (vision)
and mitigation activities
frameworks adopted by the enterprise • Target Application Architecture (vision)
Develop enterprise architecture plans
To obtain formal approval to proceed • Target Technology Architecture
and Statement of Architecture Work;
To understand the influence on, and secure approval (vision)
from, parallel architecture Communications Plan
developments Additional content populating the
Architecture Repository

B Business Architecture
Phase B: Business Architecture
To describe the Baseline Business Select reference models, viewpoints, Request for Architecture Work Statement of Architecture Work,
Architecture and tools Business principles, business goals, and updated if necessary
To develop a Target Business Develop Baseline Business business drivers Validated business principles, business
Architecture Architecture Description Capability Assessment goals, and business drivers
To analyze the gaps between the Develop Target Business Architecture Communications Plan Elaborated Business Architecture
Baseline and Target Business Description principles
Organizational Model for Enterprise
Architectures Perform gap analysis Draft Architecture Definition Document
Architecture
To select architecture viewpoints to Define roadmap components containing content updates:
Tailored Architecture Framework
demonstrate how stakeholder • Baseline Business Architecture
Resolve impacts across the Approved Statement of Architecture Work
concerns are addressed in the (detailed), if appropriate
Architecture Landscape
Business Architecture Architecture principles, including business • Target Business Architecture
Conduct formal stakeholder review principles, when pre-existing
To select tools and techniques for (detailed)
viewpoints Finalize the Business Architecture Enterprise Continuum • Views corresponding to selected
Create Architecture Definition Architecture Repository viewpoints addressing key
Document stakeholder concerns
Architecture Vision, including:
• Refined key high-level stakeholder
Draft Architecture Requirements
requirements Specification including content
updates:
• Baseline Business Architecture (vision)
• Baseline Data Architecture (vision) • Gap analysis results
• Baseline Application Architecture • Technical requirements

(vision) • Updated business requirements
• Baseline Technology Architecture Business Architecture components of
(vision) an Architecture Roadmap
• Target Business Architecture (vision)
• Target Data Architecture (vision)
• Target Application Architecture (vision)
• Target Technology Architecture (vision)

C Data Architecture
Phase C: Information Systems Architectures – Data Architecture
To define the types and sources of Select reference models, Request for Architecture Work Statement of Architecture Work,
data needed to support the viewpoints, and tools Capability Assessment updated if necessary
business, in a way that can be Develop Baseline Data Validated data principles, or new data
Communications Plan
understood by the stakeholders Architecture Description principles
Organizational Model for Enterprise Architecture
Develop Target Data Architecture Draft Architecture Definition
Description Document containing content
Data principles updates:
Perform gap analysis
Statement of Architecture Work • Baseline Data Architecture
Define roadmap components
Architecture Vision • Target Data Architecture
Resolve impacts across the
Architecture Landscape Architecture Repository • Data Architecture views
Draft Architecture Definition Document containing: corresponding to the selected
Conduct formal stakeholder viewpoints, addressing key
review • Baseline Business Architecture (detailed) stakeholder concerns
Finalize the Data Architecture • Target Business Architecture (detailed)
Create Architecture Definition • Baseline Data Architecture (vision)
Specification including content
Document • Target Data Architecture (vision) updates:
• Baseline Application Architecture (detailed or
• Gap analysis results
vision)
• Data interoperability requirements
• Target Application Architecture (detailed or
• Relevant technical requirements
vision)
that will apply to this evolution of
• Baseline Technology Architecture (vision)
the architecture development cycle
• Constraints on the Technology
Draft Architecture Requirements Specification Architecture
including: • Updated business requirements
• Gap analysis results • Updated application requirements
• Relevant technical requirements Data Architecture components of an
Business Architecture components of an Architecture Roadmap
Architecture Roadmap

C Application Architecture
Phase C: Information Systems Architectures – Application Architecture
To define the kinds of Select reference models, Request for Architecture Work Statement of Architecture Work,
application systems necessary viewpoints, and tools Capability Assessment updated if necessary
to process the data and support Develop Baseline Application Validated application principles, or new
Communications Plan
the business Architecture Description application principles
Organizational Model for Enterprise Architecture
Develop Target Application Draft Architecture Definition Document
Architecture Description containing content updates:
Application principles
Perform gap analysis • Baseline Application Architecture
Statement of Architecture Work • Target Application Architecture
Architecture Vision • Application Architecture views
Architecture Landscape Architecture Repository corresponding to the selected
Draft Architecture Definition Document containing: viewpoints, addressing key
Conduct formal stakeholder stakeholder concerns
review • Baseline Business Architecture (detailed)
Finalize the Application • Target Business Architecture (detailed)
Specification including content updates:
Architecture • Baseline Data Architecture (detailed or vision)
Create Architecture Definition • Target Data Architecture (detailed or vision)
• Application interoperability
Document • Baseline Application Architecture (vision)
requirements
• Target Application Architecture (vision)
• Relevant technical requirements that
will apply to this evolution of the
architecture development cycle
Draft Architecture Requirements Specification • Constraints on the Technology
including: Architecture
• Gap analysis results • Updated business requirements
• Relevant technical requirements • Updated data requirements
Business and Data Architecture components of Application Architecture components of
an Architecture Roadmap an Architecture Roadmap

D Technology Architecture
Phase D: Technology Architecture
To develop a Target Technology Select reference models, Request for Architecture Work Statement of Architecture Work,
Architecture that will form the viewpoints, and tools Capability Assessment updated if necessary
basis of the following Develop Baseline Technology Validated technology principles or new
Communications Plan
implementation and migration Architecture Description technology principles (if generated
planning Organizational Model for Enterprise Architecture
Develop Target Technology here)
Architecture Description Draft Architecture Definition Document
Technology principles containing content updates:
Perform gap analysis
Statement of Architecture Work • Baseline Technology Architecture
Architecture Vision • Target Technology Architecture
Architecture Landscape Architecture Repository • Technology Architecture views
Draft Architecture Definition Document corresponding to the selected
Conduct formal stakeholder review viewpoints, addressing key
containing:
Finalize the Technology stakeholder concerns
Architecture • Baseline Business Architecture (detailed)
• Target Business Architecture (detailed)
Create Architecture Definition Specification including content
Document • Baseline Data Architecture (detailed)
updates:
• Target Data Architecture (detailed)
• Baseline Application Architecture (detailed)
• Requirements output from Phases
• Target Application Architecture (detailed)
B and C
• Updated technology requirements
Technology Architecture components
Draft Architecture Requirements Specification
of an Architecture Roadmap
including:
• Relevant technical requirements
Business, Data, and Application Architecture
components of an Architecture Roadmap

E Opportunities & Solutions
Phase E: Opportunities & Solutions
To review the target business Determine/confirm key corporate Product information Statement of Architecture Work, updated if
objectives and capabilities, change attributes Request for Architecture Work necessary
consolidate the gaps from Phases Determine business constraints for Architecture Vision, updated if necessary
Capability Assessment
B to D, and then organize groups implementation
Communications Plan Draft Architecture Definition Document,
of building blocks to address these
Review and consolidate gap analysis including content updates for:
capabilities Planning methodologies
results from Phases B to D • Identification of increments
To review and confirm the Organizational Model for Enterprise
Review IT requirements from a • Interoperability and co-existence
enterprise’s current parameters for Architecture
functional perspective requirements
and ability to absorb change Governance models and frameworks
Consolidate and reconcile • Inclusion of project list and project charters
To derive a series of Transition Tailored Architecture Framework
interoperability requirements Draft Architecture Requirements Specification,
Architectures that deliver
Refine and validate dependencies Statement of Architecture Work updated if necessary
continuous business value (e.g.,
capability increments) through the Confirm readiness and risk for Architecture Vision Consolidated and validated Architecture
exploitation of opportunities to business transformation Architecture Repository Roadmap
realize the building blocks Formulate high-level Implementation Draft Architecture Definition Capability Assessment, including content
To generate and gain consensus and Migration Strategy Document updates for:
on an outline Implementation and Identify and group major work Draft Architecture Requirements • Enterprise Architecture Maturity Profile
Migration Strategy packages Specification • Transformation Readiness Report
Identify Transition Architectures Change Requests for existing Transition Architectures, including:
Create portfolio and project charters programs and projects • Consolidated Gaps, Solutions, and
and update the architectures Dependencies Assessment
• Risk Register
• Impact analysis – project list
• Dependency Analysis Report
• Implementation Factor Assessment and
Deduction Matrix
Implementation and Migration Plan (outline)

F Migration Planning
Phase F: Migration Planning
To ensure that the Implementation and Confirm management framework Request for Architecture Work Implementation and Migration Plan
Migration Plan is coordinated with the interactions for Implementation and Capability Assessment (detailed)
various management frameworks in Migration Plan Finalized Architecture Definition
Communications Plan
use within the enterprise Assign a business value to each Document
Organizational Model for Enterprise
To prioritize all work packages, project Finalized Architecture Requirements
Architecture
projects, and building blocks by Estimate resource requirements, Specification
assigning business value to each and Governance models and frameworks
project timings, and availability/delivery Finalized Architecture Roadmap
conducting a cost/business analysis vehicle Tailored Architecture Framework
Finalized Transition Architecture
To finalize the Architecture Vision and Prioritize the migration projects through Statement of Architecture Work
Architecture Definition Documents, in Re-Usable Architecture Building Blocks
the conduct of a cost/benefit Architecture Vision
line with the agreed implementation assessment and risk validation Requests for Architecture Work for the
approach Architecture Repository
architecture aspects of implementation
Confirm Transition Architecture Draft Architecture Definition Document,
To confirm the Transition Architectures projects (if any)
increments/phases and update including:
defined in Phase E with relevant Architecture Definition Document Architecture Contracts for
stakeholders • Strategic Migration Plan implementation projects
Generate the Architecture • Impact analysis – project list and
To create, evolve, and monitor the Implementation Roadmap (Time-Lined) Implementation Governance Model
detailed Implementation and Migration charters
and Migration Plan Change Requests arising from lessons
Plan providing necessary resources to Draft Architecture Requirements learned
Establish the architecture evolution Specification
enable the realization of the Transition
cycle and document lessons learned
Architectures, as defined in Phase E Change Requests for existing
programs and projects
Consolidated and validated
Architecture Roadmap
Transition Architecture
Implementation and Migration Plan
(outline)

G Implementation Governance
Phase G: Implementation Governance
To formulate recommendations for Confirm scope and priorities for Request for Architecture Work Architecture Contract (signed)
each implementation project deployment with development Capability Assessment Compliance Assessments
To govern and manage an Architecture management
Organizational Model for Enterprise Change Requests
Contract covering the overall Identify deployment resources and Architecture Architecture-compliant solutions
implementation and deployment skills
Tailored Architecture Framework deployed, including:
process Guide development of solutions
Statement of Architecture Work • The architecture-compliant
To perform appropriate governance deployment
Architecture Vision implemented system
functions while the system is being Perform enterprise architecture • Populated Architecture Repository
implemented and deployed compliance reviews Architecture Repository
• Architecture compliance
To ensure conformance with the Implement business and IT operations Architecture Definition Document recommendations and
defined architecture by implementation Architecture Requirements dispensations
Perform post-implementation review
projects and other projects Specification
and close the implementation • Recommendations on service
To ensure that the program of Architecture Roadmap delivery requirements
solutions is deployed successfully, as a • Recommendations on performance
planned program of work Transition Architecture
metrics
To ensure conformance of the Implementation Governance Model
• Service Level Agreements (SLAs)
deployed solution with the Target Architecture Contract
• Architecture Vision, updated post-
Architecture Request for Architecture Work implementation
To mobilize supporting operations that identified in Phases E and F • Architecture Definition Document,
will underpin the future working lifetime Implementation and Migration Plan updated post-implementation
of the deployed solution • Transition Architecture, updated
post-implementation
• Business and IT operating models
for the implemented solution

H Architecture Change Management
Phase H: Architecture Change Management
To ensure that baseline architectures Establish value realization process Request for Architecture Work Architecture updates
continue to be fit-for-purpose Deploy monitoring tools identified in Phases E and F Changes to architecture framework
To assess the performance of the Manage risks Organizational Model for Enterprise and principles
architecture and make Architecture New Request for Architecture Work, to
Provide analysis for architecture
recommendations for change Tailored Architecture Framework initiate another cycle of the ADM
change management
To assess changes to the framework Statement of Architecture Work Statement of Architecture Work,
Develop change requirements to meet
and principles set up in previous updated if necessary
performance targets Architecture Vision
phases
Manage governance process Architecture Repository Architecture Contract, updated if
To establish an architecture change necessary
management process for the new Activate the process to implement Architecture Definition Document
change Compliance Assessments, updated if
enterprise architecture baseline that is Architecture Requirements
necessary
achieved with completion of Phase G Specification
To maximize the business value from Architecture Roadmap
the architecture and ongoing Change Requests due to technology
operations changes
To operate the Governance Change Requests due to business
Framework changes
Change Requests from lessons
learned
Transition Architecture
Implementation Governance Model
Architecture Contract (signed)
Compliance Assessments
Implementation and Migration Plan


N093 PDF

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

N093 PDF

Uploaded by

Copyright:

Available Formats

ADM

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

• Baseline Application Architecture • Technical requirements

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

Copyright © 2009 The Open Group. All Rights Reserved.

You might also like