Differences

This shows you the differences between two versions of the page.

--- project [2011/11/15 16:08] – roumani
+++ project [2011/12/02 04:42] (current) – roumani
@@ Line 24: / Line 24: @@
 ==== Use Case: A client adds an item to the shopping cart ====
-The Cart servlet must react by displaying the content of the shopping cart. The display should be tabular with one item per row. The table columns display the number, name, and unit price of each item in a read-only fashion. In addition, there should be a writable column for the desired quantity and a read-only one for the extended price (defined as the quantity times the unit price). The display should also indicate a total, PST and GST (based on Ontario), a shipping cost ($5 that is waived for orders of $100 or more before taxes), and a grand total. The page has three buttons: Update (to refresh the calculated fields after editing a quantity), Continue Shopping, and Checkout. Notice that if the entered quantity of an item is zero then it should be removed from the cart. You need to also handle the case of negative or non-numeric quantities.
+The Cart servlet must react by displaying the content of the shopping cart. The display should be tabular with one item per row. The table columns display the number, name, and unit price of each item in a read-only fashion. In addition, there should be a writable column for the desired quantity and a read-only one for the extended price (defined as the quantity times the unit price). The display should also indicate a total, a shipping cost ($5 that is waived for orders of $100 or more before taxes), HST (13% of total, including shipping if any), and a grand total. The page has three buttons: Update (to refresh the calculated fields after editing a quantity), Continue Shopping, and Checkout. Notice that if the entered quantity of an item is zero then it should be removed from the cart. You need to also handle the case of negative or non-numeric quantities.
 ==== Use Case: A client logs in ====
-Upon checkout or at anytime, a login form (normally transmitted over https) is served prompting for the client name, shipping address, and payment details. We are not going to switch to https in this project. Instead, we will continue to use http and we will assume that all clients have already established accounts with the Company, i.e. each client has a profile that contains the shipping address and payment preferences. Hence, the login form prompts only for the client's account number and password.
+Upon checkout or at anytime, a login form (normally transmitted over https) is served prompting for the client's account number and password. We are not going to switch to https in this project; instead, we will continue to use http. We assume that all clients have already established accounts with the Company; i.e. adding new clients is //not// within the scope of this project.
 ==== Use Case: A client checks out ====
@@ Line 36: / Line 36: @@
 ==== Use Case: A client visits the URL of a P/O ====
-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 12345, is: po12345_03.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 screen.
@@ Line 45: / Line 45: @@
   * Management wants to be able to determine the average time it takes a client to add an item to the cart and the average time between a fresh visit and checkout (in the same session). Provide a mechanism by which these two averages can be viewed in real time.
   * And on an ad-hoc basis, Management may decide to advertise a certain item whenever a related item is added to the cart. As a proof of concept, activate this by cross selling 2002H712 whenever 1409S413 is added to the cart. Keep in mind that this functionality should not be part of the webapp since Management may withdraw it at any time (w/o recompiling).
   * Add a search facility to enable clients to look for items.
@@ Line 61: / Line 59: @@
   * Tables ''Category'', ''Item'', and ''Client'' in the ''CSE'' database
-  * [[http://www.cse.yorku.ca/~roumani/course/4413/res/PO.xsd|The purchase order's schema]]
+  * [[http://www.cse.yorku.ca/~roumani/course/4413/res/PO.xsd|The purchase order's schema]]. Here is a [[http://www.cse.yorku.ca/~roumani/course/4413/res/PO.xml| sample]] that adheres to the schema.
@@ Line 99: / Line 97: @@
   - Front Material: A cover page (course number and name, date, project name, team); an optional dedication page; the TOC
-  - Design: Describe your system's architecture and data flow briefly (diagrams are ideal here). Also, several design issues and decisions must have popped up during the analysis and design phases, e.g. MVC, namespaces, file formats, algorithms, representations, etc. Describe in this sections the key issues and decisions that were made and why they were made the way they did.
+  - Design: Describe your system's architecture and data flow briefly (diagrams are ideal here). Also, several design issues and decisions must have popped up during the analysis and design phases, e.g. MVC, namespaces, file formats, algorithms, representations, connecting B2B with B2C, etc. Describe in this sections the key issues and decisions that were made and why they were made the way they did.
   - Implementation: This is similar to the previous part but pertains to implementation issues and decisions. This section should also include Testing and Status. The former discusses how the project was tested and the latter lists each and every limitation or shortcoming of the finished webapp with respect to requirement.
   - The Team: Provide the cse# 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.
-   - Output Samples: Select any XML P/O and include a listing of how it appears on disk and a screenshot of how it appears in the browser. Include also a completed procurement report showing the chosen wholesaler and price per item.
+   - Output Samples: These samples are for the B2B part. Select any XML P/O and include a listing of how it appears on disk and a screenshot of how it appears in the browser. Include also one completed procurement report showing: the items to procure, the consolidated quantity per item, the chosen wholesaler and price per item, and the confirmation codes obtained from the wholesalers web services.
    - The Source Code:  Provide listing of all programs (including jspx, tags, xsl, web.xml, etc.). Partition this section into subsections, provide a title for each, and add an entry (with a page number) for each such subsection in the TOC. Make sure the code is properly formatted. Some editors do not format properly because they use spaces instead of tabs and/or use proportional fonts. Do not delay this step to the last minute; resolve it early on.