SOA Meets Business Processes

After my previous post around what SOA is, I thought that I would spend a little outlining my thinking on the major areas associated with SOA. I must admit that I am borrowing from a number of sources here SE Radio, The favourite, wikipedia, My links, (at this point I have decided the list is much to long to put anything other than..) etc.

In the current climate the corporate agenda is mostly filled with 'how do I cut costs?' opposed to how do I implement my new IT strategy which means that in order to even get close enough to get stakeholders excited, money needs to come into the equation (which is MV = PT by the way).

So you have targeted identified a collection of stakeholder(s) and sold them (Yes believe it or not we in the EA space are actually sales people, we just might not get the commission!) the concept that the road map needs to incorporate Services.. Probably the concept you have sold is that for the next project we can work in a quicker, leaner, more agile way, 'if' we consume from a number of services and these might as well be Business services as they are what the stakeholders will see. Great, from the aspect of a business user I can see a business process that consumes from a number of autonomous business services drop them all together and I get a working solution, easy! I also think that this idea needs to be sold communicated using business language opposed to technobabble. Gone are the days when I can talk about components, classes, methods, parametric polymorphism and the like (not that I ever did). What you need to do is articulate realisation of business challenges using Information Technology in an intuitive way.

All the time considering where in the quarterly life cycle you are, because this new initiative will be expected to return results by the next quarter!

Now the clock it ticking.. So what next.