• Like
The Organizational Soa Roadmap
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

The Organizational Soa Roadmap

  • 2,002 views
Published

How to setup organization for successful SOA

How to setup organization for successful SOA

Published in Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,002
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
74
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. The Organizational SOA Roadmap Byungwook Cho K. 2006-06-14
  • 2. Agenda
    • Stakeholders and Potential Conflicts of Interest
    • The Organizational SOA Roadmap
    • Four Pillars for Success
      • Budget
      • Project
      • Team
      • Buddies
    • An Ideal World
      • Structures and processes
      • SOA Specifies
    • Examples in The Real World
    • Recommendations for the SOA Protagonist
  • 3. 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.
  • 4. 1. Stakeholder and Potential Conflicts of Interest
    • 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
  • 5. 1. Stakeholder and Potential Conflicts of Interest
    • CEO : responsible for high-level strategic decisions
    • Business Unit : driver functional requirement
    • CIO
  • 6. 1. Stakeholder and Potential Conflicts of Interest Cross (Inter)-Enterprise Processes
  • 7. 2. Organizational Roadmap The organizational SOA road map
  • 8. 3. Four Pillars for Success(1)
    • 4 Main pillars for success of SOA
      • Budget
      • Project
      • Team
      • Buddies
  • 9. 3. Four Pillars for Success(2)
    • 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
  • 10. 3. Four Pillars for Success(3)
    • 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
  • 11. 3. Four Pillars for Success(4)
    • 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
  • 12. 3. Four Pillars for Success(5)
    • 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?
  • 13. 3. Four Pillars for Success(5) First Project Backer Management, Business dept, IT staff SOA Team Visible Business but less critical Evangelist has Budget `
  • 14. 4. An Ideal World(1)
    • To introduce SOA to enterprise
      • Whitepapers
      • SOA board
      • Multi-project management
      • Standard process
      • Support of all actors
  • 15. 4. An Ideal World(2)
    • 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
  • 16. 4. An Ideal World(3)
    • 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
  • 17. 4. An Ideal World(4)
    • Include all relevant actors
      • Management, IT depart, business department and admin
      • Avoid temptation to choose “new people for a new technology”
  • 18. 4. An Ideal World(5)
    • 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)
  • 19. 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
  • 20. 6. Recommendations for the SOA Protagonist
    • Solid foundation – 4 Pillars for SOA
    • Establish processes, structures and standards
    • Enforce substantial change
  • 21. Questions?