labs
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| labs [2009/02/03 20:09] – roumani | labs [2010/11/09 14:32] (current) – roumani | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== Project |
| **An eCommerce Site Backed by Web Services** | **An eCommerce Site Backed by Web Services** | ||
| - | * Due Date: < | ||
| - | * Team Size: min=2, max=3 students | ||
| - | * Technological Platform to be used: JEE | ||
| Line 21: | Line 18: | ||
| ==== Use Case: A client makes a fresh visit ==== | ==== Use Case: A client makes a fresh visit ==== | ||
| - | The relevant URL is '' | + | The relevant URL is '' |
| Line 39: | Line 36: | ||
| Upon confirmation of a P/O, the system stores its content in an XML file based on the PO.xsd schema. The name of the P/O file is derived from the account number of the client and the P/O number (a per-client serial number that starts at 1). For example, the the 3rd P/O of account number 1234B555, is: po1234B55503.xml. Since this is an XML file, it needs to be transformed to XHTML before the client can see it. Note that this use case does not involve authentication. | Upon confirmation of a P/O, the system stores its content in an XML file based on the PO.xsd schema. The name of the P/O file is derived from the account number of the client and the P/O number (a per-client serial number that starts at 1). For example, the the 3rd P/O of account number 1234B555, is: po1234B55503.xml. Since this is an XML file, it needs to be transformed to XHTML before the client can see it. Note that this use case does not involve authentication. | ||
| - | In addition to the above use cases, it is recommended that your site supports the following uses: the ability to view the shopping cart from the catalog screen (i.e. without having to add an item); the ability to checkout from the catalog | + | In addition to the above use cases, it is recommended that your site supports the following uses: the ability to view the shopping cart from the catalog screen (i.e. without having to add an item); the ability to checkout from the catalog screen. |
| Line 51: | Line 48: | ||
| ===== Specifications ===== | ===== Specifications ===== | ||
| - | * [[http:// | + | * [[http:// |
| - | * [[http:// | + | * [[http:// |
| - | * [[http:// | + | * [[http:// |
| - | * [[http:// | + | * [[http:// |
| **// | **// | ||
| Line 64: | Line 61: | ||
| The following files describe the web services from which the company procures its products: | The following files describe the web services from which the company procures its products: | ||
| - | * [[http:// | + | * [[http:// |
| - | * [[http:// | + | * [[http:// |
| - | * [[http:// | + | * [[http:// |
| Line 77: | Line 74: | ||
| - | ===== Deliverables ===== | + | |
| - | + | ||
| - | You need to deliver three things by the due date of this project: | + | |
| - | + | ||
| - | * Hand in a paper report | + | |
| - | This can be done after class or to the Department Office | + | |
| - | + | ||
| - | * Submit the report and source files | + | |
| - | The report file (in pdf, doc, or html formats) and the Java files. These can be submitted using: '' | + | |
| - | + | ||
| - | * Upload a WAR webapp | + | |
| - | Create a war file of your webapp and upload it to the project' | + | |
| - | + | ||
| - | The report is meant to describe your execution of the project to someone who is familiar with the project, e.g. a fellow student who is also executing the same project and writing a similar report. Hence, the report should focus on your own experience and efforts, i.e. what you actually did, rather than on general description. It is expected to be very brief, to the point, and made up of //at most// ten pages of typed text and diagrams (excluding printouts and source listing). The report should include the following sections: | + | |
| - | + | ||
| - | - Design: Describe your system' | + | |
| - | - Implementation: | + | |
| - | - The Team: Provide the cs# and name of each member of the team and indicate the contact person in case there are questions. It is essential that you explain how the work was divided and how was communication and consistency maintained. Include here the main lessons that were learned from this project. | + | |
| - | - Printouts: Include printouts of the XML order file as it appears on disk and on the client' | + | |
| - | - The Source Code: Provide listing of all programs (including jspx, tags, xsl, web.xml, etc.). Partition this section into subsections, | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | ===== Evaluation ===== | + | |
| - | + | ||
| - | The project will be evaluated based primarily (80%) on meeting the specs (these include system functionality and report contents) and on its internal quality (design, style, code, etc.). The remaining (20%) is based on how your project compares with those of other teams. | + | |
labs.1233691767.txt.gz · Last modified: 2009/02/03 20:09 by roumani