Notes accompany this presentation. Please select Notes Page view. These materials can be reproduced only with written approval from Gartner. Such approvals must be requested via e-mail: [email protected]. Gartner is a registered trademark of Gartner, Inc. or its affiliates. Successful Business-Critical SOA: Do's and Don'ts Massimo Pezzini
22
Embed
Successful Business-Critical SOA: Do's and Don'tsdownload.microsoft.com/documents/uk/MSFT_UK_SOA_RoadmapForSuccessM...Indoor positioning Industrial processes ... Business KPIs Service
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Notes accompany this presentation. Please select Notes Page view.These materials can be reproduced only with written approval from Gartner.Such approvals must be requested via e-mail: [email protected] is a registered trademark of Gartner, Inc. or its affiliates.
Successful Business-Critical SOA:
Do's and Don'ts
Massimo Pezzini
Beware of SOA Bigotry:
“Request/Reply" SOA Is Not the IT Cure-all
Multichannel Operations
Web commerce
Internet banking
Travel reservations/ticketing
Self-Service Portals
Customers
Suppliers
Employees
Citizens (e-government)
Composite Applications
Contact center operations
Branch operations:
Banking
Post office
Single view of "something"
Real-Time B2B
Event-driven Applications
Securities trading
Telecom services activation
Real-time fraud detection
Real-time supply/demand chain
Airline operations tracking
Near-real-time data consistency
Batch-Oriented Processing
Bill/statement printing
Data warehouse loading
Database reconciliation
"Monitoring" Applications
Systems & Network Monitoring
Indoor positioning
Industrial processes
EDI-Style B2B
Suitable Applications for “Request/Reply" SOA
Applications Requiring SOA and Events
Key Issues
1. Why will organizations adopt SOA for strategic purposes?
2. What are the critical SOA adoption stages that users will typically go through?
3. What are the key technical and organizational obstacles to successful SOA, and how can enterprises overcome them?
A well executed SOA initiative will enable your
company reduce time-to market and achieve greater
business agility (…and will help you reduce IT costs as
well).
SOA Is a Mainstream Trend
0
10
20
30
40
50
60
70
80
Asia Europe North America Total
Currently using
Planning to implement withinthe next 12 months
Not currently using and noplans to use in the next 12months
Percentage of Respondents
SOA Adoption Breakdown by Geography
Source: Gartner (September 2008)
Why Service-Oriented Architecture?
Business Drivers Prevail Over IT Drivers
Call center integration
Single face to clients, suppliers, employees
Process integration
Real-time B2B
"Doing more with less"
Business/IT alignment
Data consistency/quality
Time to deployment
"Top Down" Enterprise Drivers
"Bottom Up" Business Unit Drivers
"Perennial" IT Challenges
SOA
M&A/divestitures
Multichannel sales/support
Time to market
Continuous innovation
Process flexibility
Process visibility
Skills is the Major Obstacle to SOA
Adoption
Why doesn't your organization currently use or plan to implement
SOA in the next 12 months?
60
50
48
44
40
40
23
13
6
0 10 20 30 40 50 60 70
Lack of internal SOA expertise
No perceived business value in SOA implementation
Lack of skill sets
Cost and/or resources required to implement SOA
Lack of organizational buy-in
SOA is a relatively new/ evolving concept, waiting
to see more industry/ peer-group justifications
SOA seen as too complex
Do not have the need
Don't know
Percentage of RespondentsSource: Gartner (September 2008)
Where Will Users Source Their
Business Services From?
TCO Differentiation
On-Demand Services (SaaS)
Purchased Services (Packaged Applications)
Custom Services (Built/Wrapped)
Composite Application/Mashup (Packaged/Custom)
Composite Process (Packaged/Custom)
Business Impact of Services
Stages of SOA Adoption
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
IT Goals Proof of Concept
Establish Technology
Platform
Leverage Services Sharing
Enterprise SOA Infrastructure
Business GoalsAddress
Specific Pain(That is, Customer
Portal)
Process Integration(That is, B2B)
Process Flexibility
(That is, Time to Market)
Continuous Adaptation &
Evolution
Single Application
MultipleApplications(Single BU)
MultipleApplications(Cross BUs)
Virtual Enterprise
Scope
<25 <100 <500 >500
<5 <25 <50 >50
<10,000 <100,000 <1,000,000 >1,000,000
<10 <20 <100 >100
No. of Published Services*
No. of Service Consumers*
No. of Service Calls/Day*
No. of Service Developers*
Enabling Technology
(cumulative)
Application Server, Portal,
Adapters
ESB, WSM Integr. Suite,
B2B
SOA Reg/Rep BPM Policy
Mgmt.
Enterprise SOA
backplane
* =These figures represent typical scenarios, but they may vary considerably
depending on the specific organization's requirements.
Which Stage of SOA Adoption
Are You Ready For?
Required Management
Buy-in
Required Skills
Required Organizational
Capabilities
= ImperativeO = Recommended
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
P P P P
O P P P
Head of IT Operations O P P
CIO/Business Units
O
P
CEO
O P
P
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
P P P P
O P P P
O P P
O
PO P
P
Basic Middleware P P P P
Web Services P P P P
Enterprise Service Bus P P P
Business Process Management Tools
P PDevelopment of Applications (SODA)
PO
O
O
P
SOA Operations Management
PO P
P P P P
P P P P
P P P
P P
PO
O
O
P
PO P
O P P P
Life Cycle Management O P P
Service DesignMethodology O P P
Planning Control and Quality Management P
PService Reuse Methodology
P
O
O
Domains
Cost Allocation Schema
EnterprisewideGovernance Processes
EnterprisewideSOA Backplane
P
PO
PO
PO
PO
Operation Management PO P
O P P P
O P P
O P P
P
P
P
O
O
P
PO
PO
PO
PO
PO P
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
P P P P
O P P P
O P P
O
PO P
P
Stage 1 Introduction
Stage 2 Spreading
Stage 3 Exploitation
Stage 4 Plateau
X
X
XX
P P P P
P P P P
P P P
P P
PO
O
O
P
PO P
X
X
X
X
O P P P
O P P
O P P
P
P
P
O
O
P
PO
PO
PO
PO
PO P
X
X
X
X
X
X
X
X
X
X
SOA Center of Excellence
Service-Oriented
Head of Development or Head of Integration
CTO/Head of Architecture
Why SOA Initiatives Fail:
Technology or Governance?
Introduction Spreading Exploitation Plateau
Risk of SOA Project Failures
Lack of Governance
Risk
Technology Risk
Less Risk
More Risk
Time
The Seven Golden Rules
for the Perfect First SOA Project
1. Set Goals and Collect Business-IT Requirements
2. Segregation of Duties Application Design Teams:
• Service consumers
• Service implementations
Infrastructure Design Team (the future SOA CoE)
3. Joint Design/Independent Implementations Services jointly designed by application teams
Technically validated by the infrastructure team
4. Deliver Infrastructure (SOA backplane) First Design, implementation, testing
Validation against an agreed proof-of-concept
5. Deliver Services Before Consumer Applications Plan for services to be available and tested before relevant consumers
6. Test, Test and Test Again Plan for at least 25% of development effort on integration testing
7. Log, Log and Log Again Multiple turn-on/off logs