Before modern computing, the reservation system was done using manual means. This meant that a person about to travel had to spend a lot of unnecessary time waiting in queues in order to book their tickets. The manual process of reservation was also prone to human errors, which lead to a lot of dissatisfaction amongst travelers. The Airline Ticketing System proposed in this project will aim to automate the process of booking airline tickets online, thus reducing the time wasted as well as the errors that are involved in the manual process. The system in question will be available online, empowering future travelers to reserve their tickets themselves at the convenience of their on home. From the viewpoint of the Airline Company, the aims are to minimize repetitive work done by the system administrator and reservation clerks. Maintain consistency among different access modes, e.g. by phone, by web, at the information desk and across different physical locations. The users should be basically taken through the same steps by the system as they go through in conventional desk-reservation systems i.e. a true model of the physical world. The various access nodes are commonly referred to as channels. Maintain customer information. Maximize the revenue of the airline company by attracting global travelers to the company domain. Increase awareness among frequent travelers about various special offers and discounts. Maintain the capability to adopt a flexible pricing policy. The price of the tickets should be dynamically determined based whether or not the customer is a registered user as well as check whether the user qualifies for any discounts.
[...] The actions that an Administrator is allowed to take are as follows: o Add, Edit or Delete an Airplane o Add, Edit or Delete a Flight o Add, Edit or Delete a Schedule o Add, Edit or Delete a Scheme Operating Environment Hardware Platform The Airline Ticketing System will be available to the User's using the World Wide Web as a means of access. Therefore the system has two aspects, namely the client and the server. The Client: The hardware requirements of the client are as follows: o An Internet Connection o Color Monitor or any other Visual Display Unit o Printer o Mouse and Keyboard for User Inputs The Server: The hardware requirements for the server are as follows: o Multiple storage devices based on necessity o A minimum of 512 MB of Random Access Memory o Connection to the World Wide Web Software Platform The Client: The software requirements of the client are as follows: o Operating System o Web Browser The Server: The software requirements of the server are as follows: o The Dot Net Framework o Microsoft SQL Server System Context The Airline Ticketing System will provide the following types of easy-to- use, interactive, and intuitive graphical interfaces. [...]
[...] The Airline Ticketing System is based on the flights that the Airline company has. These follow a very precise schedule and are subject to change. The Administrator, who is an authorized employee of the Airlines Company, has the authorization to update the flight details/schedules of a particular flight. Trigger: A request to Update Flight Details Preconditions The User must be logged in as an Administrator. A flight has to exist in order for it to be deleted. When deleting a flight, no tickets can be booked on that flight. [...]
[...] Figure Adapted Architecture for Airline Ticketing System Advantages of Using the Model, View and Control Approach o The approach gives us the Scalability and Flexibility that is required for the system. Given any change in requirement, it would be possible to change only that aspect without having to change any other aspect of the system. o Changes can be implemented simplistically o Owing to the fact that one has to pass through several layers before access to the database is granted, this approach provides yet another layer of security. [...]
[...] Non-Functional Requirements Performance -Response time of the Airline Ticketing System should be less than 2 second most of the time. --Response time refers to the waiting time while the system accesses, queries and retrieves the information from the database. -It shall be able to handle at least 1000 transactions/inquiries per second. -It shall show no visible deterioration in response time as the number of users or flight schedule data increases Reliability -The System shall be available 24 hours a day days a week -It shall always provide real time information about flight availability information. [...]
[...] The Airline Ticketing System proposed in this project will aim to automate the process of booking airline tickets online, thus reducing the time wasted as well as the errors that are involved in the manual process. The system in question will be available online, empowering future travelers to reserve their tickets themselves at the convenience of their on home. From the viewpoint of the Airline Company, the aim is as follows: Minimize repetitive work done by the system administrator and reservation clerks. [...]
Online readingwith our online reader
Content validatedby our reading committee