the organizational soa roadmap

BEA Confidential. | 1

The Organizational SOA Roadmap

Byungwook Cho K.

2006-06-14


Agenda

1. Stakeholders and Potential Conflicts of Interest

2. The Organizational SOA Roadmap

3. Four Pillars for Success

1. Budget

2. Project

3. Team

4. Buddies

4. An Ideal World

1. Structures and processes

2. SOA Specifies

5. Examples in The Real World

6. Recommendations for the SOA Protagonist


1. Stakeholder and Potential Conflicts of Interest

Before introducing SOA, we need to examine who the different stakeholders in the SOA are within an enterprise and the potential conflicts of interest that you must overcome to ensue a successful introduction of new technical standard.



Obstacles to SOA investment Intangible ROI

Frequent changes in strategy

Gap between IT and Business

Not Invented here syndrome

ROI is not tangible No way to measure SOA value

History of unfulfilled promises

CASE, EAI or workflow

Favor short-term benefit



CEO : responsible for high-level strategic decisions

Business Unit : driver functional requirement

CIO



Cross (Inter)-Enterprise Processes


2. Organizational Roadmap

The organizational SOA road map


3. Four Pillars for Success(1)

4 Main pillars for success of SOA

Budget

Project

Team

Buddies



Budget will be needed to finance one or more initial projects acting as pilot

application of SOA

Compensation for initial overheads caused by SOA

Employee have to familiarize with new standard and process

Initial overhead caused by efforts required to increase reusability



Initial Project The choice of a suitable project

Chosen project should be “visible” & less important

Has to guarantee a significant reuse potential of implemented service



SOA Team Support and establish the SOA in the enterprise

Include

Design and specification of overall architecture principles

Standard

Processes

Monitoring of actual SOA applications

Contain “evangelist”

Explain benefit of the SOA to different departments of the enterprise

Education on fundamental standards and processes making up the SOA

Support actual impelmentation of these principles



Backer To acquire budget approval and sufficient enterprise-wide awareness to get the SOA off

the ground

Backers and buddies

Top management : include the SOA in the strategy planning ,covering 3~5 year

Key business department : Key business function should support SOA

Key IT management and staff : SOA is primarily a technical issue

Backers have to sell the SOA to others

To approach potential supporters

Who are the target group and key actors?

What are the 3 main arguments for and against an SOA (per target group,key factor)

Whose support will be likely?

Who is to be convinced or overruled?



First Project

Backer

Management, Business dept, IT staff

SOA TeamVisible Business but less critical

Evangelist

has

Budget

`


4. An Ideal World(1)

To introduce SOA to enterprise Whitepapers

SOA board

Multi-project management

Standard process

Support of all actors



White papers “Why” and “How” Strategy white paper

Explain the overall goal of SOA and its perspective over the next three to five years

Business white paper

Business benefits expected from the introduction of an SOA

ROI Technology white paper

Technological issues involved in implementing the SOA How integration of SOA with the existing technological infrastructure is

envisaged.

Special platform – eg ESB

Repository structure



SOA Boards Organizational entity responsible for making a technological vision

work in every day life.

Multi-project management SOA project is independent on each other project Coordinate the development of each project team

Standard processes Which is business process – ex) ISO9000 How new application projects should proceed to make sure that the

enterprise’s SOA principles are adhered to Can based on standard process – ISO9000, 6 Sigma



Include all relevant actors Management, IT depart, business department and admin

Avoid temptation to choose “new people for a new technology”



SOA Specifics Service contracts

Most obvious starting point for standardization

Describe and specify services

Repository

All including Non-IT should perceive it as a useful tool

Special team is needed to manage repository. (SOA Team)


5. Realworld example

Failure Launch postponed, scope creep, obsolete technology

Why ?

Avoid technology Focus

Start small. [ tried to start after build all of infra structure ]

Success Story Bottom-up approach : start from small pilot project.

Balanced between business needs and technological features

Business team and Dev team allocated budget to the pilot and budget.

Special team monitored compliance with the SOA standards and resuability


6. Recommendations for the SOA Protagonist

Solid foundation – 4 Pillars for SOA

Establish processes, structures and standards

Enforce substantial change


Questions?