95-843 Group Project Paper Template The paper will be between six and eight pages in length. It will be combined into one large document and it will be made available on the course web site. So, it is very important that you site all sources in endnotes. Do not use footnotes. The title of the final document is: SOA 2011: A Snapshot of Some Existing Tools Your paper should not make a case for the product or platform. You are not in the role of an advocate. Instead, the paper should be written from an objective (scientific) point of view. Think of yourself as one who is trying to evaluate the product and not as a person trying to convince others to adopt it. Each team should begin by developing an outline. Each team member will be responsible for sections of the outline. The outline that you develop will be included as the contents of the final course document. Each team member is a contributor to the final document. Your name must be included on the section(s) that you contributed to. A single section may have more than one author. The paper must be written well. Points will be deducted for poor English. Be sure to use "an SOA" and "an ESB". Please do not use "a SOA" or "a ESB". The following outline may be used as a guide. Feel free to depart from it if you need to. 0. Executive summary (one paragraph) 1. History of product including latest release 2. Market position and trajectory 3. Developer tool support (IDE) 4. Management tool support (BAM) 5. Business case studies a. Successful use cases 6. Technical Architecture a. Rules engine availability b. ESB availability and ESB capabilities c. Registries d. Web Service support e. Legacy system migration e. Other 7. Standards support a. WS-* b. WSI Profiles and Interoperability testing c. BPMN and BPEL d. Transactions (atomic and compensating) e. Security (WSS) f. SCA g. SDO h. SAML i. XACML j. Industry specific standard support k. Metadata management (WS-MetadataExchange, WS-Policy, UDDI) l. Other 8. Product support for experimentation and demonstration This part of the document will contain a description of a successful experimentation or a clear description of the obstacles encountered. Screenshots are encouraged and will be used in the appendix. The screenshots should not be taken into account in the six to eight page boundary. If screenshots are included, be sure to label them and make references to them within the text. From within your text, you may say "see XYZ in appendix "A". For the document body, only use plain text. We will combine the final document into a Word document before placing it on the course schedule. For screenshots, submit a singe separate Word document. We are assuming that you have no problem with your name being placed on a final document on the course schedule. Please see me if that is of concern. The teams and team members for July-August 2011 are: Microsoft Team ============== Sadit Zia Khan Zin-Hao Lin Hassam Raja IBM Team ======== Vivel Ramesh Devang Shah Oracle Team =========== Jaime Rodriguez Lara Saad Farooq