Why are we getting so hung up about how business people want to describe their requirements? In the end, we are the ones who have to analyze them and then model a solution domain that will cover those requirements. I don't think any of us believe that business will do the design for us.
If that is the case, then if 5 collaborating services can cover hundereds of business processes in a clear, loosely-coupled, event- driven interaction based way, what is missing? Is this whole discussion about traceability? Thanks, Udi Dahan - The Software Simplist .Net Development Expert & SOA Specialist Microsoft Solutions Architect MVP email: [EMAIL PROTECTED] web: http://www.UdiDahan.com --- In [email protected], Eric Newcomer <[EMAIL PROTECTED]> wrote: > > Keith, > > Well you are right, I do completely disagree. I think business people are much more interested in processing a transaction than identifying all the "things" involved in it. I also think OO analysis and design is one of the things holding up progress in SOA. All these folks trying to use UML, MDA, what have you based on OO notation are the ones forcing the round peg into the square hole IMO. > > Eric > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/service-orientated-architecture/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> 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/
