User Tools

Site Tools


project

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
project [2011/11/27 17:49] roumaniproject [2011/12/02 04:42] (current) roumani
Line 24: Line 24:
  
 ==== Use Case: A client adds an item to the shopping cart ==== ==== 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 ==== ==== 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 Companyi.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 Companyi.e. adding new clients is //not// within the scope of this project
  
 ==== Use Case: A client checks out ==== ==== Use Case: A client checks out ====
Line 36: Line 36:
  
 ==== Use Case: A client visits the URL of a P/O ==== ==== 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. 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 59: Line 59:
   * Tables ''Category'', ''Item'', and ''Client'' in the ''CSE'' database   * 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.
  
  
project.1322416150.txt.gz · Last modified: 2011/11/27 17:49 by roumani

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki