This Text file is old! In a 🏛️Museum, an unsorted archive of (user-)pages. (Saved from Geocities in Oct-2009. The archival story: oocities.org)
--------------------------------------- (To 🚫report any bad content: archivehelp @ gmail.com)

Use case name: BecomeAMember

Participating Actor: Customer

entry condition	
1. The customer clicks on "Create new account" button to start a new
membership.

event flow 	
2. The system displays a page containing the benifits of membership and
the store policy. In             
   order to continue the new membership process the customer must agree
to follow the store policy.

3. Customer clicks on "Agree" button to agree to the policy.

4. The system displays the "request informaton" page asking for the
customers user information.
		
5. The customer fills in the form with a name, address, telephone
number, email address. The 	
   customer then chooses a user-name and password. At the end of the
form the customer enters a credit card number and       expiration
date. Once the form is completed, the customer submits the form.
		
6. The system checks the database to see if the entered user-name and
password are already in  	
   use. If they are, then the system tells the customer that the
selected user-name and password are already taken and to    choose
another.
		
7. The system displays a confirmation page with all information
provided. If the information is   
   correct the customer will click on the "finish" button. If not the
customer may click on the "edit" button to go back to    step 5 to
correct any mistakes.
		
8. The system creates a new account in the store database and enters in
the customer 
   information acquired from the submitted form. 
		   	
9. The system sends a confirmation email to the customer.
		
Special Requirements
   A "cancel" button must be avialable at each step in order to allow
the user to cancel the create new membership process.