System Administration Functional Specifications

1. Flights:
   • Flights will not be cancelled unless they have no passengers booked - otherwise the flight will be rescheduled. When a flight is rescheduled, we need a printout of passengers with their names and numbers so that they can be notified of the change. A refund of 10% would be computed, displayed and recorded on each passenger's record for that flight.
   • The flights should be sorted by date by default, with the option of sorting by destination or departure point. (Note that we do need departure points - we will have return flights, at least.)
   • It should possible to search by date or date range, destination, departure point, and flight number (without scrolling).
   • The flight number should be assigned automatically by the system.
   • When entering flights, it would be nice to be able to select destinations, departure points, and aircraft types from lists.
   • We need to enter the rates for each class (1st, 2nd and 3rd) on each flight.
2. Aircraft:
   • We didn't ask that specific airplanes be entered in the system, just airplane types, and we would like to be able to give the seating layout for each type. This would include capacities for each class, and would allow us to specify the number of seats in each row (seats would be numbered by row number and a letter) and which ones are window, centre or aisle seats, as well as which rows are in each class. This could be done by marking a grid, giving the range of rows followed by the number of seats in the left, middle and right sections for those rows, or by any other method that is reasonably user-friendly. We realize that this feature may be difficult to implement in the limited time available, but we mention it because a seating map is referred to elsewhere in your specifications.

Booking Agent Functional Specifications

1. Booking a passenger:
   • The ticket number should be assigned by the system.
   • When the point of departure, destination, year and month have been given, we would like a list of dates and times just for flights that are not already booked to 115%.
   • A message should appear if a seat is not available in the passenger's chosen class for the selected flight, so that the booking agent can place the passenger in another class.
2. Query Passenger Information:
   • We would like to do a search by passenger name or ticket number.
   • The list of flights for a passenger should show their seat number (row number and letter) and class, and ideally whether it is a window, centre or aisle seat.
   • No field indicating whether the passenger has paid is necessary, since we are assuming that the ticket is paid for at the time of booking.
3. Query Flight Information:
   • This should also have a list of departure points.
   • The passenger list should give the seat number and class for each passenger and maybe whether it is a window, centre or aisle seat.
   • Dates - Are these the dates of future flights with the same destination and departure point? We don't need this information here.
4. Issue Boarding Passes & Issue Refunds:
   These should be combined as follows:
   • The booking agent will select the flight from a list of the days flights, then the passenger from a list that should show whether the passenger has a seat assignment. When the passenger is selected, a boarding pass can be automatically issued if they have an assigned seat and the seat map is revised accordingly (the agent wouldn't need to see the map in this case). If the passenger doesn't have a seat assignment and the booking agent chooses to issue a boarding pass, the seating map would come up (unless no seats were left that had not been taken), and the agent could choose a seat assignment from the map, then the boarding pass would be issued.
   • If boarding passes had been issued for all of the seats, the booking agent could bring up a list of other flights not yet booked to 115% with the same destination and departure point (sorted by date) and rebook the passenger on one of these. The refund amount would be computed automatically when the passenger was rebooked and stored with the passenger's information for that flight, and a voucher for the refund amount would be issued. The passenger's booking could be cancelled instead, in which case no record would be needed, although a voucher for the ticket's cost would be issued to the passenger.

FLIN FLON AIRLINES