InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

How to prepare your 2008 SOA budget?

Posted by Jean-Jacques Dubray on Sep 25, 2007

Sections
Enterprise Architecture
Topics
Governance ,
SOA
Tags
ROI

This is budget season for some of us, and many questions may come to mind as we prepare our 2008 SOA budget. Where to start? How to quickly demonstrate value? How to increase our maturity over time? Where do we source our skills?

Last week, Jeff Schneider, CEO of MomentumSI, explained why ROI cannot be achieved in the early months of a SOA program:

I've said it before and I'll say it again... SOA Transformations cost big bucks, take years to complete but in the end are worth the investment.

This has prompted some to start talking about a potential SOA backlash as Lorraine Lawson reports.

According to Nucleus Research, an IT research firm, a mere 37 percent of companies report a positive return on investment for their SOA implementations.

Jeff provides some real numbers from the field which could prove helpful for companies starting their SOA initiatives in 2008. He addresses the need to create a SOA foundation as the initial step of any SOA initiative. The foundation includes SOA Strategy & Roadmap, SOA Methodology, SOA Reference Architecture, Standards Development and SOA Governance Planning. He suggests to continue the initiative with SOA training and change management, infrastructure, build & integration, governance and  domain analysis.

On the same note, Wolfgang Keller, Partner at BusinessGlue Consulting, provided us recently with some advice to get started with SOA. He offers fours approaches:

  • Pilot project in IT department
  • Financing of the SOA through savings in the IT department
  • Powerful sponsor
  • Pilot project with real business value
  • Srikanth Inaganti and Sriram Aravamudan are stressing the need for key IT processes to be in place as they defined a comprehensive SOA Maturity model:

    One must not forget the fact that people, technology and architecture alone will not take an enterprise through SOA journey successfully, unless they are supported by key processes and activities. A maturity model for SOA should therefore encompass both the effectiveness of the architecture (product) as well as the processes required to take it from the as-is state to the to-be state.

    Sarah Hepner and Malhar Kamdar discussed the issue of acquiring SOA skills and provided some advice on balancing outsourcing, insourcing and re-skilling.

    Building on their early successes with pilot projects, many companies are pursuing enterprisewide service-oriented architecture (SOA) initiatives. These longer-term, expansive projects demand personnel with proven SOA skills. Yet the challenge of acquiring SOA skills is more than just another skirmish in the larger war for IT talent.

    Jeff notes that SOA initiatives often underestimate the need to perform domain analysis:

    It surprises [him] how many organizations forget this [last] point. Domain analysis is typically performed by enterprise architects who have a strong background in process modeling and service design. They pick a domain area (Sales, Supply Chain, etc.) and perform Process Reengineering, Process Modeling, Service Identification, Service Analysis and Composite Application Requirements Gathering.
    • This article is part of a featured topic series on SOA
    SOA in reality by matt tulum Posted
    1. Back to top

      SOA in reality

      by matt tulum

      Nice article however you seemed to miss out some key factors within the text...

      What does SOA stand for is one of them? Sh*t out of Assets?
      I for one am sure myself and my team at Tulum Hotels will be using our own 'SOA' methodology to prepare for the oncoming financial year, however your 'big company' insight has been very useful! Thanks

    Educational Content

    New-age Transactional Systems - Not Your Grandpa's OLTP

    John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

    Cool Code

    Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

    Collaboration: At the Extremities of Extreme

    Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

    Yesod Web Framework

    Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

    Transactions without Transactions

    Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

    Attila Szegedi on JVM and GC Performance Tuning at Twitter

    Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

    10 tips on how to prevent business value risk

    One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

    Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

    InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.