Service Oriented Analysis
The roundtable on Service Oriented Analysis was interesting, because it showed the culture clash between 'Pure Object' guys and 'Service Oriented ' guys.
Martin Fowler was the OO guy and someone from the Indigo team whose name I cannot remember was the SOA guy.
Fowler was quite ironic about SOA. He said he did not know what does SOA mean, and that the meaning changes every 5 minutes. In his mind, SOA was about application integration. If you have a property layered application, then SOA is just adding another layer to adapt the inner interface to the Service Oriented one. Inside the application domain, you will keep using thightly coupled OO classes.
The Indigo guy view was that you can use SOA even inside applications (i.e., inside different teams), and it was a much more pervasive thing. The audience seemed to like Fowler's point of view, as there were applauses after some of his comments.
At least there is agreement that you should not expose your inner object model in the service layer, something that was not at all clear in the times of DCOM and CORBA.
I'm closer to the SOA guys than to the OO guys.