> Dave Linthicum notes that it may well be that SOA's have large > upfront costs that taper off over time. The idea is that ROI comes > later, and that the risk capital is spent upfront when the first > components for a service are developed. > > In short, delayed gratification.
Yeah. That'll work. ;^/ I think a better answer is over in the thread on waterfall vs. iterative. The best way to build an SOA is probably a little at a time, as little as possible, focusing on immediate business value but protecting against long-term calcification. -P ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> 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/
