My blog has moved and can now be found at

No action is needed on your part if you are already subscribed to this blog via e-mail or its syndication feed.

Wednesday, June 21, 2006
« How to prepare for Service Orientation | Main | DasBlog Url Re-Writing Question »
In Brenda's comments in the ongoing discussion, Mark Griffin follows up with…  "Is it possible to focus on the business but forget that at the end of the day you still have to deliver what you promised? This would be the loosely coupled, reusable and agile services that make up that business process."

I think it is indeed possible to get absorbed in the mapping of business processes to the detriment of everything else. I personally think that one of the core benefits of a SOA implementation is re-usability, which in turn enables agility. As such a lot of how I approach this is colored by that viewpoint. Given this, my approach to business process is not as an end to itself but as a way to identify reusable aspects of a business such that it can be factored out into services.

Approaching SOA from both the Top-Down/Business Process perspective as well as the Bottom-Up/Service Factoring perspective allows for the identification of the re-usable aspects in a business process and to realize that re-usability using the service implementation technology of your choice. In short, this helps you build the right type of services that are reusable across the Enterprise. I would add that in order to provide the standards based loose coupling in the current state of technology, I would be utilizing web services to implement the SOA.

Comments are closed.