Arcihtechtural questions for a Web Services / SOA / SOAP project

I have a few architechtural questions to consider for my prject. Out of 8 questions required to be answered only 1 is technical (create a simple WSDL file). This project is complete when questions 2-8 have been answered. Some of these questions may be subjective. Please do not include in your answer anything that you are not sure and which may be incorrect. Please refer to the attached Hospital Scenario use case. 2) Neither of the specialists are available. Describe what contingency I would have built into my architectural design to work around this problem and which of the WS-* technologies you would use. 3) Assume that the hospital is using WS-Coordination when requesting blood work from the outside lab. Which of the two protocols of WS-Coordination would the hospital use in this case and why? 4) Construct a WSDL (preferably using Cape Clear) that the Hospital would use when requesting blood work from the outside lab. 5) It is critical that my message requesting a specialist from Big City Hospital be received. What Web Services technology would I use when making the request to assure that my message was received and explain how that protocol works? 6) Assume the blood lab is using BPEL. Since there is a significant delay between the time the lab receives the request and it has the results, what BPEL constructs would it use to satisfy this constraint and describe the steps that I would put in the BPEL script, e.g. The blood lab, BPEL receives the request then ...? 7) The blood lab receives many requests from different hospitals and doctors offices. How would it keep them segregated over the time it is processing the blood test so that it sends the correct result to the right party? 8) A request is sent to the blood lab by the technician preparing the blood sample, but the results should be sent to doctor handling the case. How is the correct routing handled by the SOAP request and reply? ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform N/A