Being at the moment stuck in the depths of the French countryside
where the telecoms infrastructure is somewhat fourth-world, I have not
downloaded the current edition of SD Times.  However, I would just
like to observe that an inherent virtue of SOA must surely be the
ability to extend the useful life of application code, not only by
reuse of application modules, but by providing a framework for legacy
integration.  An example: how about that Crédit Suisse project enabled
by IONA and proselitised by Gartner?

Gervas

PS No, I receive no monies from IONA or Gartner - never met them!

--- In [email protected], Todd Biske
<[EMAIL PROTECTED]> wrote:
>
> This week's SD Times had an article on Application Lifecycle  
> Management that called out some of the challenges that an SOA  
> adoption will place on the IT Organization.  It was nice to see this  
> called out, along with quotes from David Kelly, Ron Schmelzer, Dana  
> Gardner, and Carey Schwaber.  There are teams that have had enough  
> difficulty with lifecycle management when only dealing with the end  
> users of their applications.  When they begin managing services  
> derived from that original application and have to deal with other IT  
> development teams, the challenges only get bigger.
> 
> Anyone who has been dealing with SOA purely at a technology level and  
> isn't thinking about the organizational implications should give this  
> a read.  Personally, I believe this is a more important issue for the  
> overall success of an enterprise SOA adoption that the technology  
> issues are.
> 
> They haven't posted the article online at http://www.sdtimes.com/  
> yet, but you can access the PDF for the whole issue there. It begins  
> on page 29.
> 
> -tb
>









 
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/
 


Reply via email to