So if there is clarity on the need to service-orient the organization, can we describe at an organizational level what the key differences are between one that is SO and one that isn't?
I would suggest that such a description take into account the geographical perspective as well - for example, the fact that there is a billing department at each location, can we say that they all belong to the same billing service? Steve, would you like to bring the value networks stuff to play here? Best regards, -- Udi Dahan From: [email protected] [mailto:[email protected]] On Behalf Of htshozawa Sent: Saturday, June 06, 2009 11:06 PM To: [email protected] Subject: [service-orientated-architecture] Re: Anne again on SOA's Mortality --- In [email protected] <mailto:service-orientated-architecture%40yahoogroups.com> , "Udi Dahan" <thesoftwaresimpl...@...> wrote: > > Hitoshi, > > > > I wasn't being prescriptive on how we service-orient the organization > (bottom-up, top-down, middle-out, whatever), that's a different discussion. > > I just wanted to see if we could get clarity on the need. > Well, I think most of us on this list don't doubt the necesssary of SO. It's just the extent (whether SOA or just SO) and how we go about it. H.Ozawa
<<image001.jpg>>
<<image002.jpg>>
