Problem Statement: Draw a use case diagram for a ticket distribution for a train system. The system as a minimum of at least three actors: A traveler who purchases different types of tickets, a service technician who maintains the ticket system but does not purchase them, and a central computer system that maintains a reference database for the different routes and tariff. I would strong suggest that you look up similar systems in existence today to give yourself some idea of how an actual softare product might be produced.

Use cases must include as a minimum for a passing grade the following use case scenarios:

BuyOneWayTicket,

BuyWeeklyCard,

BuyMonthlyCard,

UpdateTariff,

RunDiagnostics, and

ResetSystem.

Also include at least the following exception cases as a minmum:

TimeOut $($i$.$e$.,$ traveler took too long to insert the right amount of money$),$

TransactionAbort $($i$.$e$.$ Traveler selected the cancel button without completing the transaction$),$

DistributorOutOfChange$($cannot issue ticket because there is not change$),$

DistributorOutOfPaper $($cannot issue ticket because there is no paper forms$).$