David Forslund wrote: > I'm not sure the details of what was done, but what you describe seems > pretty superficial and the SOA view doesn't have to be instead of the > CBA View. One might have a "Patient" component that serves the patient > portion of some of the higher level services such as Hospitality, > Pathology, etc. Otherwise one may find many redundancies in the > particular SOA view you have described.
I would be tempted to use a proxied service called "Patient" to wrap access to the other lower level services so that you get what you need to make the system be functional with all of the right views. This is where the rubber hits the road. If your programming interfaces don't mesh up with the use case scenarios, then the programming tasks will be more complicated, take longer, and potentially will create more fragile interfaces because of compromised access later down the road. Gregg Wonderly ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/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/
