View
1.789
Download
0
Category
Preview:
DESCRIPTION
This paper looks at how to analyze the benefits a SOA offers to different stakeholders in the context of a business case, approaches to the realization of SOA, and how to setup a roadmap. The roadmap that you create also depends heavily on the type of initiative: strategic, IT driven or departmental. Apart from objective criteria like cost and benefit, time to complete the project and ability to repeat the process, perception is an important factor that determines the ability of an organization to mature and create a successful Service Oriented Architecture.
Citation preview
1 | 28
SOA Made Simple:Creating a roadmap for your SOALonneke DikmansNovember 2012 | Nuremberg
2 | 28
Agenda
● Introduction: definition of SOA● Organizing the effort● Approach● Business case● Roadmap● Maturity and stages● Conclusion
3 | 28
Introduction | Definition of SOA
Service
something useful a provider does for a consumer
Service Oriented Architecture
Reference architecture based on services
4 | 28
Agenda
● Introduction: definition of SOA● Organizing the effort● Approach● Business case● Roadmap● Maturity and stages● Conclusion
5 | 28
Organizing the effort | Overview
6 | 28
Agenda
● Introduction: definition of SOA● Organizing the effort● Approach● Business case● Roadmap● Maturity and stages● Conclusion
7 | 28
Approaches | Top Down
8 | 28
Approaches | Bottom up
9 | 28
Approaches | Meet in the Middle
10 | 28
Agenda
● Introduction: definition of SOA● Organizing the effort● Approach● Business case● Roadmap● Maturity and stages● Conclusion
11 | 28
Business case | Overview
“A business case captures the reasoning for initiating a project or task”
Aspects● Background● Problem● Goal● Future developments● Requirements● Scenarios, analysis of the scenarios● Advice● Next steps
12 | 28
Business case | Perspectives
Company as a whole – strategic● Business case is from the perspective of entire company● Based on company strategy (operational excellence, product
leadership, customer intimacy)
IT● Cut cost● Consolidation, standardization
Departmental – tactical● Scope is department
13 | 28
Business case | Strategic example insurance (1)
Competing based on product leadership
Scenario Cost Benefit Risk Change Time
0 500K -100K 3 mo+
SOA +BPM 3000K 1500K 2 yr
SOA 750K 1500K 1 yr
14 | 28
Business case | Strategic example insurance (2)
Competing based on operational excellence
Scenario Cost Benefit Risk Change Time
0 500K -100K 3 mo+
SOA +BPM 3000K 4500K 2 yr
SOA 750K 1000K 1 yr
15 | 28
Business case | IT example – the problem
16 | 28
Business case | IT example – possible solutions
Consolidate all systems Consolidate DMS
17 | 28
Business case | Departmental example - 1
18 | 28
Business case | Departmental example-2
19 | 28
Business case | Departmental example-3
20 | 28
Agenda
● Introduction: definition of SOA● Organizing the effort● Approach● Business case● Roadmap● Maturity and stages● Conclusion
21 | 28
Roadmap | Approach and work packages
Approaches● Top down● Bottom up● Meet in the middle
Work packages● Service by service● Process by process● System by System
22 | 28
Roadmap | work packages & business case (1)
Trigger Business case Unit of work Advantages Disadvantages
Strategic SOA and BPM Process ROI is assignable to a specific budget
Reuse has to be taken into account
Strategic SOA Service Reuse and flexibility is built in from the start
Risk of building services nobody uses. ROI is hard to specify
IT Consolidation System (or Service)
ROI is assignable to a specific budget
Service design is driven by an application, not by good service design
23 | 28
Roadmap | work packages & business case (2)
Trigger Business case Unit of work Advantages Disadvantages
Departmental SOA and BPM Process ROI is assignable to a specific budget
Local process improvements
Departmental SOA Feature ROI is assignable to a specific budget
Local calculation, the benefits and cost for the whole company can differ significantly
24 | 28
Agenda
● Introduction: definition of SOA● Organizing the effort● Approach● Business case● Roadmap● Maturity and stages● Conclusion
25 | 28
Maturity models | An alternative
Maturity models● The open group● Vendors (Oracle, Microsoft)● CMMI● …
Alternative model● Stage 0: Starting● Stage 1: Newly weds● Stage 2: Live● Stage 3: Growing up● Stage 4: Experience● Stage 5: Maintenance
26 | 28
Agenda
● Introduction: definition of SOA● Organizing the effort● Approach● Business case● Roadmap● Maturity and stages● Conclusion
27 | 28
Conclusion | Six golden rules
● Communicate the SOA drivers clearly;● Train people involved;● Communicate your successes; ● Reward people that adapt to the new way;● Learn from the mistakes;● Look for a sponsor.
28 | 28
29 | 28
SOA Made Simple:Creating a roadmap for your SOALonneke DikmansNovember 2012 | Nuremberg
Recommended