Scribd Logo
Upload

Welcome to Scribd!

  • 669 views

    Airline Management System Documentation

    Uploaded by

    Deepak
    The document describes an airline management system with several use cases: 1) Login - allows airline staff to access the system after logging in. 2) View Tickets - allows passengers to view available flights between destinations. 3) Book Tickets - allows passengers to reserve seats on selected flights. 4) Cancel Tickets - allows passengers to cancel previously booked reservations. 5) Check Reservation - allows passengers to check the status of their reservations. 6) Check Flight Occupancy - allows airline staff to view available seats on flights. 7) Update Schedule - allows administrators to modify flight schedules. 8) Update Flight Info - allows administrators to edit details of existing flights.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Airline Management System Documentation

    Uploaded by

    Deepak
    669 views4 pages
    The document describes an airline management system with several use cases: 1) Login - allows airline staff to access the system after logging in. 2) View Tickets - allows passengers to view available flights between destinations. 3) Book Tickets - allows passengers to reserve seats on selected flights. 4) Cancel Tickets - allows passengers to cancel previously booked reservations. 5) Check Reservation - allows passengers to check the status of their reservations. 6) Check Flight Occupancy - allows airline staff to view available seats on flights. 7) Update Schedule - allows administrators to modify flight schedules. 8) Update Flight Info - allows administrators to edit details of existing flights.

    Original Title

    Airline Management System Documentation.docx

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes an airline management system with several use cases: 1) Login - allows airline staff to access the system after logging in. 2) View Tickets - allows passengers to view available flights between destinations. 3) Book Tickets - allows passengers to reserve seats on selected flights. 4) Cancel Tickets - allows passengers to cancel previously booked reservations. 5) Check Reservation - allows passengers to check the status of their reservations. 6) Check Flight Occupancy - allows airline staff to view available seats on flights. 7) Update Schedule - allows administrators to modify flight schedules. 8) Update Flight Info - allows administrators to edit details of existing flights.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    669 views4 pages

    Airline Management System Documentation

    Uploaded by

    Deepak
    The document describes an airline management system with several use cases: 1) Login - allows airline staff to access the system after logging in. 2) View Tickets - allows passengers to view available flights between destinations. 3) Book Tickets - allows passengers to reserve seats on selected flights. 4) Cancel Tickets - allows passengers to cancel previously booked reservations. 5) Check Reservation - allows passengers to check the status of their reservations. 6) Check Flight Occupancy - allows airline staff to view available seats on flights. 7) Update Schedule - allows administrators to modify flight schedules. 8) Update Flight Info - allows administrators to edit details of existing flights.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 4

    Airline Management System Documentation

    Use case Name: Login


    Actor: airline staff.
    Pre-Condition: a person who login is an airline staff.
    Post-Condition: after successfully login, system will be accessible.
    Basic Flow: the airline staff will first login to the system and then do further tasks.
    Alternative: if login failed the system not be accessible.
    Special Requirements: staff credentials.

    Use case Name: View Tickets


    Actor: Passenger.
    Pre-Condition: specifying source and destination.
    Post-Condition: checks the list of flights with their specifying tickets.
    Basic Flow: the passenger will check the dozen of flights tickets according to their specifying
    details.
    Alternative: if the requirement will not match with the existing flights then no flight will be shown.
    Special Requirements: specifying requirements (like source, destination, timing);

    Use case Name: Book Tickets


    Actor: passenger.
    Pre-Condition: choose a flight according to their requirement.
    Post-Condition: books tickets of that flight according to suitable class.
    Basic Flow: After choosing a flight, passenger can book their tickets of that flight according to
    their suitable class.
    Alternative: if the desired tickets will not available then passenger will not book their tickets any
    more.
    Special Requirement: availability of desired no of tickets.
    Relationships:
    1. Include: - if a passenger book a tickets than they also have an option of cancelling the
    booked tickets. There must have a include relation in between the Book tickets and
    cancel tickets use case.
    Use case Name: Cancel tickets
    Actor: passenger.
    Pre-Condition: book ticket details.
    Post-Condition: passenger can cancel booked tickets if they want.
    Basic Flow: if passengers wants to cancel their booked tickets then they can do so.
    Alternative: if tickets were not booked than there is no way to cancel it.
    Special Requirements: ticket details.

    Use case Name: Check reservation


    Actor: passenger.
    Pre-Condition: reservation details.
    Post-Condition: check reservation status according to the given reservation details.
    Basic Flow: if passenger wants to check their reservation status then they can do so.
    Alternative: if the reservation detail is not valid then request will be deny.
    Special Requirements: reservation details.

    Use case Name: check flight occupancy.


    Actor: airline staff.
    Pre-Condition: staff were login already.
    Post-Condition: airline staff will check weather how much tickets will remain free.
    Basic Flow: this use case start when there was a requirement of the airline staff to check free
    tickets remain in the specified flight.
    Alternative: if staff is not login at that time than it may not able to check the flight occupancy.
    Special Requirements: staff were login already.

    Use case Name: Update Schedule.


    Actor: Administrator
    Pre-Condition: list of flights which schedule is going to update.
    Post-Condition: update the required flight schedule.
    Basic Flow: this use case is come when there is required to update the schedule of the flights.
    Alternative: schedule of flights will varies with different circumstances.
    Special Requirement: list of flights details which will be reschedule.

    Use case Name: update flight info.


    Actor: Administrator.
    Pre-Condition: list of flight details which will going to update.
    Post-Condition: update the required flight details of the existing flights.
    Basic Flow: this use case is come when there is required to update the details of existing flight.
    Alternative: if the details of the flight is wrong than whole system will suffers from this.
    Special Requirement: correct details of the flight which will update.

    You might also like