togaf reference models

21
TOGAF – A Summary Reference Models

Upload: paul-sullivan

Post on 24-Jan-2015

9.133 views

Category:

Technology


9 download

DESCRIPTION

Summary of TO

TRANSCRIPT

Page 1: TOGAF Reference Models

TOGAF – A SummaryReference Models

Page 2: TOGAF Reference Models

Where Reference Models fits into TOGAF?

TOGAF 9

Introduction

Architecture Development

Method

Architecture Content Framework

Enterprise Continuum and Tools

TOGAF Reference Models

Architecture Capability Framework

Part I

Part II,III

ADM

ADM Guidelines and Techniques

Introduction

Preliminary Phase

Phase A : Architecture Vision

Phase C: Information Systems Architecture

Phase B: Business Architecture

Phase D: Technology Architecture

Phase E: Opportunities & Solutions

Phase F : Migration Planning

Data Architecture

Application Architecture

Phase G : Implementation Governance

Phase H : Architecture Change Management

Requirements Management

Introduction

Introduction

Core Concepts

Definitions

Release Notes

Introduction

Applying Iteration to the ADM

Applying the ADM at difference Enterprise Levels

Security Architecture and the ADM

Using TOGAF to Define & Govern SOAs

Architecture Principles

Stakeholder Management

Architecture Patterns

Business Scenarios

Gap Analysis

Migration Planning Techniques

Interoperability Requirement

Business Transformation Readiness Assessment

Risk management

Capability-Based Planning

Introduction

Content Metamodel

Architectural Artifacts

Architecture Deliverables

Building Blocks

Introduction

Enterprise Continuum

Architecture Partitioning

Architecture Repository

Tools for Architecture Development

Foundation Architecture : Technical Reference Model

Integrated Information Infrastructure Reference Model

Establishing an Architecture Capability

Architecture Board

Architecture Compliance

Architecture Contracts

Architecture Governance

Architecture Maturity Models

Architecture Skills Framework

Part IV

Part V

Part VI

Part VII

III,III

IV

VVI

VII Part III(The Practice)

Part II(The Theory)

Page 3: TOGAF Reference Models

There are two reference models

• TRM– Technical Reference

Model

• III-RM– Integrated

Information Infrastructure

Page 4: TOGAF Reference Models

What is the TRM- Technical Reference Model?

• The TOGAF’s TRM is a reference model and a foundational architecture

• A reference model has a taxonomy that’s describes components and the conceptual structure of the model and a graphic which provides a visual representation of the taxonomy as to aid understanding

• A foundation architecture is an architecture of generic services and functions that provides a foundation on which more specific architectures can be built

Page 5: TOGAF Reference Models

Uses of TRM

• Objective of TRM is to enable structured definition of the standardized application platform and its associated interfaces.

• Provides a starting point or reference for organisation to develop their own reference models by extending or adapting the TRM

• Provides a consistent taxonomy to aid a means of communication between stakeholders

• Can be used as a taxonomy to develop a standards information base within an organisation.

Page 6: TOGAF Reference Models

Overview of TRM

• Application Portability– How applications call or use

the services available in the platform.

– Done through the application platform interface

• Interoperability– How the application

platforms can communicate with each other

– Done through the communication infrastructure interface

Diversity should be minimised between the application platform and the communications infrastructure

Page 7: TOGAF Reference Models

TRM in detailApplication SoftwareContains two categories of software , business applications and infrastructure applications. The standards for the application platform will be strongly influenced by this application software.

Infrastructure ApplicationsProvide General purpose business functionality, uneconomic to customise but instead develop extensions, Interoperability and user interface are key attributes

Business ApplicationsSpecific to a particular enterprise or vertical industry, model elements of an enterprise domain of activity or business process

Application Platform InterfaceA complete interface between Application Software and the Application Platform. Needs to consist of the programming interface, protocols and data structures. Platforms provides and API that the application must comply with. An Application could call different APIs in order to conform with different platforms

Application PlatformA conceptual platform that contains all the platform services required to exist in order for the application software to work. e.g. A union of all operating systems services, security services, user interface services etc.

Communications Infrastructure InterfaceEffectively becoming a standard of IP based communications that the application platform uses to talk to the communications infrastructure.

Communications InfrastructureBasic mechanism of the transfer of data. Hardware and software elements that allow for the networking and physical links ( switches, routers) used by a system to interact with the network

QualitiesAttributes that are applicable across all the components. Qualities need to defined in detail when developing the target architecture e.g. Security, Locale, performance

Page 8: TOGAF Reference Models

What is III-RM ?

• The TRM focuses on the Application Platform space, III-RM main focus is the Applications space particularly the “Common Systems Architecture”

• Like the TRM it is a reference model with a taxonomy and a graphic however it is a subset of the scope of TRM but expands on certain parts

• Helps provide a solution to the common problem called the Boundaryless information flow

• Foundation Architecture that can be adapted be organisations as architecture building blocks

Page 9: TOGAF Reference Models

What is the Boundaryless Information Flow?

• Getting the right information to the right people in the right time in a secure, reliable manner, in order to support the operations that are core to the extended enterprise

• The problem is that departments are siloed with their own processes, their own systems, their own data.

• The trends in business now requires faster and better integration between these silos in to be responsive to changing markets, which requires access to systems and data across these silos.

• Cross functional teams help but how do they get access to the information to help them solve a business problem or to exploit a business opportunity

Page 10: TOGAF Reference Models

Boundaryless Information Flow – the problem it solves

• Imagine a simple organisation with multiple departments, each with systems and data

Internal Space Procure Space

Sell Space

datadatadatadatadata

SystemsSystemsSystemsSystemsSystems

Customer Support

Manufacturing Assembling ProcurementFinance and Legal

Page 11: TOGAF Reference Models

Issues with implementing a cross functional group

• How does it understand the big picture?

Internal Space Procure Space

Sell Space

datadatadatadatadata

SystemsSystemsSystemsSystemsSystems

Customer Support

Manufacturing Assembling ProcurementFinance and Legal

Cross functional Group

• Cannot be trained on all the systems!• All the systems are propriety and have different means of access• Time spent co-ordinating with teams, slows down group

Page 12: TOGAF Reference Models

Overview of III-RM

• Subset of TRM– No focussed on

O/S, Network or communications

• Expands the Applications and API areas

Focus of III-RM

Page 13: TOGAF Reference Models

Overview of III-RM

Infrastructure applications

Page 14: TOGAF Reference Models

Information Provider Applications (IPA)

• Solves: All the systems are propriety and have different means of access– Liberate Data by providing a open interface to a system via its

propriety interface, make it the data more accessible.– These applications tend to work on a request, response architecture

where an open interface is called, which in turn calls a propriety interface at run-time, a response is returned which is converted into the open interface response.

– Abstracts the caller function from the system’s propriety interface calls. Also if the propriety system is replaced the IPA will need to change but the caller function may not.

Page 15: TOGAF Reference Models

Liberating the data using IPA

• Introducing information provider applications(IPA)

Internal Space Procure Space

Sell Space

datadatadatadatadata

SystemsSystemsSystemsSystemsSystems

Customer Support

Manufacturing Assembling ProcurementFinance and Legal

Cross functional Group

IPA IPA IPA IPAIPA

Open interfaces

Propriety interfaces

However still too many interfaces

Page 16: TOGAF Reference Models

Brokerage Applications

• If the number of IPA interfaces is too many and the information requirements are broad it is likely that many interfaces may be called to satisfy one type of information request.

• Brokerage Applications serve up a single request that has many information sources. It does this by breaking up a request into multiple dispatches and collates all the responses

• Brokerage Applications can also be used to allow external partners access to information

Page 17: TOGAF Reference Models

Orchestrating the data using BA

• Introducing brokerage applications(BA)

Internal SpaceProcure SpaceSell Space

datadatadatadatadata

SystemsSystemsSystemsSystemsSystems

Customer Support

Manufacturing Assembling ProcurementFinance and Legal

Cross functional Group

IPA IPA IPA IPAIPA

Open interfaces

Propriety interfaces

Where is the user interface, as Brokerage applications does not have one?

BA BABA

Open interfaces

External Partner

Page 18: TOGAF Reference Models

Information Consumer Applications (ICA)

• Provides the information to the end user in the format that they need it, in a secure manner

• Communicates with the BA or IPA via open interfaces, in some cases via a firewall.

• An example of a ICA is an UI components of an Enterprise Portal

Page 19: TOGAF Reference Models

Presenting the data using ICA• Introducing Information Consumer Applications

Internal SpaceProcure SpaceSell Space

datadatadatadatadata

SystemsSystemsSystemsSystemsSystems

Customer Support

Manufacturing Assembling ProcurementFinance and Legal

Cross functional Group

IPA IPA IPA IPAIPA

Open interfaces

Propriety interfaces

BA BABA

Open interfaces

External Partner

ICA ICA ICAfirewall

How do we develop these interfaces? How to be management these applications?

Page 20: TOGAF Reference Models

Infrastructure Applications

• There are two infrastructure applications:-– Development Tools

• Provides all the necessary modelling, design and construction capabilities to develop and deploy applications that require access to the integrated information infrastructure in a manner that is consistent with the environment

– Management utilities• Tune and manage the run-time environment in order to

meet the demands of the ever changing business environment

Page 21: TOGAF Reference Models

Application Platform• There are a number of platform services required to make the III-RM work

– Software Engineering Services • Programming Languages, Libraries etc

– Security Services• Single Sign on, firewalls etc

– Location and Directory Services• Naming, Discovery, registering

– Data Exchange Services• Application-to-Application messaging

– UI Services• Browser

– Data Management Services• Search, file, query

– Workflow and event services