TOGAF 9.1 is a framework for developing enterprise architecture, detailing a method, tools, and guidelines for various architecture phases including architecture vision, information systems, business, and technology architectures. The framework emphasizes interoperability, strategic planning, and the importance of aligning IT with business objectives to optimize enterprise operations. The document outlines the history, core concepts, and benefits of using TOGAF for enterprise architecture development.

1. INTRODUCTION TO TOGAF 9.1

2. Where this fits in to TOGAF?
TOGAF 9
Introduction
Architecture
Development
Method
Architecture
Content Framework
Enterprise Continuum and Tools
TOGAF Reference Models
Architecture Capability Framework
Part I
Part II,III
ADM
ADM Guidelines
and Techniques
Introduction
Preliminary Phase
Phase A : Architecture Vision
Phase C: Information Systems Architecture
Phase B: Business Architecture
Phase D: Technology Architecture
Phase E: Opportunities & Solutions
Phase F : Migration Planning
Data Architecture
Application
Architecture
Phase G : Implementation Governance
Phase H : Architecture Change Management
Requirements Management
Introduction
Introduction
Core Concepts
Definitions
Release Notes
Introduction
Applying Iteration to the ADM
Applying the ADM at difference Enterprise Levels
Security Architecture and the ADM
Using TOGAF to Define & Govern SOAs
Architecture Principles
Stakeholder Management
Architecture Patterns
Business Scenarios
Gap Analysis
Migration Planning Techniques
Interoperability Requirement
Business Transformation Readiness Assessment
Risk management
Capability-Based Planning
Introduction
Content Metamodel
Architectural Artifacts
Architecture Deliverables
Building Blocks
Introduction
Enterprise Continuum
Architecture Partitioning
Architecture Repository
Tools for Architecture Development
Foundation Architecture : Technical Reference Model
Integrated Information Infrastructure Reference Model
Establishing an Architecture Capability
Architecture Board
Architecture Compliance
Architecture Contracts
Architecture Governance
Architecture Maturity Models
Architecture Skills Framework
Part IV
Part V
Part VI
Part VII
I
II,III
IV
V
VI
VII Part III
(The Practice)
Part II
(The Theory)

3. What is TOGAF?
• The Open Group Architecture Framework is a
framework – a detailed method and a set of
supporting tools – for developing an
enterprise architecture for use within that
organisation
• TOGAF is developed and maintained by
members of The Open Group, working with
the architecture forum

4. History of TOGAF
• 1994 the US Department of Defense gave
their Technical Architecture Framework for
Information Management (TAFIM) to TOGAF
for development
• 1995 TOGAF version 1 was released
• 2009 TOGAF version 9 was released

5. What was new in TOGAF 9
• Design objectives
– Evolution not revolution
• No change to the top level
processes
• Interoperability between TOGAF
8 and 9
– Stronger links to business
• Strategic Planning
• Deployment decisions
– Easier to use
• A More formal meta-model
• More guidelines and techniques
• Improved structure
• New sections
– Architecture Planning
– Content Framework and
Metamodeling
– Capability Based Planning
– Business Transformation
Readiness
– Architecture Repository
– Stakeholder Management
– Security
– SOA

6. Components of TOGAF 9
TOGAF Capability
Framework
TOGAF Enterprise
Continuum & Tools
TOGAF ADM
and
Content Framework
Architecture Capability Framework
(Part 7)
Architecture Development Method (Part 2)
ADM Guidelines and Techniques
(Part 3)
Introduction and Core Concepts ( Part 1)
Architecture Content Framework
(Part 4)
Enterprise Continuum and Tools (Part 5)
TOGAF Reference Models ( Part 6)
High level introduction and key
concepts, definition of terms
and release notes
Structured Meta-model for
architectural artifacts. Re-
useable architecture building
blocks
Taxonomies and tools to
categorise and store outputs
How to establish and operate
EA with an Organisation
Core of TOGAF, a step by step
guide to developing enterprise
architecture
Collections of Guidelines and
Techniques to apply with using
ADM
Two reference models that can
be applied to EA

7. TOGAF Documentation
Categorisation
• Core
– Fundamental concepts that form the essence of TOGAF
• Mandated
– Normative parts of the TOGAF specification
– Central top its use
– Would not be recognisable TOGAF if not used
• Recommended
– Pool of resources specifically referenced in TOGAF that can be used to
assist practitioners
• Supported
– Not referenced in the other three categories but can provide valuable
assistance

8. What is Enterprise Architecture?
• Architecture of an Enterprise
A formal description of a system, or
detailed plan of a system at
component level, to guide its
implementation
OR
The structure of components, their
inter-relationships, and the
guidelines governing their design
and evolution over time
The highest level ( typically) of
description of an organisation
and typically covers all missions
and functions. An enterprise will
often span multiple
organisations
“An effective enterprise architecture is critical to business
survival and success and is the indispensable means to
achieving competitive advantage through IT”

9. Why do we need Enterprise
Architecture?
• Optimise the often fragmented legacy of processes
(both manual and automated) into an integrated
environment that is responsive to change and
supportive of the delivery of the business strategy
• Good enterprise architecture helps achieve the right
balance between IT efficiency and business
innovation.

10. Benefits of Enterprise Architecture
• Create a more efficient IT Operations
– Lower software development, support and maintenance costs
– Increased portability of applications
– Improved interoperability and easier system and network management
– Improved ability to address critical enterprise-wide issues like security
– Easier upgrade and exchange of system components
• Better return on existing investment, reduced risk for future investments
– Reduced complexity in IT infrastructure
– Maximum return on investment in existing IT infrastructure
– Reduced risk overall in new investment, and the costs of IT ownership
• Faster, simpler and cheaper procurement
– Buying decisions are simpler, because the information governing
procurement is readily available in a coherent plan
– The procurement process is faster

11. What is an architecture framework
• Foundational structure used to develop a
broad range of different architectures.
• Provides a method to help design a target
state of the enterprise in terms of building
blocks, and to show how the building blocks
fit together
• Set of tools and common vocabulary
• List of recommended standards

12. Why use TOGAF as an architecture
framework
• 300 Architecture forum members
– Leading vendors and service providers
• Neutral and Open
• Plays a i porta t role de- ystify a d de-
risk the architecture develop e t process

13. Core Concepts of TOGAF
Architecture Capability
Techniques
and Tools
Architecture Development Method
Enterprise Continuum
Architecture Repository
Reference Library
Architecture Meta-model
Architecture Landscape
Standards Information Base
Architecture Continuum
Solution Continuum
Building
Blocks
Deliverables
Artifacts
The organisation structure, roles,
responsibilities, skills and process required
to practice Enterprise Architecture
Is a view of the
architecture
repository that
provides
methods for
classifying
architectures
and solution
artifacts as
they evolve
Stores
different
classes of
architecture
outputs at
different levels
of abstraction.
ADM provides
a tested and
repeatable
process for
delivering
architectures

14. Types of architecture domains
Enterprise
Architecture Business Architecture
IT Architecture
How the business
is organised to met
its objectives
How the information
System support the
objective of the business
Structure of the data assets
Information Systems or
Applications Architecture
Technology Architecture
Data Architecture
How the technology
fits together

15. Architecture Domains : Definitions
• Architecture Domain: The architecture area being considered
• Business architecture: The business strategy, governance, and key
business processes information as well as the interaction between these
concepts
• Application architecture: A description of the major logical groups of
capabilities that manage the data objects necessary to process the data
and support the business
• Data architecture: The structure of a orga isatio ’s logical a d physical
data assets and data management resources
• Technology architecture : The Logical software and hardware capabilities
that are required to support deployment of business, data and application
services, includes middleware, networks, communications etc.

16. Thank
You
For Free Demo you can call us at USA
: +1-610-686-8077