1 in Pictures
Preliminary
Architecture
Vision
Architecture Business
Change Architecture
Management
Migration Technology
Planning Architecture
Opportunities
& Solutions
www.orbussoftware.com
The TOGAF ADM Cycle Set up an EA team and make sure it
Stage
can do its work
The ADM is about understanding existing architectures and working out the
best way to change and improve them. Preliminary: Although out of the main circle, you
need to keep referring back to it to assess effectiveness
Never used without some adaptation, the ADM is more like a cookbook of of both the EA team and its initiatives. This stage is
recommendations, ideas and checklists than a set way of doing things. about the on-going improvement of EA capabilities.
Preliminary
Think of it in three chunks and bear in mind that in a large enterprise, there Architecture Vision: This isnt a one-off before
may be quite a few projects all using different phases of the ADM. everything else - architecture visions emerge slowly.
And EA is unique in having a holistic view of all
stakeholders, complexity and change, and this is
3
constantly evolving. Communication is the key.
Stage
2
and then make it happen
Architecture
Get a good picture of the
Stage
Vision
Opportunities & Solutions: Here we move away architecture: Now and in the future
from a wholly architectural perspective to figure out Architecture Business
how youre going to deliver, fund and resource the Change Architecture
changes. Management
Business Architecture: Its important to be
Migration Planning: The detailed planning here is independent from technology - planned or current.
more the province of project managers than architects, Focus on business capabilities, process, and products,
but get involved to make sure commitment is in line and relate all analysis to business from an architectural
with the architecture vision. perspective.
Implementation Governance: Along with Information System Architcture: ISA breaks down
the policing role of monitoring each project Implementation Requirements Information
Systems
into data and applications. It doesnt matter which one
and solution, this plase needs a delicate political Governance you start with - its likely that youll have to adjust both
sensitivity to remind people of the long term vision
Management Architecture
as the bigger picture emerges.
and persuade them not to compromise.
Technology Architecture: Focus here is on
Architecture Change Management: When projects architecture of IT platforms, especially hardware
and solutions are unable to meet original expectations and communications. Its important to separate the
- due to cuts in spending, changes in priority or lack of different concerns of business, information systems
funding and resources - you need to revisit the other and technology stakeholders.
phases to address the consequences. Migration Technology
Planning Architecture
Requirements Management: At the heart of the
EA role, this is where a good EA can manage diverse
stakeholder concerns and create an integrated view
Opportunities
of how the architecture will evolve. All work products & Solutions
created or used in the other phases are managed here!
www.orbussoftware.com
Outputs
Preliminary
The Preliminary Phase This phase prepares the way for the initiation of the ADM. The outputs from
the steps conducted are the foundation from which the ADM is worked.
Almost all of the documentation produced in the Preliminary Phase Architecture
will be used as inputs to the other phases and/or will be Vision
Specifically, the Preliminary Phase is where definitions are established for: updated in each phase. Architecture
Change Business
Architecture
- What the enterprise is
Management
Inputs are gathered from many resources both internal and external. Ideally, they are obtained from Tailored Architecture
previous architecture work stored as artifacts and building blocks in a repository, but they can also Framework
be pulled from industry standards. Architecture Repository
Steps
Preliminary Phase steps center on identifying organizations involved, how the enterprise is governed, finding the right people to conduct the
transition from current to target architectures, firmly define principles by which all aspects of the transition can be judged, integrating TOGAF
into the corporate environment, and selecting the right tools for the right job.
www.orbussoftware.com
Outputs
Phase A - Architecture Vision
Preliminary
Starts with receipt of a Request for Architecture Work. Later Phases expand these initial outputs to produce the Architecture Business
Change
Its objectives are: detailed plan for delivering the proposed changes. Management
Architecture
- To develop a high-level vision of the capabilities and business value delivered
by the proposed enterprise architecture
- To gain approval for a Statement of Architecture Work that defines the Requirements Information
program of works to develop and deploy the proposed architecture.
Implementation
Architecture Vision Governance Systems
Management Architecture
including a problem
description, key requirements,
Inputs summary views and objectives
Migration
Planning
Technology
Architecture
The key input is the Request for Architecture Work, together with everything necessary to outline an
effective vision and proposed future architectures. Approved Statement of Opportunities
& Solutions
Architecture Work
including an overview of the
A Capability Assessment
Steps
This Phase is vital for outlining a resolution to Stakeholder concerns in architectural terms as an architecture vision and value
propositions and securing Stakeholder commitment and approval. All steps are important, but key steps are shown in purple!
Identify Stakeholders,
Concerns and Assess Readiness
Establish the Business Evaluate Business for Business Confirm and Elaborate
Architecture Project Requirements Capabilities Transformation Define Scope Architecture Principles
1 2 3 4 5 6
Identify Business
Define Target Transformation Develop Statement of
Develop Architecture Value Risks and Architecture Work and
Architecture Vision Propositions and KPI Mitigation Activities Secure Approval
7 8
9 10
www.orbussoftware.com
Inputs
Preliminary
- Identify candidate Architecture Roadmap components based upon gaps between the Governance Systems
Management Architecture
Request for Architecture Work
Baseline and Targert Architectures
Business principles, business goals,
- The Business Architecture describes how the enterprise needs to operate to achieve the
and business drivers
business goals, and respond to the strategic drivers set out in the Architecture Vision
Capability Assessment Migration Technology
- The Information Systems Architecture describes how it will enable the Business Planning Architecture
Communications Plan
Architecture and the Architecture Vision Opportunities
& Solutions
- The Technology Architecture shows how it enables the logical and physical Architectural Inputs
data components and the Architecture Vision
Organizational Model for EA
Tailored Architecture Framework
- Architecture principles
Steps
Architecture domains
- Application principles described by TOGAF Key
www.orbussoftware.com
Phase E - Opportunities and Outputs
Preliminary
Inputs
Draft Architecture Migration Technology
The key inputs are from the Architecture Definition Phases (B, C & D), which are then Definition Document
Planning Architecture
Draft Architecture
Reference Materials Architectural Inputs Requirements Specification
Architecture reference materials & T he Organizational model for EA, Governance
product information Model & Framework, Tailored Architecture
Architecture Roadmap
Capability Assessments
Framework, Architecture Repository
including Work
S tatement of Architecture Work &
Package Portfolio,
Architecture Vision
Non-Architectural Inputs Transition Architectures,
D raft Architecture Definition Document
(including baseline & target architectures)
Implementation & & Implementation
The Request for Architecture
Draft Architecture Requirements Specification Migration Plan (version 0.1) Recommendations
Work, Capability Assessment,
C andidate Architecture Roadmap
Communications Plan, & Planning
components from Phases B, C & D
Methodologies
Steps
Phase E is about architecture delivery. It amalgamates the gaps between Target & Baseline Architectures in all architecture domains, & groups changes into work packages to build a
best-fit roadmap based on stakeholder requirements, the enterprise's business transformation readiness, identified opportunities & solutions and implementation constraints.
1 2 3 4
www.orbussoftware.com
Outputs
Preliminary
Phase F - Migration Planning Outputs show dependencies, costs, and benefits of the various
migration projects in the final version of the Implementation and
Migration Plan. Architecture
Phase F is where we create an Implementation and Migration Plan
Vision
in co-operation with portfolio and project managers. The architecture development cycle is completed here, Architecture
Change
Business
- Finalize the Architecture Roadmap with lessons learned enabling continuous improvement Management
Architecture
- Finalize the supporting Implementation and Migration Plan, making sure that to the EA process.
it is coordinated with the enterprise change management approach and the
overall change portfolio
Requirements
- Ensure the value and cost of work packages and Transition Architectures is Implementation Information
Governance Systems
Management Architecture
understood by stakeholders
Implementation and
Inputs Migration Plan (Version 1.0)
including the Implementation and
Migration
Planning
Technology
Architecture
The key inputs are the incomplete Architecture Roadmap and Implementation and Migration Plan Migration Strategy, and the Project Opportunities
from Phase E and portfolio breakdown of the & Solutions
implementation
Reference Materials Architectural Inputs Reusable Architecture
Finalized Architecture Building Blocks
Any useful architecture reference T he Organizational Model for EA; Definition Document
materials (often from external Governance models and frameworks; including any Finalized Transition
sources) Tailored Architecture Framework; Architectures Request for Architecture
Statement of Architecture Work and
Work (for a new iteration
Architecture Vision
Non-Architectural Inputs of the ADM)
P opulated Architecture Repository, Finalized Architecture
including reusable building blocks Requirements Specification
The Request for Architecture
D raft Architecture Definition Document
Work, Capability Assessment and
and Architecture Requirements
Possible Change Requests
Communications Plan
for Architecture Capability
Specification Finalized Architecture
Steps
The level of detail addressed in Phase F will depend on the scope and goals of the overall architecture effort. All steps are important, but key steps are shown in purple!
www.orbussoftware.com
Outputs
Preliminary
Phase G - Implementation Governance Outputs show dependencies, costs, and benefits of the various
migration projects in the final version of the Implementation and
Migration Plan. Architecture
Vision
Phase G is where all the information for successful management of the
The architecture development cycle is completed here, Architecture
various implementation projects is brought together. In parallel is the Change
Business
with lessons learned enabling continuous improvement Management
Architecture
Architecture-Compliant
Reference Materials Architectural Inputs Solutions Deployed
including the implemented system,
Any useful architecture reference T he Organizational Model for EA; populated architecture repository,
materials (often from external Tailored Architecture Framework; Request compliance recommendations &
sources) for Architecture Work; Statement of dispensations, recommendations
Request for Architecture
Architecture Work and Architecture Vision on service delivery requirements & Work (for a new iteration
Populated Architecture Repository, performance metrics, Service Level of the ADM)
Non-Architectural Inputs
including reusable building blocks Agreements (SLAs)
Architecture Definition Document and
The Request for Architecture Work Post-implementation update
Architecture Requirements Specification
and Capability Assessment
Architecture Roadmap and Business and IT operating of Architecture Vision and
Implementation and Migration Plan models for the implemented Architecture Definition
Architecture Contract and Implementation solution Document
Governance Model
Steps
A key aspect of Phase G is ensuring compliance with the defined architecture(s), not only by the implementation projects,
but also by other ongoing projects. All steps are important, but key steps are shown in purple!
www.orbussoftware.com
Phase H - A
rchitecture Outputs
Preliminary
Change Management When the Foundation Architecture needs to be re-aligned with strategy,
substantial change is required to components, standards or guidelines
for their use that have a significant end-user impact (e.g. regulatory Architecture
Phase H ensures that the architecture achieves its original target changes), then a refreshment cycle (partial or complete Vision
business value, by managing changes to the architecture in a cohesive re-architecting) is required, and a new Request for Architecture Architecture
Change
Business
and architected way. Here we ensure that: Work must be issued (to move to another cycle). Management
Architecture
Inputs
Phase H is closely related to the architecture governance processes,and to management of the
Architecture updates and
changes to architecture
Migration Technology
Architecture Contract between the EA function and business users of the enterprise Planning Architecture
Any useful architecture reference T he Organizational Model for EA; New Request for
materials (often from external Tailored Architecture Framework; Request
Architecture Work, to move
sources) for Architecture Work; Statement of
Architecture Work and Architecture Vision
to another cycle
(for major changes)
Populated Architecture Repository,
Non-Architectural Inputs
including reusable building blocks
Architecture Definition Document and
The Request for Architecture Work
Architecture Requirements Specification
Statement of Architecture
Architecture Roadmap and Work, Architecture Contract
Implementation and Migration Plan
Architecture Contract and
Implementation Governance Model Compliance Assessments
Change Requests for business and
(updated if necessary)
technology changes and from lessons
learned; Compliance Assessments
Steps
The architecture change process determines how changes are to be managed, what techniques are applied, and what methodologies used. It also identifies
which phases of the ADM are impacted by changes e.g. changes that affect only migration may be of no interest to architecture development phases.
Provide Analysis for Develop Change
Establish Value Deploy Monitoring Architecture Change Requirements to Meet
Realization Process Tools Manage Risks Management Performance Targets
1 2 3 4 5
Manage Activate the Process to
Governance Process Implement Change
6 7
www.orbussoftware.com
Architecture Requirements Inputs
Preliminary
Management The Requirements Repository holds information from multiple ADM cycles.
The Architecture Requirements Specification and Requirements Impact
Assessment hold information for a specific project.
Architecture
Vision
The Requirements Management circle at the centre of the ADM graphic reminds us Architecture
that ADM is continuously driven by the requirements management process. In this Architecture Requirements Change
Management
Business
Architecture
phase we:
Specification
- Ensure that Requirements Management process is sustained and operates
for all ADM phases
- Manage architecture requirements identified during any execution of the A populated Architecture
Requirements Information
- Ensure that relevant architecture requirements are available for use by each Organizational Model for
phase Enterprise Architecture
Tailored Architecture Framework
Statement of Architecture Work Migration Technology
Architecture Vision Planning Architecture
Requirements Management itself does not dispose of, address, or prioritize any Requirements Specification
requirements, which is done in the relevant phase of the ADM. It is merely the process Requirements Impact Assessment
for managing requirements throughout the overall ADM. Hence the split between
steps below: Architecture requirements are invariably subject to change because
architecture deals with uncertainty and change. Dealing with changes in
Requirements Management Steps requirements is crucial -the grey area between what stakeholders aspire to
and what can be delivered as a solution.
Baseline requirements Monitor baseline requirements
1
2
www.orbussoftware.com
Business Scenarios
Preliminary
TOGAF 9.1: Guidelines and Techniques Method within a method to identify and articulate business requirements.
1 Problem
Architecture
2 5
Vision
Adapting the ADM Process Architecture Development Environment Computor Actors Architecture
Change
Business
Architecture
Management
Applying
the ADM Architecture
3 Objectives 6 Roles and
Responsibilities
4 7
Applying
Iteration to at Different Principles
Enterprise Capability- Stakeholder Human Actors Refine Implementation Requirements Information
the ADM Governance Systems
Levels Based Planning Management Management Architecture
Guidelines
Risk Architecture
Management Patterns
Using TOGAF Capability Based Planning Migration
Planning
Technology
Architecture
Security to Define & Techniques
Architecture Govern SOAS Business Capabilities of the enterprise. Opportunities
and the ADM Transformaon Business People & Solutions
Readiness Scenarios
Assessment
Information
Interoperability Management Process
Gap Analysis
Requirements Migration
Planning
Techniques
Stakeholder Analysis Capability Increment 3
Capability Increment 2
Win support from stakeholders. Capability Increment 1
Capability Increment 0
Research and
Material
Operations
Development
Communications
Management
Management
Management
Infrastructure
Service Desk
System
Application
Data/Voice
IT Service
Program
Management Scope
Organization
Office
Technical Specialist
Line Management
Functional Experts
Product Specialist
Business Process/
Executives
Architecture
Architecture
Architecture
Architecture
Architecture
Architecture
Organization
Transition
Transition
Transition
Transition
Transition
Transition
Line Management
Business Domain
End User
Data Owners
HR
Architecture
6
4
2
3
Executives
1
Experts
Depth
(Content)
Architecture Architecture Architecture Architecture Architecture Architecture
Realization Realization Realization Realization Realization Realization
www.orbussoftware.com
Content MetaModel - Broken Down
Preliminary
Organization Unit
Architecture Business
Change Architecture
Deliverables, artifacts, building blocks and relationships Motivation Ext.
Driver
its motivated by
contains
perform
task in
Role
accesses
owns produces
Process Modeling Ext. All object types can be nested,
and have decomposition
Management
Business Architecture
Goal produces
Matrices
Objective orchestrates
Diagrams Diagrams
Event Process
Governance Ext. Governance Ext.
generates
Which are Measure
Event
is resolved by
Process Service Quality Contract
meets
Describing Describing Measure
is bounded by Service Quality Contract
Infra. Consolidation Ext. orchestrates
consumes resolves
Location
consumes is processed by
Migration Technology
provides
Data Modeling Ext.
implements realizes provides platform for
Planning Architecture
Logical Application
Services Ext. Infra. Consolidation Ext.
Logical Data Component
Content Meta-Model - D
escription of Building Blocks
Physical Data Physical
Application Physical
Component Technology
Component
Component
Data Architecture contains Application Architecture contains Technology Architecture
Architecture Realization Search Progressively more General Architectures and Solutions for Candidate Components
Opportunities, Solutions, and Migration Planning Implementation Governance
Architecture
Capabilities Work Packages Contracts Standards Guidelines Specifications Architecture Continuum Solutions Continuum
Common Organization Common Organization
Foundation Industry Foundation Industry
Systems Specific Systems Specific
Viewpoints
www.orbussoftware.com
Architecture Capability Framework Preliminary
Technical Reference Model (TRM) Business Capability for Architecture (Operating at a level of maturity) Architecture
Change
Business
Architecture
A model and taxonomy of generic platform services Management
Participates in
Communication Infrastructure Skilled Resource Pool
Governance
Management Architecture
Project/Portfolio
Application Platform Interface
Training Governance
Setting
priority
and focus
Communication Infrastructure Interfaces
International Operations
Transaction Processing
Software Engineering
Roles and
Local and Directory
Data Management
Data Interchange
Projects/
User Interface
Responsibilities
Management
Delivering
Requires to a particular
solutions
aligned
project)
Participates in
Posses Posses Opportunities
Application Platform Assigned Business & Solutions
Architecture Professionals Projects/Portfolios Operations
Operating System Services
Application Platform Interface Populating the Re-using building blocks and
Network Services
Repository complying with standards
Communication Infrastructure Interface
Infra Apps Bus Apps Enterprise Continuum (used to classify inputs to and outputs from the Repository)
Communication Infrastructure
Architecture Repository
Integrated Information Infrastructure Reference Model (III-RM) Compliance Levels Skills Framework
Model for business applications and infrastructure applications
Compliance of projects Define roles, skills and experience
Essential part of architecture governance Measure staff development right fit
Application Format
Mobility Management Utilities Management Policy
Formulate IT compliance strategy
Qualities Information Consumer Brokering Applications Information Provider Qualities
Applications Applications
Security Development Tools Preformance SLAs
Enterprise Program/
Irrelevant Compliant
Roles Architecture Project IT Designer
Business Manager
Governance Architecture Views and
Creation and monitoring of architectural components Viewpoints Design
Building Block Design
CIO/CTO Consistent Fully Conformant
Stewardship
Solutions Modeling
Develop Implementation Deploy Enterprise Continuum
Program Benefits Analysis
Architecture Management Service
Chief Architect Board Management Architectures Processes Solutions
Office
Guidance Business Interworking
Alignment
Alignment
Regulatory
Enterprise Architects SLAs/OLAs
Requirements Compliant Non-Conformant Systems Behavior
Diffusion Authority Organizational
Domain
Architects Conformance
Implementation Change
Projects
Operational
Systems Structures Standards Project Management
1 2 3 4
www.orbussoftware.com