TOGAF 9.1 Online Training

Page 1

INTRODUCTION TO TOGAF 9.1


Where this fits in to TOGAF? Introduction

Introduction

Part II (The Theory)

Core Concepts

ADM

Part I

Definitions

Introduction

Release Notes

Part II,III Architecture Development Method

Preliminary Phase Phase A : Architecture Vision Phase B: Business Architecture

Data Architecture

Phase C: Information Systems Architecture Phase D: Technology Architecture

Application Architecture

Phase E: Opportunities & Solutions Phase F : Migration Planning

Introduction Phase G : Implementation Governance

Part IV Architecture Content Framework

I

Content Metamodel Architectural Artifacts

Phase H : Architecture Change Management Requirements Management

Architecture Deliverables

II,III

Introduction

Building Blocks

TOGAF 9 VII

IV V

VI

Applying Iteration to the ADM Introduction Enterprise Continuum

Part V Enterprise Continuum and Tools

Architecture Partitioning

Part III (The Practice)

Architecture Repository

ADM Guidelines and Techniques

Tools for Architecture Development Foundation Architecture : Technical Reference Model

Part VI TOGAF Reference Models

Applying the ADM at difference Enterprise Levels Security Architecture and the ADM Using TOGAF to Define & Govern SOAs Architecture Principles Stakeholder Management Architecture Patterns

Integrated Information Infrastructure Reference Model Business Scenarios Introduction Establishing an Architecture Capability

Part VII Architecture Capability Framework

Gap Analysis

Architecture Board

Migration Planning Techniques

Architecture Compliance

Interoperability Requirement

Architecture Contracts Architecture Governance

Business Transformation Readiness Assessment Risk management

Architecture Maturity Models Capability-Based Planning Architecture Skills Framework


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


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


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


Components of TOGAF 9 Introduction and Core Concepts ( Part 1)

TOGAF ADM and Content Framework

Architecture Development Method (Part 2) ADM Guidelines and Techniques (Part 3) Architecture Content Framework (Part 4)

TOGAF Enterprise Continuum & Tools

TOGAF Capability Framework

Enterprise Continuum and Tools (Part 5) TOGAF Reference Models ( Part 6)

High level introduction and key concepts, definition of terms and release notes Core of TOGAF, a step by step guide to developing enterprise architecture Collections of Guidelines and Techniques to apply with using ADM Structured Meta-model for architectural artifacts. Re-useable architecture building blocks Taxonomies and tools to categorise and store outputs Two reference models that can be applied to EA

Architecture Capability Framework (Part 7)

How to establish and operate EA with an Organisation


TOGAF Documentation Categorisation 

Core 

Mandated 

Normative parts of the TOGAF specification

Central top its use

Would not be recognisable TOGAF if not used

Recommended 

Fundamental concepts that form the essence of TOGAF

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


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”


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.


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


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


Why use TOGAF as an architecture framework 

300 Architecture forum members 

Leading vendors and service providers

Neutral and Open

Plays an important role “de-mystify” and “de-risk” the architecture development process


Core Concepts of TOGAF Architecture Capability Architecture Development Method

The organisation structure, roles, responsibilities, skills and process required to practice Enterprise Architecture

Enterprise Continuum Architecture Continuum Solution Continuum

Deliverables Artifacts

Building Blocks

Architecture Repository Architecture Meta-model Reference Library

ADM provides a tested and repeatable process for delivering architecture s

Techniques and Tools

Is a view of the architecture repository that provides methods for classifying architectures and solution artifacts as they evolve

Standards Information Base Architecture Landscape

Stores different classes of architecture outputs at different levels of abstraction.


Types of architecture domains Enterprise Architecture Business Architecture

How the business is organised to met its objectives

IT Architecture

Information Systems or Applications Architecture Data Architecture Technology Architecture

How the information System support the objective of the business Structure of the data assets

How the technology fits together


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 an organisation’s logical and 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.


Thank You

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


Turn static files into dynamic content formats.

Create a flipbook
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.