Flight Booking Portal
Flight Booking Portal
ABSTRACT:
Major airlines are now starting to book air tickets online. But the problem lies in the user friendliness of such portals. Often users need to contact the support staff and simultaneously use the portal for booking. Others simply skip the online booking portal altogether and physically book their tickets.
Flight Booking Portal shows the ideal portal that such airlines need to implement. Its very user friendly and also effective. The users can very easily book their tickets and also get a print out of the same. They can also view flight information for planning their journey.
EXISTING SYSTEM
The existing airline reservation system has many shortcomings associated with it. In the existing system airlines used to set flight reservation levels higher than seating capacity to compensate for passenger cancellations and no-shows accounting to
overbooking in the system. If travelers had to make / cancel reservation he had to
visit either the airline or travel agent frequently to do so thus wasting time and money
for all. In the existing system due to non-availability of a central server the airline and
the agents suffered unwanted delays in bookings and payments. In the existing system
integration of different airlines on a single platform was not met. With the advent of
the online reservation system these flaws can be overcome.
PROPOSED SYSTEM
The new online reservation system maintains the database centrally giving the clients
the information required from anywhere in the world whenever required. This system
requires the use of an API (Application Programming Interface) through which it
extracts the data from a central database. The central database monitors all the data
changes that are made at the client side to it and updates it automatically.
Through online reservation system passenger is able to book & purchase the ticket
from his home/office conveniently it doesn’t require the passenger to go to the airline
or an agent to purchase a ticket thus saving time & money for the customer and an
airline/agent. As the information is stored centrally the passenger never loses his ticket
as in the existing system.
MODULE DESCRIPTION
Number of Modules
After careful analysis the system has been identified to have the following modules:
1. Administrator Module
2. Passenger Module
3. Check Flight Module
4. Book Ticket Module
5. Payment Module
6. Cancellation Module
1. Administrator Module
• Enables the airline administrator to perform all administrative functions
and manage inventory over LAN or the Internet.
• The administrator can define or modify routes, fares, schedules and assign or deny access rights for qualified travel agents and other authorized users.
2.PassengerModule
• The passenger should register himself in order to proceed the book ticket service.
• They need to input all the required particular details during the registration process.
• The web service will perform validation checks on passenger input and length constraints.
• Upon successful login, the passenger will be registered officially to the web service and he can login using his username and password.
• The guest is only permitted to check flight availability.
3.CheckFlightModule
• The passenger is permitted to search available flights based on the origin city, destination city, departure date and return date.
• The web service will display any matching records based on the search criteria entered.
• The web service will notify the passenger about the flight availability.
• If the searched flights are available, then web service will display flights which are within a week. Otherwise, the web service will prompt to ask the user to re-enter new searching criteria.
4. Book Ticket Module
• From the Check Flight, the passenger is required to log in and the web service will prompt the passenger to confirm the flights.
• The web service will then ask the passenger whether to update his profile details or not. Subsequently, the passenger will be asked to purchase and confirm the selected flights.
5. Payment Module
• After Book Ticket, the web service will generate payment ID upon successful transaction is made.
• Once it has been confirmed, the web service will generate booking id to the passenger and require the passenger to view the payment receipt.
6.CancellationModule
• The passenger is required to be logged in before he has privilege to cancel his confirmed tickets.
• The passenger will select which ticket to be cancelled in the booking history. Once the confirmed ticket has been selected then the web service will delete the data off from the database.
• The passenger is given cancellation ID upon successful transaction.
System Requirements:
Hardware Requirements:
• System : Pentium IV 2.4 GHz.
• Hard Disk : 40 GB.
• Floppy Drive : 1.44 Mb.
• Monitor : 15 VGA Colour.
• Mouse : Logitech.
• Ram : 512 Mb.
Software Requirements:
• Operating system : – Windows XP.
• Coding Language : VS2008
• Data Base : SQL Server 2005
Comments are closed.