Introduction to Enterprise

Architecture and TOGAF 9.1

Introduction to Entreprise Architecture

And Enterprise Architecture with TOGAF 9.1

Who am I?

ndice

The Need for

Enterprise Architecture.
Architecture Has Always Been
Around Us

In fact, thousands of years of history suggests that the

only known strategy for addressing complexity and
change is architecture.

Example Zero
Architecture

Or, In Terms of Your Organizations Systems

Purchased Packages

Legacy
Applications
E-Marketplaces

HTTP/XML
Autonomous Divisions
Message
queue

Download
file

FTP
Screen
scrape

Screen
scrape
Download
file

CICS gateway
Transaction
file
Gateway

Transaction
file
Sockets

RPC

ORB

E-mail
Applications in Trading
Partners

Message
queue

Transaction
file

SMTP
Transaction
file
Message
queue

CICS gateway

XML/HTTP
Browser
End-User Development
Message

Applications From Mergers and Acquisitions

Download
file

APPC

Outsourced and ASP Applications

The Car Analogy

www.EnterpriseArchitects.com

Enterprise. Architecture

An Architecture is the fundamental

organization of something, embodied in:
its components,
their relationships to each other and
the environment,
and the principles governing its design
and evolution

Enterprise Architecture

Why Enterprise Architecture?

The Benefits

The Why in a Design

In a Nutshell

Enterprise Architecture = Strategy + Business + Technology

EA = S + B + T

(Scott A. Bernard. EA3)

In a Nutshell
Enteprise Architecture means better
business, pure and simple

Why Business and EA?

( www.EnterpriseArchitects.com)

Why Business and EA?

What is a Capability?

( www.EnterpriseArchitects.com)

Tecnology
Capability
Process
People

Why Business and EA?

( www.EnterpriseArchitects.com)

From Strategy to Execution

Architecture Domains

TOGAF
How do we manage EA?

How do we map all necessary

information?

How do we build on industry-practice

models?

How do we apply the ADM?

How can we maximize recycling of

existing architectures?

How do we design our EA?

24

Zachman
abstractions
perspectives

DATA

FUNCTION

NETWORK

PEOPLE

What

How

Where

Who

MOTIVATION
Why

List of Things Important to the Business

List of Processes the Business Performs

List of Locations in which the Business Operates

List of Organizations Important to the Business

List of Events Significant to the Business

List of Business Goals

and Strategies

Entity = Class of
Business Thing

Function = Class of
Business Process

Node = Major Business

Location

People = Class of People and

Major Organizations

Time = Major Business Event

Ends/Means=Major Business
Goal/Critical Success Factor

e.g., Semantic Model

e.g., Business Process Model

e.g., Logistics Network

e.g., Work Flow Model

e.g., Master Schedule

e.g., Business Plan

Entity = Business Entity

Rel. = Business Relationship

Process = Business Process

I/O = Business Resources

Node = Business Location

Link = Business Linkage

People = Organization Unit

Work = Work Product

Time = Business Event

Cycle = Business Cycle

End = Business Objective

Means = Business Strategy

e.g., Logical Data Model

e.g., Application Architecture

e.g., Distributed System

Architecture

e.g., Human Interface

Architecture

e.g., Processing Structure

e.g., Business Rule Model

Entity = Data Entity

Rel. = Data Relationship

Process.= Application Function

I/O = User Views

Node = IS Function
Link = Line Characteristics

People = Role
Work = Deliverable

Time = System Event

Cycle = Processing Cycle

End = Structural Assertion

Means =Action Assertion

e.g., Physical Data Model

e.g., System Design

e.g., Technical Architecture

e.g., Presentation Architecture

e.g., Control Structure

e.g., Rule Design

Entity = Tables/Segments/etc.
Rel. = Key/Pointer/etc.

Process= Computer Function

I/O =Data Elements/Sets

Node = Hardware/System
Software
Link = Line Specifications

People = User
Work = Screen/Device Format

Time = Execute
Cycle = Component Cycle

End = Condition
Means = Action

e.g. Data Definition

e.g. Program

e.g. Network Architecture

e.g. Security Architecture

e.g. Timing Definition

e.g. Rule Specification

Entity = Field
Rel. = Address

Process= Language Statement

I/O = Control Block

Node = Addresses
Link = Protocols

People = Identity
Work = Job

Time = Interrupt
Cycle = Machine Cycle

End = Sub-condition
Means = Step

SCOPE
Planner

contextual

ENTERPRISE
MODEL
Owner
conceptual

SYSTEM
MODEL
Designer
logical

TECHNOLOGY
CONSTRAINED
MODEL
Builder
physical

DETAILED
REPRESENTATIONS
Subcontractor
out-of-context

FUNCTIONIN
G
ENTERPRISE

DATA

FUNCTION

NETWORK

ORGANIZATION

SCHEDULE

STRATEGY

Implementation

Implementation

Implementation

Implementation

Implementation

Implementation
25

Pick a Framework
PEAF
IAF
NORA
DNDAF
AGATE
EABOK

ARCON
Zachman
NIST EA

NAF

TOGAF

GERAM
TRAK

SAP EA
MEGAF

IDEAS
Group

MoDAF

SABSA

DoDAF
Praxeme

GOD

ATOS
CLEAR

RM-ODP a

LEAD

And, the
Winner Is

TOGAF: A Cook Book

What is TOGAF?

Everyone speaks the same language

The most prominent and useful EA standard
Combine industry best practices and with your
organizations
Avoid being locked into proprietary methods
Saves time and money
Proven, tested, and effective
Utilize resources more effectively
Demonstrates ROI
Reliable
Benchmark

TOGAF Evolution
Customer members demand architecture standards

Customer members select TAFIM as preferred

starting point
DoD Information System Agency (DISA) donate
TAFIM as base
93

94

TOGAF 9 Enterprise Edition

TOGAF 7 Technical
Edition

96
01

02

03

TOGAF 9.1 Technical

Corrigendum

06

TOGAF first
published

09

11

TOGAF 8.1.1

The Interoperable Enterprise

Business Scenario first published

TOGAF 8 Enterprise Edition First

TOGAF Certification Program Launched

1990 91

92

93

94

95

96

97

98

99 2000 01

02

03

YEAR

04

05

06

07

08

09 2010 11

12

13

14 2015

TOGAF Features

Whats in It?

Core Concepts: ADM

Preliminary

Phase H Management of
architecture change, establishment of
procedures for managing change.

H.
Architecture
Change
Management

A.
Architecture
Vision

Requirements Management Examination

of the process of managing architecture
requirements.

Phase F Definition of
implementation and migration plan.

Source: TOGAF Version 9.1, The Open Group, 2011

Phase A Definition of scope,

identification of stakeholders,
creation of architecture vision.

B.
Business
Architecture

Phase G Oversight of the

implementation.
G.
Implementation
Governance

Preliminary Phase Preparation and initiation activities,

definition of enterprise-specific architecture framework,
architecture principles.

Requirements
Management

C.
Information
Systems
Architectures

D.
Technology
Architecture

F.
Migration
Planning
E.
Opportunities
and Solutions

Phase B Development of
business architecture.

Phase C Development of data

and application architectures.

Phase D Development
of technology architecture.

Phase E Implementation
planning, identification of delivery
vehicle.

TOGAF ADM

34

ADM Guidelines and Techniques

Guidelines for Adapting the ADM Process
Ways to apply iteration to the ADM,
Applying the ADM at different levels of the
enterprise,
Security considerations for the different phases
and
Supporting SOA

Techniques for Architecture Development

Architecture Principles,
Stakeholder Management,
Architecture Patterns,
Business Scenarios,
Gap Analysis,
Migration Planning Techniques
Interoperability Requirements,
Business Transformation Readiness
Assessment,
Risk Management,
Capability-Based Planning

Architecture Content Framework

Architecture Content Framework

TRM and III-RM

Technical Reference Model

Integrated Information Infrastructure Reference Model

TOGAF Enterprise Continuum

TOGAF Enterprise Continuum

TOGAF Enterprise Repository

Architecture Capability Framework

How Does EA Relate to Mayor IT Frameworks?

How Does EA Relate to Mayor IT Frameworks?

Capability
Planning

Business
Planning

Business Direction

Resources

Architectural
Direction

Runs the
Enterprise

Operations
Management

Enterprise
Architecture

Solution
Development

Structured
Direction

Delivers

Portfolio/Projec
t Management

Delivers

Source: TOGAF Version 9.1, The Open Group, 2011

Architectural
Governance

Project Management
Governance

How Does EA Relate to Mayor IT Frameworks?

PMP

Project
management

COBIT
Governance
structure

TOGAF
Architecture
principles and
models

PRINCE2

Project briefs

IT strategy,
configuration
items

ITIL

Process Chain and Frameworks

( www.bizzdesign.com)

TOGAF and eTOM

TOGAF and BIAN

EA and ITIL

EA and PRINCE2

EA and COBIT

IASA y The Open Group

TOGAF in Spain. Examples

TOGAF in The World.

TOGAF Skills Are Demanded. (Jobs)

EA and The University.

EA and The University.

Who Needs Training?

Enterprise Architect
Solution Architect
ERP/SAP Architect
Data Architect
Technical Architect
Governance Engineer
EA/ Governance Consultant
Business Analyst
Business information Manager
Project & Program Manager

58

The TOGAF Momentum

59

TOGAF 9.1 Portfolio

Ensures knowledge and understanding of the
terminology, basic concepts and the core
principles of TOGAF.

Focuses on implementation, enabling

professionals to analyze and apply knowledge of
TOGAF.

Practitioner
Foundation

Classroom
Know
TOGAF

Classroom

Apply
TOGAF

Know
TOGAF

Foundation Exam

60 Minutes

Certified
Exam

90 Minutes
60

IASA and TOGAF

61

Preguntas? y Respuestas

http://www.iasaglobal.org/iasa/Spain_Chapter.asp