On Mar 12, 2006, at 5:39 PM, Eric Newcomer wrote: > Are you > implying that an SOA doesn't have to be realized in > software?
I think Todd is argueing that service orientation can be beneficially applied at the business level by managing/modeling interactions between intra-organisational parties in terms of services they provide to each other (resulting in a contracts and responsibilities view). The software services that are implemented to meet the contractural responsibilities then merely *derive* from that higher level approach. I find that idea rather attractive, as it enables a view on business 'subsystems' interaction that groups communication into various functionally related 'channels' (into various services).[1] Hope that replays Todd's point close enough. [1] An example of that might be defining a 'helpdesk' as the single point of communication between IT service provider and customer in the IT Service management world. Such a helpdesk will of course usually be a piece of software but it might well be just a single support phone number (no SOA technology there). Jan ________________________________________________________________________ _______________ Jan Algermissen, Consultant & Programmer http://jalgermissen.com Tugboat Consulting, 'Applying Web technology to enterprise IT' http://www.tugboat.de Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
