Home Random Page


CATEGORIES:

BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism






Use-Cases for Part 1

Ticketing

Khafizova Aru CSSE-125R

Use-Cases for Part 1

 

(a) New client account registration:

 

 
 

 

 


Basic Scenario:

 

  1. Client selects “Register as New Client”.
  2. Client fills in identity and contact information.
  3. Client selects “Register”.
  4. System proposes account name and requests password.
  5. Client enters password.
  6. System creates account in the database.
  7. System displays work screen to Client.

(b) Client login:

 

 
 

 

 


Basic Scenario:

 

  1. Client enters account name and login.
  2. Client selects “Log in”.
  3. System checks account name and password in database.
  4. System registers logged-in state in the database.
  5. System displays work screen to Client.

Client logout:

 

 
 

 

 


Basic Scenario:

 

  1. Client selects “Log out”.
  2. System registers logged-out state in the database.

(c) Client creation of an event:

 

 
 

 

 


Basic Scenario:

 

  1. Client selects “Create New Event”.
  2. Client fills in name, type, description, date(s), available seats and prices.
  3. Client selects “Create”.
  4. System creates event in the database.
  5. System displays work screen to Client.

(d) Buyer search of upcoming events:

 

 
 

 

 


Basic Scenario:

 

  1. Buyer selects “Search Events”.
  2. Buyer fills in name, type, and/or description keyword(s).
  3. Buyer selects “Search”.
  4. System searches events in the database.
  5. System displays search results to Buyer.

(e) Buyer viewing of remaining seats:

 

 
 

 

 


Basic Scenario:

 

  1. Buyer selects event from search results.
  2. Buyer fills in desired date.
  3. Buyer selects “View”.
  4. System fetches available seats for the event on the given date from the database.
  5. System displays available seats to the Buyer.

(f) Buyer purchase of seats:

 

 
 

 

 


Basic Scenario:

 

  1. Buyer selects one or more seats for an event on a given date.
  2. Buyer selects “Buy”.
  3. Buyer fills in credit card information, e-mail address, billing address, and shipping address.
  4. Buyer selects “Confirm”.
  5. System ensures that the selected seats are still available; if not, it refreshes the view of available seats for the Buyer.
  6. System registers the purchase of the seats (i.e., no longer available) in the database.
  7. System sends e-mail confirmation to the event’s Client and to the Buyer.

(g) Weekly reports sent to the client by email reflecting the history of seat purchases for each of the client’s upcoming events:

 

 
 

 

 


Basic Scenario:

 

  1. Every Monday, for each active Client, the system determines the history of seat purchases for each event that was still upcoming as of the previous Monday.
  2. The system sends an e-mail to each Client with the history report.


Date: 2015-12-24; view: 803


<== previous page | next page ==>
Submission date 11/30/2015 | Testing/Deployment Grid for Part 2
doclecture.net - lectures - 2014-2024 year. Copyright infringement or personal data (0.007 sec.)