Monday, September 24, 2012

Airline Ticket Reservation-Use Case Diagram

Use Case Diagram for Airline Ticket Reservation System is shown below. The various participants of the same are detailed below:

Actors: Traveller, Travel Agent, Airline Counter Incharge

The corresponding usecases  for these actors are:

  • Traveller: Book Ticket Online, Cancel Booking Online, Book via Agent, Cancel Ticket via Agent, Book At Counter, Cancel Ticket At Counter, Online Inquiry, Fill Details, Cancel Ticket, Book Ticket, Make Payment, Update Database, Receive Money On Cancellation

  • Travel Agent: Book via Agent, Cancel Ticket via Agent, Online Inquiry, Fill Details, Book Ticket, Make Payment, Cancel Ticket, Update Database, Receive Money On Cancellation

  • Travel Counter Incharge: Book At Counter, Cancel Ticket At Counter, Online Inquiry, Fill Details, Book Ticket, Make Payment, Cancel Ticket, Update Database, Receive Money On Cancellation

Here we have some dependencies like Book Ticket Online, Book Via Agent and Book at Counter all three have <<include>> relationship with Online inquiry and Fill Details. In all these cases one needs to do online inquiry and then filling details. Fill Details further has a dependency <<include>> with Book ticket that again depends on Make Payment. Until and unless payment is made ticket can't be booked.

Again, Cancel Booking Online, Cancel Ticket at Counter and Cancel via Agent all three has a <<include>> dependency with Cancel Ticket and which further <<includes>> Receive Money On Cancellation, and updating database. Make Payment also <<includes>> updating database.

The Usecase UML Diagram for Airline Ticket Reservation is shown below:


 Related Articles
 Use Case Diagram Examples

No comments:

Post a Comment