Introduction to Enterprise Architecture and TOGAF 9.1

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…

6

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 Organization’s Systems

Download file

Download file

Download file

Screen scrape

Screen scrape

Browser

HTTP/XML

Transaction file

Transaction file

Transaction file

Transaction file

Message queue

Message queue

Message queue

FTP

Sockets

E-mail

Message

XML/HTTP

Gateway RPC

CICS gateway

APPC

SMTP

CICS gateway

ORB

Applications From Mergers and Acquisitions

Legacy Applications

Purchased Packages

Applications in Trading Partners

E-Marketplaces

End-User Development

Autonomous Divisions

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

Process People

Capability

Why Business and EA? (© www.EnterpriseArchitects.com)

From Strategy to Execution

Architecture Domains

TOGAF

24

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?

Zachman

25

DATA Implementation

DATA What

FUNCTION How

NETWORK Where

e.g. Data Definition

Entity = Field Rel. = Address

e.g., Physical Data Model

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

e.g., Logical Data Model

Entity = Data Entity Rel. = Data Relationship

e.g., Semantic Model

Entity = Business Entity Rel. = Business Relationship

List of Things - Important to the Business

Entity = Class of Business Thing

List of Processes - the Business Performs

Function = Class of Business Process

e.g., Application Architecture

Process.= Application Function I/O = User Views

e.g., System Design

Process= Computer Function I/O =Data Elements/Sets

e.g. Program

Process= Language Statement I/O = Control Block

FUNCTION Implementation

e.g., Business Process Model

Process = Business Process I/O = Business Resources

List of Locations - in which the Business Operates

Node = Hardware/System Software Link = Line Specifications e.g. Network Architecture

Node = Addresses Link = Protocols

NETWORK Implementation

MOTIVATION Why

PEOPLE Who

e.g. Rule Specification

End = Sub-condition Means = Step

End = Condition Means = Action

List of Business Goals and Strategies

List of Events - Significant to the Business

Time = Execute Cycle = Component Cycle

e.g. Timing Definition

Time = Interrupt Cycle = Machine Cycle

SCHEDULE Implementation

List of Organizations - Important to the Business

People = User Work = Screen/Device Format

e.g. Security Architecture

People = Identity Work = Job

ORGANIZATION Implementation

STRATEGY Implementation

SCOPE Planner

SYSTEM MODEL

Designer

TECHNOLOGY CONSTRAINED

MODEL Builder

DETAILED REPRESEN-

TATIONS Subcontractor

ENTERPRISE MODEL

Owner

contextual

conceptual

logical

physical

out-of-context

FUNCTIONING

ENTERPRISE

perspectives abstractions

Node = Major Business Location e.g., Logistics Network

Node = Business Location Link = Business Linkage e.g., Distributed System Architecture

Node = IS Function Link = Line Characteristics

e.g., Technical Architecture e.g., Rule Design

e.g., Business Rule Model

End = Structural Assertion Means =Action Assertion

End = Business Objective Means = Business Strategy

Ends/Means=Major Business Goal/Critical Success Factor Time = Major Business Event

e.g., Processing Structure

Time = System Event Cycle = Processing Cycle

e.g., Control Structure

e.g., Master Schedule

Time = Business Event Cycle = Business Cycle

People = Class of People and Major Organizations

e.g., Work Flow Model

People = Organization Unit Work = Work Product e.g., Human Interface Architecture

People = Role Work = Deliverable

e.g., Presentation Architecture

e.g., Business Plan

EABOK

GERAM

IDEAS Group

RM-ODP a

ARCON

TRAK

MEGAF

Praxeme GOD

SABSA

Zachman

SAP EA

ATOS CLEAR

DoDAF

MoDAF

NAF

AGATE

NORA

NIST EA

DNDAF

IAF

TOGAF

PEAF

LEAD

Pick a Framework

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

TOGAF first published

TOGAF 8.1.1 The Interoperable Enterprise Business Scenario first published

1990 91 92 93 94 95 96 97 98 99 2000 01 02 03 04 05 06 07 08 09 2010 11 12 13 14 2015

TOGAF 7 – Technical Edition

TOGAF 9 – Enterprise Edition

TOGAF® 9.1 – Technical Corrigendum

TOGAF 8 – Enterprise Edition First TOGAF Certification Program Launched

Customer members demand architecture standards

Customer members select TAFIM as preferred starting point

DoD Information System Agency (DISA) donate TAFIM as base

YEAR

‘93 ‘94 ‘96

‘01 ‘02 ‘03 ‘06

‘09 ‘11

TOGAF Features

What’s in It?

Core Concepts: ADM

Requirements Management — Examination of the process of managing architecture requirements.

Requirements Management

Phase A — Definition of scope, identification of stakeholders, creation of architecture vision. A.

Architecture Vision

Phase B — Development of business architecture.

B. Business

Architecture

Phase C — Development of data and application architectures. C.

Information Systems

Architectures

Phase E — Implementation planning, identification of delivery vehicle.

E. Opportunities and Solutions

Phase G — Oversight of the implementation.

G. Implementation

Governance

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

Architecture Change

Management

Phase D — Development of technology architecture.

D. Technology Architecture

Phase F — Definition of implementation and migration plan.

F. Migration Planning

Preliminary Phase — Preparation and initiation activities, definition of enterprise-specific architecture framework, architecture principles.

Preliminary

Requirements Management

A. Architecture

Vision

B. Business

Architecture

C. Information

Systems Architectures

E. Opportunities and Solutions

G. Implementation

Governance

H. Architecture

Change Management

D. Technology Architecture

F. Migration Planning

Preliminary

Source: TOGAF® Version 9.1, The Open Group, 2011

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?

Business Planning

Enterprise Architecture

Solution Development

Operations Management

Portfolio/Project Management

Architectural Governance

Project Management Governance

Delivers

Capability Planning

Business Direction

Architectural Direction Resources

Runs the Enterprise

Structured Direction

Delivers

Source: TOGAF® Version 9.1, The Open Group, 2011

How Does EA Relate to Mayor IT Frameworks?

COBIT PMP PRINCE2

TOGAF

ITIL

Governance structure

Project management

Project briefs

IT strategy, configuration items

Architecture principles and models

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?

58

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

59

The TOGAF® Momentum

TOGAF® 9.1 Portfolio

60

Foundation

Classroom

Foundation Exam

Know TOGAF

60 Minutes

Ensures knowledge and understanding of the terminology, basic concepts and the core

principles of TOGAF.

Practitioner

Focuses on implementation, enabling professionals to analyze and apply knowledge of

TOGAF.

Classroom

Certified Exam

Apply TOGAF

90 Minutes

Know TOGAF

IASA and TOGAF®

61

¿Preguntas? y Respuestas…

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