• TOGAF is developed and maintained by members of The Open Group, working within the Architecture Forum.
• TOGAF is a framework for developing an enterprise architecture.
• The main focus has been on quality improvements to ensure consistent use of terminology.
• It may be used freely by any organization wishing to develop an enterprise architecture for use within that organization.
• TOGAF an Open Group standard, is a proven enterprise architecture methodology and framework used by the world's leading organizations to improve business efficiency.
• TOGAF helps practitioners avoid being locked into proprietary methods, utilize resources more efficiently and effectively, and realize a greater return on investment.
• TOGAF is an industry-standard architecture framework that may be used freely by your organization to develop an information systems architecture.

•     Any organization undertaking,or planning to undertake, the development and implementation of an enterprise architecture for the support  of business transformation will benefit  from use ofTOGAF.
•     Organizations seeking Boundary less Information Flow can use TOGAF to define and implement the structures and processes to enable access to integrated information within and between  enterprises.
•     Organizations that design and implement enterprise architectures using TOGAF are assured of a design and a procurement specification that can facilitate an open systems implementation,thus enabling  the benefits of open systems with reduced risk.

• Enterprise (IT) Architects
• Business Architects
• Information Security Architects
• Individuals who require a deeper understanding of TOGAF 9
• Professionals who are working in an organization where TOGAF 9 has been adopted and who need to participate in architecture projects and initiatives
• Architects who will be responsible for developing architecture artifacts
• Architects who wish to introduce TOGAF 9 into an architecture practice
• Architects who want to achieve a recognized qualification to demonstrate their detailed knowledge of TOGAF 9.1

• In this course, you will gain the knowledge needed to prepare for and achieve both TOGAF® 9.1 Certification.
• You will learn the frameworks, structure, and concepts of TOGAF 9.1 and how to analyze and apply this knowledge.
• Delegates will understand the TOGAF 9 framework and how to practically apply it in support of the design and implementation of enterprise architecture.
• They will also learn how to apply TOGAF to create well-designed enterprise architectures through the use of practical scenarios and case study working.

•     Stakeholders and Values
•     What is an Enterprise?
•     What is an Architecture?
•     What is Enterprice Architecture?
•     Architecture Types
•     Why  Enterprise Architecture?
•     Pressure  to develop Enterprise Architecture
•     Business Benefits of Enterprise Architecture
•     The Importance of Governance
•     What do we mean by Governance?

•     The Value  of a Framework
•     Enterprise Architecture Development Method
•     TOGAF  Origins
•     TOGAF  Development
•     TOGAF  Scope
•     TOGAF  Goals
•     TOGAF  9 Components

•     ADM—Basic Principles
•     Preliminary Phase
•     Phase A : Architecture Vision
•     Phase B : Business  Architecture
•     Phase  D : Technology Architecture
•     Phase  E : Opportunities and Solutions
•     Phase  F : Migration Planning
•     Phase  G : Implementation Governance
•     Phase H : Architecture Change Management
•     TOGAF  Certification
•     TOGAF  Foundation Target Audience
•     TOGAF  Certified Target Audience

•     Objectives
•     TOGAF  9 Components
•     Roadmap
•     The Architecture Development Method
•     ADM Guidelines and Techniques
•     Applying Iteration to the ADM
•     Categories of Stakeholder
•     Architecture Content Framework
•     Deliverables, Artifacts and Building Blocks
•     Full Content Metamodel with Relationships

•      Architecture Repository
•     TOGAF  Reference Models
•      High-Level TRM
•      Detailed TRM
•      Boundaryless Information  Flow™
•      Capability Framework

•     What is the TOGAF ADM?
•     Architecture Development Method –Process
•     Relationship to other Parts of TOGAF
•     ADM  Phases
•     ADM  Phase Steps Example
•     ADM Inputs and Outputs
•     Adapting the ADM
•     Governing the ADM
•     Governance Repository
•     Reasons  to Constrain the Scope of Architectural Activity
•     Scoping the Architecture Activity
•     Architecture Integration

•     Roadmap
•     Architecture Reuse
•     Enterprise Continuum: Constituents
•     The Architecture Continuum
•     The Solutions Continuum
•     Relationships
•     The Enterprise Continuum
•     Using the Continuum
•     Relationships
•     The Need  for Tools
•     Tools can Model the Enterprise Architecture
•     Issues  in Tool Standardization

•     Purpose
•     Architecture Repository
•     Architecture Landscape
•     Reference Library
•     Standards Information Base
•     Standards Classification
•     Governance Log Contents
•     Relationship to other Parts of TOGAF
•     Exercise

•     Objectives
•     Introduction
•     Benefits of the Architecture Content Framework
•     Deliverables, Artifacts, and Building Blocks
•     Relationship between Deliverables,Artifacts
•     Architectural Artifacts
•     Content Metamodel
•     Mapping the Framework and the ADM
•     Content Framework and the TOGAF ADM

•     Objectives
•     What is a Metamodel
•     Why  a Metamodel
•     Benefits of Content Metamodel
•     Formal and Informal Modeling
•     Core  Content MetamodelConcepts
•     TOGAF  Content Metamodeland its Extensions
•     Core  MetamodelEntities
•     Core Entities and their Relationships
•     Stakeholder Needs

•     Objectives
•     Steps
•     Scope the enterprise organizations impacted
•     Confirm governance and support frameworks
•     Define the team and organization
•     Identify and establish architecture principles

•     Objectives
•     Architecture Governance in Practice
•     Architecture Board
•     Architecture Board Value
•     Architecture Board Responsibilities
•     Architecture Board Operations
•     Architecture Contracts
•     Architecture Contracts and ADM
•     Architecture Compliance: Terminology
•     Architecture Compliance
•     Architecture Compliance Reviews
•     Architecture Compliance Review Process
•     Establishing an Architecture Capability

•     What is a Business Scenario?
•     Business  Scenarios
•     Business  Scenarios and the ADM
•     What is a Good Business Scenario?
•     SMART
•     The Benefits of Business Scenarios
•     Who Contributes to a Business Scenarios?
•     Developing a Business Scenario

•     Benefits
•     Stakeholder Management
•     Step 1: Identify Stakeholders
•     Categories of Stakeholder
•     Step 2: Classify Stakeholder Positions
•     Example: Stakeholder Map

•     Concepts and Definitions
•     System
•     Stakeholders
•     Concerns
•     View
•     Viewpoint
•     Views  and Viewpoints
•     What is an Architecture View?
•     A Simple Example of a Viewpoint
•     A Simple Example of a View
•     Developing Views in the

•     ABB Specifications
•     Solution Building  Blocks (SBBs)
•     Building Blocks and the ADM
•     Building Block Design
•     Architecture Patterns
•     F 6: ADM  phases  level  1
•     Objectives
•     Preliminary Phase
•     Objectives in detail
•     Approach
•     Phase A Architecture Vision
•     Business  Scenarios

• Objectives
• Readiness Factors
• Assess the Readiness Factors
• Readiness Factor Rating
• Readiness Factor Risks & Actions
• Risk Management
• Risk Management in the ADM
• Initial Risk Assessment
• Risk Classification Scheme

Objectives
Steps
Step 1: Establish the Project
Step 2: Identify Stakeholders
Step 3: Confirm Business Goals,Drivers and Con­
straints
Step 4: Evaluate Business Capabilities Value Chain
Diagram
Step 5: Assess Readiness for Business Transforma­
tion
Step 6: Define the  Scope
Step 7: Confirm and Elaborate Architecture Principles and Business

• Diagrams and matrices
• Catalogs, Matrices and Diagrams
• Catalogs
• Exercise
• Matrices
• Business Interaction Matrix
• Actor/Role Matrix

• Information Systems Architectures-Objectives
• Approach
• Top-Down Design-Bottom-Up Implementation
• Approach:Architecture Repository
• Considerations for Data Architecture

• Technology Architecture:Inputs
• Steps
• TOGAF 9 Artifac t s
• Tec hnology Architecture Outputs
• Cata l ogs,Matrices,and Di agra ms

• Module Objectives
• Approach
• Phase E:Inputs
• Steps
• Phase E Outputs
• TOGAF 9 Artifacts
• Project Context Diagram
• Benefits Diagram

• The Consolidated Gaps,Solutions
• Architecture Definition Increments table
• The Transition Architecture State Evolution Table
• The Business Value AssessmentTechnique

• Module Objectives
• Phase G Objectives
• Approach
• Phase G:Inputs
• Steps
• Phase G Outputs

• Maintenance versus Redesign
• Change Impact Exercise
• Phase H: Inputs
• Change Requests
• Steps
• Phase H Outputs
• Business Users'Architecture Contract
• Request for Architecture Work

• Maintenanc e versus Redesign
• Change Impact Exercise
• Phase H: Inputs
• Change Requests
• Steps
• Phase H Outputs
• Business Users'Architecture Contract
• Request for Architecture Work

•     Steps in Data Architecture Phase
•     Select reference models, viewpoints, and tools
•     TOGAF  9 Artifacts
•     Develop a Baseline Data Architecture  Description
•     Develop Target Data Architecture Description
•     Perform Gap Analysis
•     Define Candidate Roadmap Components
•     Resolve impacts across the Architecture
•     Conduct Formal Stakeholder Review
•     Finalize the Data Architecture
•     Create Architecture Definition Document

•     Objectives
•     Key Business and Technical Drivers
•     TOGAF  TRM
•     TOGAF TRM Orientations
•     Catalogs, Matrices, and Diagrams
•     Catalogs
•     Exercise
•     Matrices
•     Data  Entity/Business Function Matrix

•     Matrices
•     Application/Organization Matrix
•     Example Application/Organization Matrix
•     Role/Application Matrix
•     Example Role/Application Matrix
•     Application/Function Matrix
•     Diagrams
•     Application Communication Diagram
•     Application and User Location Diagram
•     Application Use Case Diagram
•     Enterprise Manageability Diagram

•     TOGAF  Foundation Architecture
•     Technical Reference Model Components
•     The Technical Reference Model
•     Taxonomy of Platform Services
•     Taxonomy of Application Platform Service Qualities

•     Module Objectives
•     ADM Requirements Management
•     Requirements Development
•     Resources
•     Volère
•     Requirements Specifications Template
•     Requirements Management: Inputs
•     Requirements Management: Outputs
•     Requirements Impact Assessment

•     Module Objectives
•     Iteration and Levels
•     Iteration and the ADM
•     Iteration to Manage the Architecture Capability
•     A Hierarchy of ADM Processes
•     Architecture Development Iteration “Baseline First”
•     Architecture Development Iteration “Target First”
•     Transition Planning
•     Architecture Governance
•     Applying the ADM Across the Architecture Landscape

    Phase A: Architecture Vision
    Phase B: Business  Architecture
    Phase  C: Information Systems Architectures
    Phase D: Technology Architecture
    Phase  E: Opportunities and Solutions
    Phase  F: Migration Planning
    Phase  G: Implementation Governance
    Phase H: Architecture Change Management

•     module objectives
•     what is service oriented architecture?
•     preliminary phase
•     phase  a: architecture vision
•     architecture development: phases b,c, and d

•     module objectives
•     Capability Maturity Models
•     CMMI
•     US Department of Commerce ACMM
•     Maturity Assessments in the ADM
•     Architecture development: phases b,c, and d

TOGAF level 1 Information:

• Exam Duration : 60 minutes
• Number of Questions : 40 (1 question = 1 point)
• Pass Marks : 55% (22 Points out of 40 Points)
• Open book : No
• Electronic Device Permitted : No

TOGAF level 2 Information:

• Exam Duration : 90 minutes
• Number of Questions : 8 (1 question = 5 Points)
• Pass Marks : 60% (24 Points out of 40 Points)
• Open book : Yes
• Electronic Device Permitted : No