Use Case Description

1
Use Case Description

• Week 1 Lab2

2
Use Case Description

• Six months from now, the Grand Cineplex Odeon II
  is opening in downtown Calgary. It will sport a
  multilevel parking garage free for movie-goers,
  enhanced online ticket purchasing, more combos of
  soda and popcorn, and make a larger dent in your
  monthly bank statement. They have started the
  planning for their system infrastructure and part
  of this involves developing a use case diagram
  for their system.
• Actors
• Customers (Movie-goers)
• Ticket Salesperson
• Managers

3
What use cases do we have?

• Customers
• Purchase tickets (online)
• Print tickets
• Check status of movie (sold out, x full, etc..)
• Check available seating (which seats, or if it's
  a "free-for-all")
• Reserve seating (if possible)
• Get parking entrance receipt (by authenticating
  their ticket, they can enter the parking garage
  15 minutes before, and park till 15 minutes after
  their movie)
• Pay for parking (if they went in earlier or
  stayed too late)

4
Use Case Description

• Name The name of the user case
• Description A brief description of the use
  casePrimary Actors Actors participating in the
  use caseSecondary Actors Actors that may
  participatePreconditions
• What needs to exist for this use case to start
• Main Flow
• Steps done in this use case
• PostconditionsWhat should happen by the end of
  this use case to verify that it is done in a
  correct way
• Alternative FlowsA possible alternative flow
  for the use case (e.g. an error happens)

5
Use Case Description

• Name Purchase TicketsDescription Purchase
  tickets for a moviePrimary Actors Customer,
  SalesSecondary Actors ManagerPreconditions
• Movie not sold out
• Movie playing
• Main Flow
• Customer logs into online system
• Customer selects movie theatre
• Customer selects movie
• Customer pays for movie
• Postconditions Customer has a ticket ID and/or
  printed out ticket for a movie
• Alternative FlowsIn-Theatre Purchase
• Salesperson or Manager verifies available tickets
  for a playing movie
• They get payment and processes it

6
Use Case Description

• Name Check Movie StatusDescription Returns the
  movie status (tickets left, playing times,
  etc..)Primary Actors Customer, SalesSecondary
  Actors ManagerPreconditions
• Movie exists
• Main Flow
• Check the number of available seats, movie times,
  etc..
• Return to user
• Postconditions None
• Alternative Flows None

7
Use Case Description

• Name Reserve Seating Description Reserves
  seat(s) for a given moviePrimary Actors
  Customers, SalesSecondary Actors
  ManagersPreconditions
• Movie exists
• Ticket purchased for movie
• Main Flow
• Check to see if the seat is available
• Reserve it
• Print a new ticket if this is done in-theatre,
  otherwise update the e-ticket number.
• Postconditions
• Chosen seat is no longer available.
• Alternative Flows
• Movie does NOT allow reserved seats
• Return an error message to user

8
Exercise

• Develop a use case diagram for a shipping company
  such as UPS or FedEx.
• Requirements
• Customers must be able to arrange for a pickup of
  a package to be delivered
• Customers must be able to check the status of a
  package, assuming there is a tracking number for
  it
• Customers must be able to refuse a package
• Delivery people must be able to determine the
  next address to deliver a package to, and get
  directions for it
• Delivery people must be able to confirm a package
  has been delivered, and store the signature of
  the signer.
• Front staff must be able to accept new packages
  to be shipped, as well as charge customers.
• Auditors must be able to look at past parcel
  sending history for a particular location or
  customer.

9
(No Transcript)
10
(No Transcript)