Skip to main content

Bus service use cases with elaboration

Short answer

Actors: Passenger, Driver, Traffic Planner, Price Analyst, Driver Manager, Phone Staff, Payment System, Email System, Transport Dept. Key use cases: Buy Ticket (includes Make Payment, Send E-ticket), Cancel Ticket (includes Calculate Refund), View Schedule, Check Ticket Barcode, Manage Lines, Design Schedule, Adjust Prices, Allocate Drivers/Buses, Schedule Vehicle Tests.

A new bus service, Gana Rajya Express (GRE) is starting soon, which has the business plan and operation as detailed below. GRE sells tickets only through the web service, not in bus stations or in buses. Tickets must be paid by credit card or online bank payment. Tickets are not bookable. Ticket can be sold to the particular line, but not with particular seating location. The ticket can be cancelled, but GRE returns only a portion of the ticket price. Cancellation can be handled via Internet or via phone services. The closer to departure, the lower part of the price shall be refunded. In addition to ticket cancellation, it is possible to inquire about bus schedule information via phone service. Tickets are electronic tickets delivered via e-mail. The driver checks the right to travel by reading the barcode on the ticket using mobile reading terminal. GRE hires workers for different tasks. Traffic planner establishes and closes down lines. He also shifts in demand, and designs schedules. Price analyst adjusts prices depending on demand and competitors. Driver manager is the head of drivers and allocates drivers and buses, and schedules services and Transportation Department tests for the vehicles. GRE pays hourly rate for drivers and telephone service staff. Other staff will be paid by monthly salary basis. Non-core activities (accounting, payroll, vehicle maintenance, computer maintenance, etc.) will be outsourced. Prepare and draw Use Cases with elaboration for the above scenario.

Actors: Passenger (customer), Driver, Traffic Planner, Price Analyst, Driver Manager, Telephone Service Staff, Payment System (credit card/online bank), Email System, and the Transportation Department (secondary actor for vehicle tests). Non-core activities (accounting, payroll, maintenance) are outsourced, so they lie outside the system boundary.

Use case diagram

                 +----------------------------+
                 |    GRE Ticketing System    |
 [Passenger] ----|-( Buy Ticket )---+         |
 [Passenger] ----|-( Cancel Ticket )+--include|
 [Passenger] ----|-( View Schedule ) v        |
                 |          ( Make Payment )--|-- [Payment Sys]
 [Phone Staff] --|-( Cancel Ticket )          |
 [Phone Staff] --|-( Inquire Schedule )       |
 [Driver] -------|-( Check Ticket Barcode )   |
 [Traffic Plnr] -|-( Manage Lines )           |
 [Traffic Plnr] -|-( Design Schedule )        |
 [Price Analyst] |-( Adjust Prices )          |
 [Driver Mgr] ---|-( Allocate Drivers/Buses ) |
 [Driver Mgr] ---|-( Schedule Vehicle Test )--|-- [Transport Dept]
                 +----------------------------+

Actors and their use cases:

ActorUse cases
PassengerBuy Ticket, Cancel Ticket (web), View Schedule
Phone service staffCancel Ticket (phone), Inquire Schedule
DriverCheck Right to Travel (scan barcode)
Traffic PlannerEstablish Line, Close Line, Design Schedule, Adjust Lines to Demand Shifts
Price AnalystAdjust Price
Driver ManagerAllocate Drivers and Buses, Schedule Services, Schedule Vehicle Tests
Transportation Dept (secondary)Receives the vehicle test schedule and tests the vehicles
Payment systemAuthorise Payment
Email systemDeliver E-ticket

Relationships: Buy Ticket includes Make Payment and Send E-ticket; Cancel Ticket includes Calculate Refund; Cancel by Phone and Cancel on Web are specialisations of Cancel Ticket.

Elaboration of main use cases (fully dressed, short form)

UC1: Buy Ticket

  • Primary actor: Passenger. Secondary: Payment System, Email System.
  • Preconditions: the line and date exist.
  • Main flow: 1) Passenger selects line, date and number of tickets. 2) System shows the price. 3) Passenger enters credit card/online bank details. 4) System authorises the payment. 5) System generates an e-ticket with a barcode and e-mails it.
  • Alternate: payment rejected -> ask for another payment method.
  • Note: tickets cannot be booked without paying, and no seat location is given (the ticket is for the line only).
  • Postcondition: ticket stored as valid; sale recorded.

UC2: Cancel Ticket

  • Actors: Passenger (web) or phone staff on behalf of the passenger.
  • Main flow: 1) Enter the ticket id. 2) System checks that the ticket is valid. 3) System computes the refund from the time left to departure (less time = smaller refund). 4) Passenger confirms. 5) Ticket is marked cancelled and the refund is paid.
  • Alternate: ticket already used or bus already departed -> reject.

UC3: Check Right to Travel

  • Actor: Driver. Flow: scan the barcode with the mobile terminal; the system validates the ticket and line, shows valid/invalid, and marks the ticket used.

UC4: Adjust Prices - Price Analyst reviews demand and competitors' prices and updates the fare table. UC5: Design Schedule - Traffic Planner sets lines and timings and adjusts them to shifts in demand. UC6: Allocate Drivers and Buses - Driver Manager assigns drivers and buses to scheduled services and schedules vehicle tests with the Transportation Department; a bus must have passed its test before it is allocated.

✓ Answer checked by Claude Opus 5.5 (high effort)

Related questions

All Object Oriented Analysis and Design chapter 2 questions →