Differences

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

--- project [2011/12/02 04:37] – roumani
+++ project [2011/12/02 04:42] (current) – roumani
@@ Line 29: / Line 29: @@
 ==== 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.