2 Use Case DescriptionSix 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.ActorsCustomers (Movie-goers)Ticket SalespersonManagers
3 What use cases do we have? CustomersPurchase tickets (online)Print ticketsCheck 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 case Primary Actors: Actors participating in the use case Secondary Actors: Actors that may participate Preconditions:What needs to exist for this use case to startMain Flow:Steps done in this use casePostconditions: What should happen by the end of this use case to verify that it is done in a correct wayAlternative Flows: A possible alternative flow for the use case (e.g. an error happens)
5 Use Case DescriptionName: Purchase Tickets Description: Purchase tickets for a movie Primary Actors: Customer, Sales Secondary Actors: Manager Preconditions:Movie not sold outMovie playingMain Flow:Customer logs into online systemCustomer selects movie theatreCustomer selects movieCustomer pays for moviePostconditions: Customer has a ticket ID and/or printed out ticket for a movieAlternative Flows: In-Theatre PurchaseSalesperson or Manager verifies available tickets for a playing movieThey get payment and processes it
6 Use Case DescriptionName: Check Movie Status Description: Returns the movie status (tickets left, playing times, etc..) Primary Actors: Customer, Sales Secondary Actors: Manager Preconditions:Movie existsMain Flow:Check the number of available seats, movie times, etc..Return to userPostconditions: NoneAlternative Flows: None
7 Use Case DescriptionName: Reserve Seating Description: Reserves seat(s) for a given movie Primary Actors: Customers, Sales Secondary Actors: Managers Preconditions:Movie existsTicket purchased for movieMain Flow:Check to see if the seat is availableReserve itPrint 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 seatsReturn an error message to user
8 ExerciseDevelop a use case diagram for a shipping company such as UPS or FedEx.RequirementsCustomers must be able to arrange for a pickup of a package to be deliveredCustomers must be able to check the status of a package, assuming there is a tracking number for itCustomers must be able to refuse a packageDelivery people must be able to determine the next address to deliver a package to, and get directions for itDelivery 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.