Soa maturity business model

Embed Size (px)

Text of Soa maturity business model

  • 1. SRL Methodology Library
    SOA
    Yuval Birenboum
    CTO
    Integration, SOA, BPM
    & Architecture

2. Lack of Agility ?
Duplication ? | Data | Web service| Process |
Low Reliability ?
High Maintenance Costs?
Support Confusion - Difficult Root Cause Determination?
IT ChallengesWhere are Your Pain Points?
Cant Estimate Change Impact?
Poor Project Estimating with Multiple Systems Involved?
Falling Data Quality?
Project Failure?
3. Integration Has Become EasyQuick and Easy
What did we get ?
connection between systems
exposure of transactions
spread of data
& functions
SOA technologies enable
Asset
Visibility
Process
Modeling
Impact Analysis
4. How did we get here ?The Big Box Application
Stand alone.
Modules can import/export data but not dependent
Represented a complete end-to-end process by itself.
Asset Management
Inventory
Asset State
Parts
Accounting
Ordering
Supplies
Stock Control
5. How did we get here ?But Data Became Real Time
Not acceptable to slowly import/export data between applications
Asset Management
Inventory
Asset State
Parts
Accounting
Ordering
Supplies
Stock Control
6. How did we get here ?The Distributed Application
The Big Box
Application
Asset Process
Inventory
Asset State
Parts
Decomposition

  • Increased complexity

7. Reliability issues 8. Performance concerns 9. New security requirements
Accounting
Ordering
Supplies
Stock Control
distributed
interconnected
systems and
processes.
10. Business : ITChallenges
Quickly Changing Business Demands
Do Even More
with Less
Move Beyond Overhead
Start Innovating
11. Business Demands vs. IT Constraints
Stop running
Start innovating
New & changing
business demands
Business need
Business Value
Do more
with less
Business subduction
Business growth
Run the business
0
Increased complexity
ITConstraints
Reliability
Issues
Performance
Concerns
12. SOA eliminates the gap
Stop running
Start innovating
ITEmpowers the Business
New & changing
business demands
Business need
Business Value
Do more
with less
Business subduction
Business growth
Run the business
0
Increased complexity
ITConstraints
Reliability
Issues
Assets & Process Composition = Service Enabling
Assets & Process Visibility = (re)use
BAM, Governance & KPIs = Control
Performance
Concerns
13. SOA ApproachesDoes it matter ?
Top-Down
Middle-Out
Bottom-Up
Start with business model finish with implementation
For each project expose, compose & consume
Start with implementation finish with business model
Whichever you choose, same steps different order.
None of these approaches say Start tool shopping
14. A Full SOA Model
In a perfect world, SOA would follow
three top-down stages
Collaborative Modeling
Collaborative Operation
Service Oriented System Construction
15. The three milestones of SOACollaborative modeling
Multi-views business modelling
describes enterprise business
Collaborative modeling
Business model is transformed
into platform independent
business collaborative model
Platform-independent business
collaborative model is mapped into platform-specific business collaborative model
16. The three milestones of SOA
Service modules in enterprise information systems are identified, encapsulated and published into business process services
Service oriented information system construction
Build service component libraries
Theservices in these libraries can be composed and choreographed
17. The three milestones of SOA
Monitor enterprise business processes
Collaborative operation and evaluation
Analyze and Optimize the performance of the enterprises business processes by a workflow management system
Enforce business policies and regulations
18. Challenges
We have a large number of existing systems in older technology & architecture models to maintain & integrate.
We have project and business deadlines that dont care about architecture, they just want to get it done NOW.
SOA tech has entered bottom-up, without methodologies & process, because just connecting things using SOAP is fast and easy.
19. SOA Technology without Methodology leads to
Hard to identify process impact, impact of changes and system modifications and upgrades
Major Support (Root Cause Identification) Challenges
Connection Spaghetti
Process Duplication
Reduced Reliability
Data Duplication
20. SOA Methodology Provides Measurable Value
Adjustments for Each Stage
Every Stage of the Software Development Lifecycle
Requires Tweaks to Achieve SOA Success & Get Real Value
Measurements for Each Stage
Keeps the SOA ROI Positive
Provides Describable Business Value
21. - Improved Data Quality
- Reduced Business Process Duplication
SOA CycleAre You Getting Value Here?
Identify & Model
the gold copy of data
business process
the right source system or application
SOA
Analysis
22. - Increased Reuse / Faster Development
- Increased Agility
SOA CycleAre You Getting Value Here?
Creating
reuse incentives
services with highest likelihood of reuse
Penalties
having to adjust services in the next year
Handling of budget
issues regarding first-creator cost, maintenance & support costs, etc
SOA
Analysis
IT Management
for SOA
23. - Improved Service & IT Process Control
- Improved Project Estimating
- Clear Understanding of Change Impact
SOA CycleAre You Getting Value Here?
Governance
Managed Service SDLC Workflow
Policy Creation, Automated Application & Enforcement
Impact Analysis
Determine, Track, Report
SOA
Analysis
Create SOA Controls
IT Management
for SOA
24. - Avoid SOA Reliability Decreases
- Allow for coordinated parallel development, faster results!
SOA CycleAre You Getting Value Here?
Consumer Provider
contracts
Roles and responsibility
Layered QA testing
Integration into the Software
SDLC
SOA
Analysis
Create SOA Controls
Coordinated SOA Development
IT Management
for SOA
25. - Determine system, project, and business process impact.
- Avoid surprise system overloads , whether from service misuse or unexpected business growth.
SOA CycleAre You Getting Value Here?
Distributed Monitoring
SOA
Analysis
Create SOA Controls
Pinpoint problems
SLA control
Excess use
Coordinated SOA Development
IT Management
for SOA
26. - Improve what needs improving and provides maximum return!
SOA CycleAre You Getting Value Here?
Distributed Monitoring
measure
the right points +
Get detailed feedback
=
Show the ROI, detailed/granular
and enterprise.
SOA
Analysis
Create SOA Controls
Ongoing KPIs
for SOA
Coordinated SOA Development
IT Management
for SOA
27. What will we get from a Methodology ?
Moving up in the
SOA maturity model
28. Create services definitions
SOA maturity model
Integrate SOA into project development
methodology
Quantify costs, time, and business
benefits of pilot projects
Key goals
Business Value
New
Functionality
1
0
Initial
Services
29. Specify technology standards for SOA
SOA maturity model
Integrate SOA into organization-wide
development process
Use incremental integration
Key goals
Business Value
IT Cost
Reduction &
Control
New
Functionality
2
1
0
Initial
Services
Architected
Services
30. Specify policies for use of SOA in creation
or modification of business processes
SOA maturity model
Take advantage of event-oriented and
mediation functionality of SOA technologies,
especially with regards to enhancing/
extending business processes
Key goals
Business Value
change business
processes quickly
and effectively
IT Cost
Reduction &
Control
New
Functionality
2
1
3
0
Initial
Services
Architected
Services
Business
Service
31. SOA maturity model
Specify policies for use of SOA in
collaboration with business and trading
partners
Implement cross-enterprise security
Key goals
Collaboration
with business &
trading partners
Business Value
Change business
processes quickly
& effectively
IT Cost
Reduction &
Control
New
Functionality
2
1
3
4
0
Initial
Services
Architected
Services
Business
Service
Collaborative
Services
32. Collect and analyze business process oriented
real-time performance metrics
SOA maturity model
Implement ongoing business process
evaluation and re-engineering
Business
transformation