Yes, it was deliberate overstatement though based on OASIS SOA RM standard. When I talk with people who see value in SOA Projects, I usually one of two cases (sometimes, both): 1) it is just an initial first pilot project 'to taste the water', and it is OK 2) Web Services are used for application integration w/o going into real SOA value of business functionality
Actually, I do not mind having SOA projects but only AFTER the overall business functionality picture and SOA environment are in place: think/see globally and move locally. - Michael ----- Original Message ---- From: Kirstan Vandersluis <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, October 16, 2008 5:31:46 PM Subject: [service-orientated-architecture] Re: van Hoof on EDA & SOA --- In service-orientated- architecture@ yahoogroups. com, Michael Poulin <[EMAIL PROTECTED] .> wrote: > ...Those you insist on mentioned simplification take SOA_service = Interface, which is totally wrong in 2008. It was OK before the end of 2006 when a service was taken as just a Web Service. Michael, I agree with your statement in the context of enterprise SOA, an "SOA Initiative" in terms Anne would use. But there is still value in "SOA projects" where Paul's more technical SOA description is completely valid. This level of SOA has more modest goals than a complete business and IT overhaul, but still brings value in developing capabilities in a service oriented manner. I know some on this list beleive strongly that project level SOA really isn't SOA, but I disagree with that, as do most people I interact with. So, to say this view is "totally wrong in 2008" is a significant overstatement. -Kirstan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
