Overview for the Enterprise Architect - IBM · PDF fileOverview for the Enterprise Architect....

© 2005 IBM Corporation

Service Oriented Architecture

Overview for the Enterprise Architect

© 2005 IBM Corporation2

Agenda

Introduction► Relating SOA to the Enterprise Architect

SOA Reference Architecture► Providing a comprehensive model

SOA Roadmap► Relating business and IT objectives

SOA Governance► Executing for success

Summary


Service Oriented Architecture: Different things to different people

Business

RolesA set of services that a business wants to expose to customers and clients

an architectural style which requires a service provider, requestor and a service description.

a set of architectural principles and patternswhich address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composableand single implementation.

Architecture

ImplementationA programming model complete with standards, tools, methods and technologies such as web services.


SOA: Different from the Past

Broadly adopted Web services ensure well-defined interfaces. Before, proprietary standards limited interoperability

Standards

Organizational Commitment

Degree of Focus

Connections Level of Reuse

SOA unites Businessand IT (66% of projects today are driven by line of business)Before, IT alone defined the design

SOA services focus on business-level activities & interactionsBefore, focus was on narrow, technical sub-tasks

SOA services are linked dynamically and flexibly Before, service interactions were hard-coded and dependent on the application

SOA services can be extensively re-used to leverage existing IT assetsBefore, any reuse was within silo’edapplications


SOA and Enterprise Architecture: A Common Goal

Aligning BUSINESS and IT Objectives

Function (Service Definition)

Security & Compliance

Performance & Quality (KPI)

Reference Architecture

Roadmaps

Governance

Enterprise Architect

IncreaseTime to Market

Increase Revenue

Reduce Costs


SOA: The focus of the Enterprise Architect

Deliverable Description Overview

Service Oriented Architecture (SOA)

Reference Architecture

The SOA Reference Architecture defines a reference framework and corresponding IT principles for SOA implementation projects. A

pps

&

Info

Ass

ets

App

s &

In

fo A

sset

s

Business Innovation & Optimization Services

Dev

elop

men

tSe

rvic

es

Interaction Services Process Services Information Services

Partner Services Business App Services Access Services

Integrated environment for design

and creation of solution

assets

Manage and secure services,

applications &

resources

Facilitate better decision-making with real-time business information

Enable collaboration between people,

processes & information

Orchestrate and automate business

processes

Manage diverse data and content in a unified manner

Connect with trading partners

Build on a robust, scaleable, and secure services environment

Facilitate interactions with existing information and application assets

ESBFacilitates communication between servicesESBFacilitates communication between services

IT S

ervi

ceM

anag

emen

t

Infrastructure ServicesOptimize throughput, availability

and performance

Implementing Individual Web Services

Service Oriented Integration of Services

ImplementServices Repository

Implement Policy-based Service Management & Security Services Infrastructure

Implement Enterprise Data Services

Enterprise-wideServices

Define Autonomic & Utility Services Strategy

Define Resource Virtualization Strategy

Implement Dynamic Services Discovery & Orchestration

Expose Managed Information via Services

Implement Enterprise Data and Services Management

Define Portal Strategy

Define Web services Strategy

Define Extranet Strategy

Implement Business Domain-based Services Oriented Development Infrastructure

On Demand Services

Implement Autonomic and Utility Services

Implement Business Domain-based Service Management

Define Web services Implementation Guidelines

Define Web services Infrastructure and Policies

Define SOA Strategy

Implement Usage Analytics and Dynamic Workflow

Define & Implement Service-Oriented Development Environment

Extend Application Development Infrastructure for Service Exposure

Develop Services & Infrastructure Policies

Implement Business Process Orchestration

Extend Services Management to include “Enterprise Service Bus”

Define Services & Data Description Standards

Define & Implement Services Repository – Strategy & Model

Define Component Business Services Map

Define and Implement Enterprise SOA Governance

Implement SOA Reference Model

Design and Implement Services ManagementService Oriented

Architecture (SOA) Roadmap

The SOA Roadmap outlines the key set of initiatives for moving to service oriented

computing. The Roadmap is used to create a tailored transition plan for getting to the end-state Service Oriented Architecture.

Service Oriented Architecture (SOA) Governance Model

The SOA Governance Model defines governance team mission, roles and

responsibilities, compliance and vitality processes, method based checkpoints,

checkpoint–compliance criteria, technology usage templates.


Agenda

Introduction► Relating SOA to the concerns of the Enterprise Architect




Summary


The SOA Lifecycle

Gather requirementsModel & SimulateDesign

DiscoverConstruct & TestCompose

Integrate peopleIntegrate processesManage and integrate information

Manage applications & servicesManage identity & complianceMonitor business metrics

Financial transparencyBusiness/IT alignmentProcess control


SOA Reference ArchitectureSupporting the SOA Lifecycle


Dev

elop

men

tSe

rvic

es

Integrated environment

for design and creation of solution

assets


applications &

resources

Facilitates better decision-making with real-time business information

IT S

ervi

ceM

anag

emen

t

Infrastructure ServicesOptimizes throughput,

availability and performance

ESBFacilitates communication between services

App

s &

In

fo A

sset

sPartner Services Business App Services Access Services



Facilitates interactions with existing information and application assets

Interaction Services Process Services Information ServicesEnables collaboration

between people, processes & information


processes

Manages diverse data and content in a

unified manner


SOA Reference ArchitectureSupporting a new Solution Abstraction Layering

Integration (Enterprise Service Bus approach)Custom

ApplicationPackaged Application

Packaged Application

Custom Application

consumers

business processesprocess choreography

servicesatomic and composite

service components

operational systems

Service Consum

erService P

rovider

11

22

33

44

55 66

OO Application

Integration (Enterprise Service Bus approach)Custom

ApplicationPackaged Application

Packaged Application

Custom Application

consumers

business processesprocess choreography

servicesatomic and composite

service components

operational systems

Service Consum

erService P

rovider

11

22

33

44

55 66

OO Application

CompositeApplication

Composite service

Atomic service

Composite service

Atomic service

Composite service

Atomic service


A new Programming Model supporting the SOA Reference Architecture

The IBM SWG Programming Model derives its SOA technical strategy and vision from the basic concept of a service:

► “A service is merely an abstraction that encapsulates a software function.”► “Developers build services, use services and develop solutions that aggregate services.”

SWG SOA: Programming Model and Architectural Overview

Business Expertise

Technical Expertise

Extensive Overlap

UsersDefine/refine business processes

Service DevelopersCreate app building blocks – patterns, templates, and components using core technologies

Service-Oriented Development

App DevelopersTranslate bus. Processes into apps by assembling and configuring building blocks

Business Expertise

Technical Expertise

Limited Overlap

UsersDefine/refine business processes

DevelopersProgram apps using core technologies

Traditional Software Development


SOA Programming ModelDesign

► Focus on business design modelling, simplification, and role-based collaboration

► Use of declarative policy ….

User Interaction► Dynamic support for people integration into the business

design

Business Components► Composable and reusable services

Information► Built-in access to service state, disconnected service-

data exchange, information composition and transformation

Composition of Business-level Applications► Wired assembly of services to form business-level

applications, workflows, and business orchestration

Invocation► Loosely-coupled call-style and event-driven

interconnection of services with built-in support for topology transparency, mediation, and brokering featuring standards-based interoperability


Key Development Roles for SOA

Analyst

Capture business and

system requirements

Analyst

Capture business and

system requirements

Architect

Model applications

and data

Architect

Model applications

and data

Project Manager

Follow a common processTrack project statusManage requirements

Manage change and assetsManage qualityProject

Manager

Follow a common processTrack project statusManage requirements

Manage change and assetsManage quality

IntegrationDeveloper

Create composite

applications

IntegrationDeveloper

Create composite

applications

Tester

Design, create, and

execute tests

Tester

Design, create, and

execute tests

Developer

Construct, program,

and generate code

Developer

Construct, program,

and generate code


Key Standards for SOA

SOA and Web Service Standards

Sem

antic

Sta

ndar

ds Business Services: Service Offerings and Componentse.g. Book_Flight, Low_Fare_Search, Update_PNR_Data

Evolving Industry Semantics(ACORD, FIXML, OTAXML, UCCNet, ebXML)

Service Orchestration (WS-BPEL)

Service Discovery (WSIL, UDDI, RAS)

Service Invocation & Messaging (WS-I, SOAP)

Service Description (WSDL, RAS)

XML (Infoset, Namespace, Schema)

Network Protocol (HTTP, SMTP, Other)Infra

stru

ctur

e S

tand

ards

Tran

sact

ions

(WS

-Tx)

Sec

urity

(WS

-SE

C)

Man

agem

ent


The core of business performance is cross-organizational optimization and innovation

Alerts, KPIs, Metrics(role-based views and semantics)

Associate

Manager

Executive

BusinessDomains

policypolicy

processprocess

ITIL Processes

IT impacton processes

ITInfrastructure

IT Domain


Common business monitoring goals

Report on business performance measured against targets (scorecard)

►Share growth and new product revenue

Track business process flow►Status of particular insurance claim►Bottlenecks due to human tasks

Monitor business process metrics►Duration, cost, branch ratios

Business Analysis through aggregation and multidimensional reporting

►Total monthly revenue by customer

Detect and alert of anomalous situations►Gold customer order with no inventory and supplier decommitted


IT Management: 4 Principles

A repeatable approach to sense and respond to performance problems within the composite application infrastructure.

Measure Response Time

TraceTransactions

AnalyzeServices

Adjust Resources


IT Observation

Supporting InfrastructureCommon Event Infrastructure, Correlation Engine, Event Store

ModelModel

Business Observation

MonitorMonitor

Monitoring in Action: Enabled by Standards

MetadataFlow

Transformation Aggregation

Based on OASIS Common Base Event (CBE) Standards


Business Performance Management in an SOAProcess Modeling and Analysis

Invoke

Invoke

Invoke

Invoke Invoke

Business Process Workflows

Enterprise Services – Business FunctionsRouting Pub/Sub Transformation Mediation

Transport

Real-time Monitoring and Management

112

2

3

4567

8

9

1011

Distributed Resources: Modular Applications, Databases, Organizations, People


Summary: The SOA Ref Arch and its key principles

Linkage between business and IT through support of the entire SOA lifecycle

Separation of Concerns

Modularity for incremental adoption

Component based programming and solution development

Open Standards

Business and IT level monitoring and management


Dev

elop

men

tSe

rvic

es

Integrated environment for design

and creation of solution

assets


applications &

resources

Facilitates better decision-making with real-time business information

IT S

ervi

ceM

anag

emen

t

Infrastructure ServicesOptimizes throughput,

availability and performance

ESBFacilitates communication between servicesESBFacilitates communication between services

App

s &

In

fo A

sset

sA

pps

&

Info

Ass

etsPartner Services Business App

Services Access Services



Facilitates interactions with existing information and application assets

Interaction Services Process Services Information ServicesEnables collaboration

between people, processes & information


processes

Manages diverse data and content in a

unified manner

The IBM SOA Reference Architectureprovides the level of

IT flexibility required to meet the demands of

Business


Agenda





Summary


SOA Roadmap: A Plan for Adopting SOASOA Goal

Market return through transformation: quicker time to production, lower costs, competitive differentiation

Revenue and Profit

Time

Strategic Vision Market Return through Transformation

IncrementalApproximation

Two Primary Roadmap Perspectives

Strategic VisionBusiness and IT statement of direction which can be used as a guideline for decision making, organizational buy-in, standards adoption

Project PlansImplementation projects to meet immediate needs of the current business drivers


SOA Adoption Considerations

Business Drivers► Time to market

► Reduce Costs

► Increase revenue

► Reduce risk and exposureOrganizational readiness

► Executive support and sponsorship

► SkillsCurrent architecture and environments

► Build and Runtime

► Degree of heterogeneityOperational readiness

► Ability to monitor and manage current operations

► Integration of monitoring functions into production environments


Organizations can take different paths to eventual adoption of SOA depending on your business goals and IT constraints.

Entry Points Based On Business Priorities

Implementing with SOA

technology

Implementing an SOA Project

Line of Business Application

process integration

Enterprise Business and IT Transformation

Bus

ines

s V

alue

Creating services from tasks contained

in new or existing applications

Implementing business aligned services to meet a business objective for the enterprise

An architected implementation enabling integration across business functions throughout an enterprise

Broad transformation of existing business models or the deployment of new business models

1

2

3

4

Bus

ines

s V

alue


Options for Getting Started

SOA a strategic initiative for application development and integration at an Enterprise level

Component BusinessModeling

Single project implementation at IT group level. “Testing the waters”… gradual adoption approach

Entry Point “How To Get Started”

Line of business level, or across a set ofrelated projects

ClientArchitectureReadinessEvaluation

SOA Jumpstart

Example


Agenda





Summary


What do you really mean by SOA Governance …

Governance comes from the root word

“Govern”. Governance is the structure

of relationships and processes to direct

and to control the SOA components in

order to achieve the enterprise’s goals

by adding value while balancing risk

versus returnThe governance model defines:What has to be done? How is it done?Who has the authority to do it? How is it measured?

Processes

People

Technology

Services

The focus of SOA is the Services Model


SOA requires effective IT Governance“Effective IT Governance is the single most important predictor of value an

organization generates from IT.”MIT Sloan School of Mgmt.

Increasing Share Price Professional investors are willing to pay premiums of 18-26% for stock in firms with high governance

Increasing Profits “Top performing enterprises succeed where others fail by implementing effective IT governance to support their strategies. For example, firms with above-average IT governance following a specific strategy (for example, customer intimacy) had more than 20 percent higher profits than firms with poor governance following the same strategy.”

Increasing Market Value “On average, when moving from poorest to best on corporate governance, firms could expect an increase of 10 to 12 percent in market value.”

Source: MIT Sloan School of Mgmt.


SOA Governance in contextIT and Operations align with Business

BusinessOpportunity

TechnologyAvailability

Planning

Model & Assemble

Strategy

Deploy & Manage

BusinessStrategy

InformationTechnology

Strategy

ITArchitecture

Business Operating Environmentand IT Infrastructure

IT Solutions

BusinessArchitecture

Ente

rpris

e-w

ide

focu

s

Consistent Service Model

ReconcileMultiple

Viewpoints & Interests


What does IBM have to offer? Business Enabling ServicesIGS SOA Transformation Roadmap People

-CBDI Forum,April 6, 2005

Component Business Modeling (CBM)

Business EnablementServices for SOA

ImplementationServices for SOA

IBM’s Service-Oriented Architecture Services [new]

Integrated Technology Services

Application Value Optimization Services [new]

Infrastructure Service Readiness EngagementsInfrastructure Services Architecture & Design

Design Services for SOA ManagementServices for SOA

Assessment for SOAStrategy & Planning for SOAService-Oriented Modeling & Architecture (SOMA)COE & Governance

Web Services AssessmentArchitecture & Planning for Web ServicesService-Oriented Modeling & Architecture (SOMA

Service- Oriented DevelopmentService-Oriented Integration

Service MonitorService SecurityService PerformanceBusiness Requirements Verification

IBM Business Enablement Services integrate SOA into daily business life to achieve the desired agility and competitive advantage.


Agenda





Summary


SOA for the Enterprise Architect …

Understand your business goals, drivers, and context

Understand your current environment► Development, Runtime, and Management

Establish a Roadmap ► Find appropriate starting point

► Determine the development and runtime requirements– Leverage Separation of Concerns and the new Programming Model

Establish Governance► Appropriate for your company culture and environment


Now … Imagine this scenario ….JK Enterprises

Current State Desired State

SOA

Business Perspective:- Takes too long to open new accounts- Losing business to competition- Inconsistent status between Sales and

Customer Service- Multiple open-new-account forms

confusing customers and frustratingSales

- Wide range in response time duringcredit checks, etc.

IT Perspective:- Individual connections between front end

channels and back-end apps (complexity)- Large operations expenses – manual dataentry

- Redundant functions across apps- Slow response to business demands

Business Perspective:- Consistent open-new-account process- Instant approval 90% of time- Common status available to Sales,

Customer Service, and customer- Streamlined credit check and other 3rd party actions

IT Perspective:- Isolation between front-end channels and back-end systems

- Consistent data across applications- Ability to re-use application functions- Elimination of manual keying operations- Reduce time to production by 30%

On average, JK Enterprises takes 5 days to open a new account. This is 3 days longer than their competition. As a result, they are losing customers, revenue, and market share.

… How do they get to the desired state??

Overview for the Enterprise Architect - IBM · PDF fileOverview for the Enterprise Architect....

Documents

Transcript of Overview for the Enterprise Architect - IBM · PDF fileOverview for the Enterprise Architect....