Management Plan

Features

This system will mostly be used by booking agents with varying levels of familiarity with computers. With this in mind, an important feature of this software is that it be relatively simple to use. The main function of the software will be to book passengers on selected flights. If the desired flight is not full the passenger should be given the option to choose his/her seat. Due to different needs of todays' travelers, the system will store special requests for food or assistance to inform the flight crew prior to departure. Any agent should be able to obtain information on flights, passengers, and possibly seat configuration layouts of each flight in order to quickly process each check-in and provide a detailed boarding pass to the customer. Over booking is commonly practiced among airlines to ensure there are no empty seat on the plane due to no-shows. The system should allow for this and in the event of an overbooked flight with too few seats, provisions should allow for compensation of the customer.

Major classes of Functions and Relationships Between them

The overall system can be broken down into two subsystems. The first is the Administrative subsystem and the second the Booking Agent subsystem.

The two subsystems form the ATICS application which is a functionally complete program that is capable of running an airline reservation system.

Administrative Subsystem

The administrative subsystem has three main modules. They are responsible for maintaining the different types of aircraft, booking agents, and scheduled flights.

The aircraft properties will be modifiable. Furthermore, an aircraft can be removed from active commission. Also, a new aircraft can be added to a new commission. Therefore, the datatype aircraft can be added/deleted/modified by the aircraft maintenance module.

The system information that will be affected by the aircraft maintenance module is as follows:

Aircraft:

• name, manufacturer, model etc.
• capacity
• layout

Booking Agent properties will also be modifiable much like the aircraft's. An agent can either be added, modified or deleted from the system. The system information that will be affected by the Booking Agent module is as follows:

Booking Agent:

• name, address etc.
• username
• password

Finally, scheduled Flight properties will be modifiable via the Flight maintenance module. Flights can either be added, removed, or modified. The system information that will be affected by this module is as follows:

Flight:

• departure and destination
• departure and arrival time
• aircraft type
• number
• seat prices

Booking Agent Subsystem

The Booking Agent subsystem has four main modules. They are responsible for maintaining the type Bookings and Seat Selection. Also, they will perform general queries and the task of checking in passengers.

The first module is for maintaining the type Booking. This is where the user can either add, modify or delete a booking. The system information affected by this module is as follows:

Booking:

• name, address
• flight number
• amount paid
• ticket number
• seat class
• special needs (meal etc.)

The second module is for maintaining the type Seat Selection. This is where the user can either add, modify or delete a seat selection. The system information affected my this module is as follows:

Seat Selection:

• ticket number
• seat number
• seat class

The General Query module will allow the user to obtain more information regarding a flight or a passenger. The queries will be performed by flight number, date, or destination. It should result in a list of passengers(with ticket numbers) and/or display a complete seat map. If a passenger query is executed the search should result in a listing of flights a given passenger has booked or display passenger information.

The final module is designed to check in a passenger. It will be used the day of the flight. If the passenger has already chosen a seat they will be issued a boarding pass. Otherwise, a seat will be assigned. Information that should appear on the boarding pass is as follows:

Boarding Pass:

• passenger name
• flight number
• boarding time
• ticket number
• seat number
• class

Possible Implementations

Both possibilities use industry standard equipment which is commonly available and are secure networked systems.

1. MS-Access 2.0 Relational Database

   Overview:
   This system would consist of "forms" which the user would fill out when conducting the check-in procedure. The customer information fields would be filled out and seating arranged. The database is updated after each form is completed. The object oriented environment of MS-Access provides a transparent system for the users.

   Features:

   1. Easy to use graphical environment
   2. Easy maintenance of database
   3. Low Hardware costs relative to other solutions
   4. Multi-user system

   Hardware Environment:
   PC Based Local Area Network with workstations for each agent. File Server for centralized access to the database.

2. Sybase Relational Database

   Overview:
   A similar paradigm would be used in this implementation with "screens" used to gather the customer data for updating the database.

   Features:
   

   1. Easy to use graphical environment
   2. Reliable network environment
   3. Multi-user system
   4. Fast access time

   Hardware Environment:
   UNIX Based Local Area Network with workstations or PC's for each agent. File Server for centralized database.

Possible Main Data Structures and Algorithms

Please note that this information is preliminary.

Data Structures

Relational Database for airline flight schedule information

• sub-tables for each flight containing seating information
• sub-table for customer information

The data structures used for relational databases are tables. A table would exist for the customers, one for the flight schedule, and one for the seat selection on one flight. These tables are then linked via common information.

Algorithms

User formulated queries for flight information using structured queries. Users are lead through the queries via an easy to use graphical environment with fields for various search criteria.

e.g. List flight from Flin Flon to Vancouver between March 3 and March 5
e.g. List customer on flight # 102 with lastname "SMITH"

Minimal System and Enhancements

Due to Flin Flon Airlines' desire for the quick implementation of this project and their need for a scaled down version to be operational by late February, each feature must be categorized either as a minimal system feature or enhancement feature which will be incorporated at a later date.

The features in their major function groupings and feature categories are listed below:

Booking Agent

Minimal Features:

• add/ delete/ modify booking
• query flight info by date number and destination
• query passenger by name, ticket number or phone number
• produce a boarding pass with required information on it
• automatic seat availability update 15 minutes prior to departure, when seats that have been assigned but no boarding pass has been issued become available
• listing of all seats divided into available seats, seats assigned and boarding pass issued, seat assigned with no boarding pass issued.

Enhancements:

• aircraft map with seat configuration with current vacant seats indicated
• allow for 10% refund of fare if booked-passenger unable to get flight due to over book. (No indication was given by customer about forms of transaction (i.e. cash,credit card, cheque) so this must be implemented at a later date)

Administration Options

Minimal Features:

• add/modify/delete aircraft type
• add/modify/delete booking agent
• change flight information such as dep. time, aircraft type, prices, flight numbers, etc.

Enhancements:

• Additional reports such as flight popularity with seasonal trends

Summary

As a well-structured software supply team, we make it our duty to please the customer. Flin Flon Airlines needs are important to us and we will do our best to meet the needs of your distinguished company. The important key points of our management plan are as follows: