TOGAF 9.

1 – Big Picture
Architecture Principles, Vision, and Requirements
Technology Preliminary Architecture Vision
Architecture A. Architecture Vision
Domains Architecture Architecture High level model of candidate building
Enterprise Vision and Architecture Definition Business Strategy Technology Strategy
Business Principles,
Architecture Vision Stakeholders
Data Principles Objectives, and Drivers Preliminary
blocks
Business
Enterprise Vision and Architecture Definition
Architecture Requirements
Scope Enterprise Vision and Architecture Definition B. Business Architecture
Request for
Enterprise Requirements Constraints Assumptions Gaps C. Data/Application Architecture
Architecture Work
EnterpriseLevel D. Technology Architecture
EnterpriseLevelInitaitve Step 1: Select Reference Models, Viewpoints, and Tools
Enterprise Segment Vision & Architecture Definition
Organizational EnterpriseLevelInitaitve Business Architecture Information Systems Architecure Information Systems Statement of Step 2: Develop Baseline Architecture Decription
N
Depth LevelInitaitve IO Architecture Work High-level model of existing building blocks, re-using definitions form Architecture
Architecure UT
Segment Initaitve
Motivation Motivation Motivation
EC Repository where they are available
Capability Capability Capability EX A.
Vision Vision Vision Level Architecture Step 3: Develop Target Architecture Description
Architecture Architecture Architecture Initiative Vision Develop view of required building blocks through the creation of catalog, matrices, and
Definition Definition Definition Drivers Goals Objectives Measures Information H.
Data Entities Platform B. diagrams of the architecture document
System Contract Architecture
Services Business
Services Change
Architecture
Fully document each building block
Management
Document rationale for building block decisions in architecture document
Motivation Identify the impacted building blocks, checking against a library of building blocks
wirhin the Architecture Repository and re-using where appropriate
Logical Logical Logical
Where necessary, define new building blocks

DESIGN
Organization Location Actor, Role Data Application Technology G. C. Select standards for each building block, re-using as much as possible from reference
Components Components Components Implementati Requirements Information models selected from the Architecture Continuum

Transition
on Management System
Governance Architectures Document final mapping of the building blocks to the Architecture Landscape
From selected building blocks, identify those that might be re-used, and publish as
Motivation standards of reference models selected from the Architecture Repository
Business Processes, Physical Physical Physical
Srep 4: Perform Gap Analysis
Services, Events, Data Application Technology Identify building blocks carried over
Functions Components F.
Industry Organization-Specific Contracts, Controls, Components Components D. Identify eliminated building blocks
Foundation Common Systems
Architecture Architecture Service Qualities Products Migration Technology
Architecture Architecture
Planning Identify new building blocks
Contract E. Architecture
External factors Opportunities
Identify gaps and determine the realization approach (e.g. to be developed or to be
Provide context and procured)
Enterprise Continuum Architecture Realization
Solutions Step 5: Define Roadmap Components
NG Step 6: Resolve Impacts across the Architecture Landascape
Enterprise Repositories
(including Requirements
Architecture Context and Requirements Opportunities, Solutions, and Migration Planning Architecture Vision
L ANNI Step 7: Formal Stakeholder review
Repository, Architecture Capabilities Work Packages Architecture Contracts Standars Guidelines Specifications
P Step 8: Finalize the architecture
Contextual factors
Repository, Design Stores,
shape architectures Step 9: Create the Architecture Definition Document
and CMDB)

Architecture Continuum

The Enterprise Continuum

Generalization for future re-use E. Opportunities and Solutions
provides structure and Generic Specific Associate building block gaps with work packages
Architectures Architectures Architecture Repository
classification for assets in that will address the gaps
Enterprise Repositories.
Adaptation for use Architecture Metamodel
TOGAF Capability Framework
Architecture Method Content Metamodel

Informs the size, structure, and Sets targets, KPIs, plans, and budgets
culture of the capability for architecture roles Artifacts in the
Generalization for future re-use Deliverable: Architecture landscape are Reference
Architecture Capability structured according
Enterprise Repositories Generic Specific Definition Document Library
provide resources to be Architectures Architectures Framework to the metamodel
(Part VII) Best practice
classified within the Foundation
Enterprise Continuum. Adaptation for use Artifacts: Best practice Architectures Reference
Process Flow Diagram Artifacts describe building blocks Architecture creates models adopted
Effective operation of the Business Capability drives the need
Architecture Capability ensures for Architecture Capability Maturity
Building Blocks: Landscape reference Common Systems by the
External
Solutions Continuum Baseline Call Handling Process architecture Architectures enterprise
realization of the Business Vision Artifacts: Reference
Artifacts describe building blocks
Use-Case Diagram Models
Building Blocks: Industry
Solutions are instantiated Deployed solutions become Strategic
Customer Services Representative Architectures
within a deployment Architecture Context Architectures
Business need feeds into the The Architecture Capability
Artifacts: Adopted
Deployed Solutions operates a method Organiz.-Specific
method, identifying problems to be Architecture Use-Case Diagram by the The Reference
addressed Building Blocks: Architectures
enterprise Library is
Development Method The method delivers new business Target Call Handling Process governed
(Part II) solutions Artifacts: Segment Standards have
Process Flow Diagram Architectures reference
Business implementations
Business
Vision and The method refines understanding of
business need ADM Guidelines and Capabiliites
Drivers Techniques (Part III) Deliverables contain Artifacts Standards are Standards
Standards
Capability
complied with Informations Base adopted by the
The method produces content
to be stored in the Repository, Architectures enterprise
TOGAF ADM & External
classified according to the Business Standards
Architecture Content Framework
Standards
Enterprise Continuum
Content Best practice Data Standards
Framework creates
Architecture Deliverables Architecture Repository standards Application Standards
Foundation Common Systems Industry Organization-Specific (Part IV)
Solution Solutions Solution Solution Technology Standards
The landscape Compliance
Enterprise Continuum Catalogs Catalogs
The Enterprise Continuum and Operational changes update the is governed Is governed
Repository inform the business of and Tools Enterprise Continuum and Artifacts Matrices Matrices
current state (Part V) Repository Governance Log Visibility and
Diagrams Diagrams
Which are escalation
Compliance Capability
Decision Log
Assessments Assessments
TOGAF Reference Describing Describing
The business strategy Models (Part VI) Performance
Identification of Required Change Definition of Change Calendar Project Portfolio
identifies a need to change Building Blocks Building Blocks Measurement
Architecture
where the target is not
understood
Architectural Definition of Board
Foundational Change Initiatives Architecture
TOGAF Enterprise Continuum and Tools Board steers and
Supporting Business Strategy Other Deliverables
Architecture
Architecture Architecture Capability manages the
Deliverables
Architecture
Aspects of large Deliverables capability
Implementation of Learning from business operation creates new business need Deliverables Capability Capability Capability
The business The business strategy change initiatives Architectures Architectures Architectures
the architecture
strategy sets identifies need to require their own
must be governed
priority for change where the architectures
the portfolio target is well understood Governance Framework

Portfolio assessment Architectural Definition of Process Content

identifies specific Bounded Change Initiatives
need to change Take on, retirement Regulatory Requirements

Policy Management SLA and OLAs

Implementation of Change
Architectural Portfolio Implementation of Compliance Authority Structures
Repository

the architecture
Management of the Landscape must be governed Dispensation Organizational Standards
The portfolio Escalated issues
provides context influence the Assessment/selection of Technology/Product Set
Architectural Portfolio for governance portfolio Architectural Governance of - Models and Architectures
- Technologies and Products Architectures
Management of Projects Change Implementation
Business Control

Environment Management

Architecture activities that support the identification of a need to change.

Architecture activities that support the definition of how change can be achieved. Process Flow Control

Architecture activities that govern the implementation of change.

Gallotti Stefano© - http://www.galoz.it