1. An Overview of TOGAF® Version 9.1
21 April, 2017
An Overview of TOGAF® Version 9.1
Your card goes here!
44 Montgomery Street
Suite 960
San Francisco, CA
94104 USA
Tel
Fax
Name
Position
Slide deck for use by Open Group members only. Redistribution and commercial use prohibited without prior permission from The Open Group.
If you use this deck please acknowledge the source – thank you.
This is a technical overview of TOGAF, and specifically TOGAF Version 9.1
TOGAF is a registered trademark of The Open Group in the United States and other countries
Copyright © The Open Group 2011

2. Agenda Background on TOGAF® TOGAF® Version 9.1 TOGAF® 9 Certification
Q&A
This is the agenda for this deck 2 2

3. What is TOGAF®? TOGAF, an Open Group Standard:
A proven enterprise architecture methodology and framework used by the world's leading organizations to improve business efficiency
The most prominent and reliable enterprise architecture standard, ensuring consistent standards, methods, and communication among enterprise architecture professionals
Enterprise architecture professionals fluent in TOGAF standards enjoy greater industry credibility, job effectiveness, and career opportunities
TOGAF helps practitioners avoid being locked into proprietary methods, utilize resources more efficiently and effectively, and realize a greater return on investment
TOGAF(r), an Open Group Standard, is a proven enterprise architecture methodology and framework used by the world's leading organizations to improve business efficiency. It is the most prominent and reliable enterprise architecture standard, ensuring consistent standards, methods, and communication among enterprise architecture professionals. Enterprise architecture professionals fluent in TOGAF standards enjoy greater industry credibility, job effectiveness, and career opportunities. TOGAF helps practitioners avoid being locked into proprietary methods, utilize resources more efficiently and effectively, and realize a greater return on investment.

4. The Origins of TOGAF® A customer initiative
A framework, not an architecture
A generic framework for developing architectures to meet different business needs
Not a “one-size-fits-all” architecture
Originally based on TAFIM (U.S. DoD)
TOGAF is developed and maintained by The Open Group Architecture Forum. The first version of TOGAF, developed 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 TOGAF at regular intervals and published each one on The Open Group public web site.
TAFIM, Technical Architecture Framework for Information Management

5. Member (End User) Driven
Customer members demand architecture standards …
Customer members select TAFIM as preferred starting point…
DoD Information Systems Agency (DISA) donate TAFIM as base
TOGAF first published
TOGAF 7 – Technical Edition
‘93
‘94
‘96
‘01
TOGAF 9 Enterprise Edition
‘02
‘03
‘06
‘09
‘11
This is a view of the timeline , this illustrates the long maturation cycle.
As TOGAF has become more mature the time period between publications has also increased
TOGAF 9.1
TOGAF 8.1.1
The Interoperable Enterprise Business Scenario first published
TOGAF 8 – Enterprise Edition
First TOGAF Certification Program Launched

6. Why TOGAF® ? A comprehensive general method
Vendor, tool and technology neutral open standard
Complementary to, not competing with, other frameworks
Avoids re-inventing the wheel
Widely adopted in the market
Business IT alignment
Tailorable to meet an organization and industry needs
Based in best practices
This slide gives many of the reasons why TOGAF is suitable and widely chosen as an architecture framework
The graphic shown is the conceptual overview diagram for the TOGAF ADM illustrating the iterative cyclical nature of the process.
(This process model is sometimes referred as a ‘the crop circle’.)
Possible to participate in the evolution of the framework
Available under a free perpetual license

7. TOGAF® Momentum More than 100,000 downloads
Over 16,000 certified practitioners
More than 220 corporate members of The Open Group Architecture Forum
Over 55,000 TOGAF series books shipped
Association of Enterprise Architects membership at more that 20,000
Some stats 7

8. TOGAF® Certification Statistics
Foundation (3100)
Certified (7200)
Total (10,300) since February 2009
TOGAF® 8
7564
Some more stats

9. 21 April, 2017
TOGAF® 9 Market Drivers
Ongoing quest for Boundaryless Information Flow™
In a survey of members, the three most prominent views:
The need for closer alignment with the business
The desire for simple implementation, greater usability
The next version of TOGAF should be an evolution rather than a revolution
Consideration for different architectural styles, e.g. SOA
Security is an increasing concern for CIOs and Enterprise Architects due to disappearance of traditional boundaries
Need for greater detail on Architecture Development Method (ADM)
These were the market drivers behind the major revision that was TOGAF 9 9
© The Open Group 2008 9

10. Introducing TOGAF® 9
Developed, reviewed and approved by a collaborative of 300 members from some of the world’s leading IT customers and vendors
An evolution from TOGAF that preserves existing investments
The core Architecture Development Method
Existing investment in people - knowledge and skills
Existing investment in tools
Expanded detail and clarification of existing proof points
Restructured for better usability
More focused on holistic enterprise change
Clear links between business and IT objects
Increased consistency of output 10

11. TOGAF® 9.1 TOGAF 9.1 was released in December 2011
It is the first maintenance update to TOGAF 9
It is an upwards-compatible evolution from TOGAF 9, addressing usage feedback and comments raised
It addresses over 400 comments received
Contains over 450 changes
TOGAF 9 Technical Corrigendum 1 (Document U112) is available describing each change in detail
TOGAF 9.1 includes a set of maintenance updates based on feedback received on the 2009 publication of TOGAF 9. As such, the changes are upwards-compatible adding clarification, consistency, and additional details where needed. A separate document describing the changes including rationale is available as TOGAF 9 Technical Corrigendum 1 (Document U112).[1]
[1] TOGAF 9 Technical Corrigendum 1 can be obtained from

12. The TOGAF® 9.1 Standard
Part I - Introduction
Part II – Architecture Development Method
Part III – ADM Guidelines and Techniques
Part IV – Architecture Content Framework
Part V – Enterprise Continuum and Tools
Part VI – TOGAF Reference Models
Part VII – Architecture Capability Framework
Preface, Executive Overview, Core Concepts, Definitions and Release Notes
Introduction to ADM
ADM Phase Narratives
Architectural Artifacts
Architecture Deliverables
Building Blocks
Guidelines for Adapting the ADM Process
Techniques for Architecture Development
Enterprise Continuum
Architecture Partitioning
Architecture Repository
Tools for Architecture Development
Foundation Architecture: Technical Reference Model
Integrated Information Infrastructure Reference Model
Architecture Board
Architecture Compliance
Architecture Contracts
Architecture Governance
Architecture Maturity Models
Architecture Skills Framework
Content Metamodel
This slide shows the TOGAF 9.1 Specification table of contents, which remains the same as TOGAF 9

13. TOGAF Capability Framework
Modular Structure
Content Framework
Extended Guidance
Architectural Styles
Additional ADM detail
TOGAF Capability Framework
Architecture Capability Framework (Part VII)
Business Vision and Drivers
Business Capabilities
Ensures Realization
of Business Vision
Informs the capability
Sets targets, KPIs, budgets for architecture roles
Drives need for Architecture Capability maturity
TOGAF ADM &
Content Framework
Architecture Development Method (Part II)
Refines
Understanding
Business needs feed into method
Delivers new business solutions
ADM Guidelines & Techniques (Part III)
Architecture Content Framework (Part IV)
TOGAF Enterprise Continuum & Tools
The structure of the TOGAF standard reflects the structure and content of an architecture capability within an enterprise
The architecture capability operates a method (click)
The method is supported by a number of guidelines and techniques (click)
And produces content to be store in the repository (click) the content is classified according to the Enterprise continuum (click) which is populated initially with the TOGAF reference models.
This ties to the business as follows
Enterprise Continuum & Tools (Part V)
Informs the Business
of the current state
Operational changes cause updates
TOGAF Reference Models (Part VI)

14. TOGAF® 9 Components
This shows the structure in a graphical overview format calling out the main components
These are discussed briefly in the next few slides:
Architecture Development Method (ADM)
An iterative sequence of steps to develop an enterprise-wide architecture
ADM Guidelines and Techniques
Architecture Content Framework
TOGAF Reference Models
Technical Reference Model
I3RM: Integrated Information Infrastructure Reference Model, Supporting “Boundaryless Information Flow”
The Enterprise Continuum
A virtual repository of architecture assets. During application of the ADM, assets are created or drawn from existing assets, used, modified and returned to the virtual repository
The Architecture Capability Framework

15. The Architecture Development Method
The core of TOGAF
A proven way of developing an architecture
Specifically designed to address business requirements
An iterative method
A set of architecture views to ensure that a complex set of requirements are adequately addressed
The ADM is the core of TOGAF

16. 21/04/2017
ADM – Basic Principles
An iterative method, over the whole process, between phases and within phases
Each iteration = new decisions:
Enterprise coverage
Level of detail
Time horizon
Architecture asset re-use:
previous ADM iterations
other frameworks, system models, industry models,…
Decisions based on:
Competence / resource availability
Value accruing to the enterprise.
The ADM is iterative and circular. 16

17. Set the scope, constraints and expectations for a TOGAF project; create the Architecture Vision;
validate the business context; create the Statement of Architecture Work
Prepare the organization for a successful architecture project
ADM Phases
Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise
Develop Business Architecture
Develop baseline and target architectures and
analyze the gaps
Provide architectural oversight for the implementation; ensure that the implementation project conforms to the architecture
Develop Information Systems Architectures
Develop baseline and target architectures and
analyze the gaps
Analyze costs, benefits and risks; develop detailed Implementation and Migration Plan
Develop Technology Architecture
Develop baseline and target architectures and
analyze the gaps
ADM Phase overview
Ensure that every stage of a TOGAF project is based on and validates business requirements
Perform initial implementation planning; identify major implementation projects

18. ADM Phase Steps Example
The phases of the ADM cycle are further divided into steps; this example shows Phase B: Business Architecture phase.
A similar set of steps applies to phases C and D

19. ADM Guidelines and Techniques
A set of guidelines and techniques to support the application of the ADM
The guidelines help to adapt the ADM to deal with different scenarios, including different process styles (e.g. the use of iteration) and also specific requirements (e.g. security).
The techniques support specific tasks within the ADM (e.g. defining principles, business scenarios, gap analysis, migration planning, risk management, etc).
(TOGAF 9 Part III: ADM Guidelines and Techniques is a set of resources – guidelines, templates, checklists, and other detailed materials – that directly support application of the TOGAF ADM.
The individual guidelines and techniques are described in a separate part of TOGAF so that they can be referenced from the relevant points in the ADM as necessary, rather than having the detailed text clutter the description of the ADM itself.
Guidelines versus Technique
The guidelines provided with TOGAF describe how the ADM process can be adapted to deal with a number of different usage scenarios, including different process styles (e.g., the use of iteration) and also specific specialty architectures (such as security).
The techniques described within TOGAF 9 Part III support specific tasks within the ADM (e.g., the gap analysis technique, principles, etc.).
Some examples follow

20. Applying Iteration to the ADM
21 April, 2017
Applying Iteration to the ADM
An example from ADM Guidelines and Techniques is how to apply iteration. This is a Guideline
Example Guideline
© The Open Group 2008 20

21. Applying the ADM Across the Architecture Landscape
21 April, 2017
Applying the ADM Across the Architecture Landscape
Similarly it provides guidance on applying the ADM at different levels across the Architecture Landscape. This is another Guideline
Example Guideline
© The Open Group 2008 21

22. Categories of Stakeholder
Part III contains the Stakeholder Management Technique to support application of the ADM
Example Technique

23. Architecture Content Framework
Provides a detailed model of architectural work products, including Deliverables, Artifacts within deliverables, and the Architecture Building Blocks (ABBs) that deliverables represent.
It drives for greater consistency in the outputs of TOGAF
It provides a comprehensive checklist of architecture outputs
It promotes better integration of work products
It provides a detailed open standard for how architectures should be described
It includes a detailed metamodel
Part IV of the TOGAF 9 document is the Architecture content framework.
(During application of the ADM process, a number of outputs are produced; for example, process flows, architectural requirements, project plans, project compliance assessments, etc. In order to collate and present these major work products in a consistent and structured manner, TOGAF defines a structural model – the TOGAF Architecture Content Framework – in which to place them.
We look at Deliverables, Artifacts and Architecture Building Blocks next

24. Deliverables, Artifacts and Building Blocks
The Architecture Content Framework provides three categories to describe architectural work products
The Architecture Content Framework uses the following three categories to describe the type of architectural work product within the context of use:
Deliverables
Formal products
Contractually specified
Outputs from a project
A deliverable can contain many artifacts
Building blocks
components that can be combined with other building blocks to deliver architectures and solutions
Artifacts
fine grained products that describe an architecture from a specific viewpoint
For example: use-case specifications, architectural requirements, network diagrams, etc.
Classified as:
Catalogs (lists of things),
matrices (showing relationships between things) or
diagrams (pictures of things).
Artifacts make up the content of the Architecture Repository
(longer explanations)
A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders. Deliverables represent the output of projects and those deliverables that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.
An artifact is an architectural work product that describes an aspect of the architecture. Artifacts are generally classified as catalogs (lists of things), matrices (showing relationships between things), and diagrams (pictures of things). Examples include a requirements catalog, business interaction matrix, and a use-case diagram.. An architectural deliverable may contain many artifacts and artifacts will form the content of the Architecture Repository.
A building block represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions.

25. Full Content Metamodel with Relationships
This is the full content metamodel with relationships. We won’t be going into this level of detail in this overview talk

26. The Enterprise Continuum
Part V of TOGAF: The Enterprise Continuum is a “virtual repository” of all the architecture assets – models, patterns, architecture descriptions, etc. –
The Enterprise Continuum, sets the broader context for an architect and explains how generic solutions can be leveraged and specialized in order to support the requirements of an individual organization. The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures. The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum.
This diagram shows an overview of the context and constituents of the Enterprise Continuum.
The Enterprise Continuum is partitioned into three distinct continua:
The Enterprise Continuum is the outermost continuum and classifies assets related to the context of the overall enterprise architecture.
The Enterprise Continuum classes of assets may influence architectures, but are not directly used during the ADM architecture development. The Enterprise Continuum classifies contextual assets used to develop architectures, such as policies, standards, strategic initiatives, organizational structures, and enterprise-level capabilities. The Enterprise Continuum can also classify solutions (as opposed to descriptions or specifications of solutions). Finally,
the Enterprise Continuum contains two specializations, namely the Architecture and Solutions continuum

27. Architecture Repository
21 April, 2017
Architecture Repository
Supporting the Enterprise Continuum is the concept of an Architecture Repository which can be used to store different classes of architectural output at different levels of abstraction, created by the ADM. In this way, TOGAF facilitates understanding and co-operation between stakeholders and practitioners at different levels.
(In 9.1 we have added the Enterprise Repository explicitly to the diagram)
© The Open Group 2008 27

28. TOGAF® Reference Models
Two Reference Models are provided
The TOGAF Technical Reference Model (TRM)
A Foundation Architecture
A model and a taxonomy of generic platform services
The Integrated Information Infrastructure Model (III-RM).
A model for business applications and infrastructure applications
Specifically aimed to support the vision of Boundaryless Information Flow™
Part VI: The TOGAF Technical Reference Model (TRM), provides a model and taxonomy of generic platform services
It is a Foundation Architecture: “An architecture of generic services and functions that provides a foundation on which more specific architectures and architectural components can be built”.
III-RM
The Open Group has documented the business scenario that led to the creation of the Integrated Information Infrastructure Reference Model (III-RM) in the Interoperable Enterprise Business Scenario (K022). This is freely available for download from the Business Scenarios section of The Open Group online bookstore at

29. High-Level TRM
The coarsest breakdown of the TRM is shown in Technical Reference Model - High-Level View , which shows three major entities (Application Software, Application Platform, and Communications Infrastructure) connected by two interfaces (Application Platform Interface and Communications Infrastructure Interface).
The diagram says nothing about the detailed relationships between the entities; only that they exist.
Each of the elements in this diagram will be discussed in detail later.

30. Detailed TRM
The detailed TRM is only a depiction of the TRM entities: it neither implies nor inhibits inter-relationships among them.
IT architectures derived from TOGAF may differ greatly depending on the requirements of the information system. In practice, many architectures will not include all of the services discussed here, and many will include additional services to support Application Software that is specific to the organization or to its vertical industry.
In building an architecture, users of TOGAF should assess their own requirements and select the services, interfaces, and standards that satisfy their own business needs.
(Ch 43 of TOGAF)

31. The Integrated Information Infrastructure Reference Model (III-RM)
This is pronounced I3-RM. Closer to the solution space than the TRM.
An example of a Common Systems Architecture
So a lower level abstraction than the TRM
Based on the TRM
Aimed at the helping the design of architectures to enable and support the vision of Boundaryless Information Flow
III-RM The Open Group has documented the business scenario that led to the creation of the Integrated Information Infrastructure Reference Model (III-RM) in the Interoperable Enterprise Business Scenario (K022). This is freely available for download from the Business Scenarios section of The Open Group online bookstore at

32. Capability Framework 21 April, 2017 © The Open Group 2008 32
TOGAF 9 provides an Architecture Capability Framework that is a set of reference materials and guidelines for establishing an architecture function or capability within an organization.
A structured definition of the organizations, skills, roles and responsibilities to establish and operate an Enterprise Architecture, including:
Terms of Reference for an Architecture Board
Guidance on measuring levels of Architecture Compliance against Architecture contracts
Processes and organization structures required to operate Architecture Governance
Techniques for assessing Architecture Maturity
An overview of the Skills required by practicing architects
© The Open Group 2008 32

33. Stand-alone or Complementary
TOGAF 9
Zachman Framework
Support or
Guidance
DoD Architecture Framework
Other Frameworks
Federal Enterprise Architecture Framework

34. Complementary ITIL COBIT Framework, method and resources
TOGAF 9
ITIL
Framework, method and resources
IT Service Management
Best Practice
COBIT
Modeling languages and notation
Governance and control

35. Value of TOGAF® Certification
A globally recognized standard, backed by certification
Certified professionals
Demonstrable knowledge of TOGAF
Minimizes employers' hiring time and improves quality of hires
Vendors of TOGAF Certified Products or Services
Warrant conformance to the TOGAF product standard throughout the lifetime of certification
Customers who procure are assured of compliance
Certification credentials can readily be verified

36. TOGAF® Certification Certification Level Purpose TOGAF 9 Foundation
To provide validation that the candidate has gained knowledge of the terminology and basic concepts of TOGAF 9 and understands the core principles of Enterprise Architecture and TOGAF
TOGAF 9 Certified
To provide validation that in addition to knowledge and comprehension, the candidate is able to analyze and apply knowledge of TOGAF
The TOGAF For People Certification program for TOGAF 9 has two levels of certification, an entry level known as TOGAF 9 Foundation and a higher level known as TOGAF 9 Certified
These are described in further detail on the next few slides

37. TOGAF® 9 Certification

38. Summary TOGAF®, an Open Group Standard, is…
An effective, industry standard framework and method for enterprise architecture.
Complementary to, not competing with, other enterprise frameworks
A repository of best practice
Vendor, tool, and technology neutral
A framework and method for achieving the “Boundaryless Information Flow” vision
This is a brief summary of TOGAF 9.1.

39. Questions?

40. For More Information . . . The TOGAF Web Site The Architecture Forum
The Architecture Forum
TOGAF Version 9.1 on-line
TOGAF Version 9.1 licensing and downloads

41. TOGAF® Version 9.1 TOGAF Version 9.1, “The Book” Document No. G116
The TOGAF Specification

42. TOGAF® Version 9.1 Pocket Guide
TOGAF Version 9, The Pocket Guide
Document No. G117
The TOGAF Pocket Guide

43. TOGAF® 9 Certification Self Study Pack
Preparation for the TOGAF 9 Part 1 and Part 2 Examinations
Includes Study Guides, Practice tests, Pocket Guide, Reference Cards and more…
Document No. B097
The TOGAF Certification Self Study Pack 2nd edition covers TOGAF 9.1