SCREEN LAYOUT (CHAPTER 11)

CHAPTER  11

SCREEN LAYOUT

HOME PAGE

FLIGHT DISPLAY

TICKET DESCRIPTION WITH FARE

ALREADY A MEMBER/NOT A MEMBER/LOGIN

CONTACT INFORMATION & MODE OF PAYMENT

CONGRATULATION-‘Ticket has been booked successfully’

REFERENCE NO. 1274000996784

PRINT E-TICKET

UPDATE PROFILE

CANCELLATION OF TICKET

CANCELLATION OF TICKET (contd.)

CONCLUSION/SCOPE (CHAPTER 10)

CHAPTER  10

CONCLUSION/SCOPE

Airline Reservation System (ARSystem) Web Site is a project work and not a real time reservation system intended for the partial fulfillment of  Bachealor in  Computer Engineering (4^rd Year).

This is an automatic Internet based system to book any domestic flights from one place to another. All the data relating to the flight schedules has been created in ARSystem database. It is not dyanamically linked with the concern airlines.

International flights are not covered due to huge database and limitation of the project work. However,  if the system is linked with various database of the airlines and a little bit modification in the codings and layouts, the system can work for international flights as well.

The ticket is a model ticket, not actual one. ARSytem can be made on real time by signing a Memorandum of Understanding (MoU) defining the terms and conditions between the ARSytem and the concern airlines.

SYSTEM IMPLEMENTATION (CHAPTER 9)

CHAPTER  9

SYSTEM IMPLEMENTATION

For the implementation of Airline Reservation System following  H/W and S/W are required:

HARDWARE	SOFTWARE
Pentium II onwards	Window-2000/XP/Vista(32-bit)/Windows-7
RAM-256 MB or more	Tomcat 6 server
Hard Disk Space- 20 GB	JDK 1.6
CD-ROM Drive-52x	MySQL 5
Pen Drive	Internet Explorer/Mozilla Firefox

HARDWARE:

Above hardwares  are generally available in recent computers otherwise to be installed.

SOFTWARE:

Almost all softwares are freely available on Internet. Location of a few software are given below:

1. Tomcat 6 Server(http://tomcat.apache.org/download-60.cgi)
2. JDK 1.6(http://java.sun.com)
3. MySQL 5(http://www.mysql.com/)

IMPLEMENTATION:

Step of implementation and mode of operation are:

• Open the Tomcat 6.0 Server.
• Open the browser(Internet Explorer/Mozilla Firefox) and enter the URL of ARSystem   http://localhost:8080/AirlineReservationSystem/
• Home page ARSystem will be displayed.
• Enter-------From, To, Depart(data), Class, Adults, Children(2-11 yrs), Infants(under 2 yrs) and then click on the search button.
• Flights display--------list of all flights available on a parlicular day.
• Select flight of your choice.
• Description of ticket along with fare and continue booking.
• Login page displayed.

1.       Already a Member ? Login

Enter email and password and then click on login button.

2.       Not a Member ? Register

Enter Title(Mr.,Mrs.,Ms.), First Name, Last Name, Email, Password, Confirm PASSWORD, City, Country, Pin , Address1, Address2, Mobile#, Alternate# and then click on Register button.

• Your contact information as shown above and Lead Customer’s(First Adult) Title, First Name, Last Name and mode of payment(Credit Card, Debit Card, Net Banking) click on Continue Booking.
• A message will be displayed “Congratulations, your ticket has been booked successfully. Your booking reference number is : 1274000996782” and then click on Show My Ticket button.
• Ticket is issued and can be printed by clicking on Print Ticket button.
• If you want to cancel your ticket/update your profile/ change password then go to home page and click on Login/Register.
• Already a member------Enter Email and Password and click on Login button.
• A page called my booking will be displayed Update Profile, Change Password, Print E-Ticket, Cancel E-Ticket, Booked History, Cancelled History.

1.      Update Profile : - To update profile click on Update Profile link and fill the fields Email Id, Salutation, First Name, Last Name, City, Country, Address1, Address2, Mobile No., Alt. Contact, Pin Code and then click on Update Profile button.

2.      Change Password : - If user want to change the password then click on Change Password link and enter the new password and then click on Update Password button.

3.       Print E-Ticket  : -To print ticket click on  Print E-Ticket link then “Enter the booking reference number : “in the displayed field and then click on Get Ticket button.

4.       Cancel E-Ticket : - To cancel ticket click on Cancel E-Ticket link then then “Enter the booking reference number : “ in the displayed field and then click on Get Ticket button.

5.       Booked History & Cancelled History : -  On click the button displays the detail history of the booking /cancel.

• If not a member then register himself by entering Title(Mr.,Mrs.,Ms.), First Name, Last Name, Email, Password, Confirm PASSWORD, City, Country, Pin , Address1, Address2, Mobile#, Alternate# and then click on Register button.

DATABASE DESIGN (CHAPTER 8)

CHAPTER  8

DATABASE DESIGN

Table  : tbl_country

tbl_country

CREATE TABLE  `airlinereservationsystem`.`tbl_country` (

  `id` int(7) unsigned NOT NULL auto_increment PRIMARY KEY, 

`country_name` varchar(50) default NULL,) 

Table   :  tbl_domestic_airlines Table

tbl_domestic_airlines

CREATE TABLE  `airlinereservationsystem`.`tbl_domestic_airlines` (

  `ID` int(10) unsigned NOT NULL auto_increment PRIMARY KEY,

  `AIRLINES_NAME` varchar(45) NOT NULL,

  `SEAT_ECONOMY` varchar(45) NOT NULL,

  `SEAT_BUSINESS` varchar(45) NOT NULL,) 

Table  : tbl_flight_info

tbl_flight_info

CREATE TABLE  `airlinereservationsystem`.`tbl_flight_info` (

  `ID` int(10) unsigned NOT NULL auto_increment,

  `FLIGHT_NUMBER` varchar(45) NOT NULL,

  `ORIGIN_CITY` int(3) NOT NULL,

  `DESTINATION_CITY` int(3) NOT NULL,

  `DEPARTURE_TIME` int(10) unsigned NOT NULL,

  `ARRIVAL_TIME` int(10) unsigned NOT NULL,

  `DEPARTURE_DAYS` varchar(45) NOT NULL,

  `AIRLINES_ID` int(10) unsigned NOT NULL,

  PRIMARY KEY  (`ID`),

  KEY `AIRLINES_ID` (`AIRLINES_ID`),

  CONSTRAINT `tbl_flight_info_ibfk_1` FOREIGN KEY (`AIRLINES_ID`) REFERENCES `tbl_domestic_airlines` (`ID`)

)

Table  : tbl_geographical_cities

tbl_geographical_cities

CREATE TABLE  `airlinereservationsystem`.`tbl_geographical_cities` (

  `ID` int(10) unsigned NOT NULL auto_increment PRIMARY KEY,

  `STATION_1` int(3) NOT NULL,  `STATION_2` int(3) NOT NULL,

  `DISTANCE` int(10) unsigned NOT NULL,)

Table  : tbl_mastercity

tbl_mastercity

CREATE TABLE  `airlinereservationsystem`.`tbl_mastercity` (

  `ID` int(10) unsigned NOT NULL auto_increment PRIMARY KEY,

  `CITY_NAME` varchar(45) NOT NULL,

)

Table  : tbl_registration

tbl_registration Table

CREATE TABLE  `airlinereservationsystem`.`tbl_registration` (

  `id` int(7) unsigned NOT NULL auto_increment,

  `salutation` varchar(4) NOT NULL,

  `first_name` varchar(50) default NULL,

  `last_name` varchar(50) default NULL,

  `email_id` varchar(50) default NULL,

  `password` varchar(20) default NULL,

  `city_name` varchar(50) default NULL,

  `country_id` int(7) unsigned default NULL,

  `address_1` varchar(500) default NULL,

  `address_2` varchar(500) default NULL,

  `mobile_number` varchar(10) default NULL,

  `alternate_number` varchar(12) default NULL,

  `pin_code` varchar(6) default NULL,

  PRIMARY KEY  (`id`),

  UNIQUE KEY `email_id` (`email_id`),

  KEY `FK_tbl_registration` (`country_id`),

  CONSTRAINT `FK_tbl_registration` FOREIGN KEY (`country_id`) REFERENCES `tbl_country` (`id`) ON DELETE CASCADE ON UPDATE CASCADE

) 

Table  : tbl_reservation

tbl_reservation

CREATE TABLE  `airlinereservationsystem`.`tbl_reservation` (

  `id` int(7) unsigned NOT NULL auto_increment,

  `user_id` int(7) unsigned NOT NULL,

  `flight_id` int(7) unsigned default NULL,

  `class` char(1) default NULL,

  `no_of_passengers` int(3) unsigned default NULL,

  `booking_date` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,

  `travel_date` timestamp NOT NULL default '0000-00-00 00:00:00',

  `airlines_id` int(7) unsigned NOT NULL,

  PRIMARY KEY  (`id`),

  UNIQUE KEY `indx_user_id` (`user_id`),

  UNIQUE KEY `indx_flight_id` (`flight_id`),

  KEY `indx_airlines_id` (`airlines_id`),

  CONSTRAINT `FK_tbl_reservation_1` FOREIGN KEY (`user_id`) REFERENCES `tbl_registration` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,

  CONSTRAINT `FK_tbl_reservation_2` FOREIGN KEY (`id`) REFERENCES `tbl_flight_info` (`ID`) ON DELETE CASCADE ON UPDATE CASCADE,

  CONSTRAINT `FK_tbl_reservation_3` FOREIGN KEY (`airlines_id`) REFERENCES `tbl_domestic_airlines` (`ID`) ON DELETE CASCADE ON UPDATE CASCADE

)

Table  : tbl_state

tbl_state

CREATE TABLE  `airlinereservationsystem`.`tbl_state` (

  `id` int(7) unsigned NOT NULL auto_increment,

  `state_name` varchar(50) default NULL,

  `country_id` int(7) unsigned default NULL,

  PRIMARY KEY  (`id`),

  KEY `FK_tbl_state` (`country_id`),

  CONSTRAINT `FK_tbl_state` FOREIGN KEY (`country_id`) REFERENCES `tbl_country` (`id`) ON DELETE CASCADE ON UPDATE CASCADE

)

Table  : tbl_week_days

tbl_week_days

CREATE TABLE  `airlinereservationsystem`.`tbl_week_days` (

  `ID` int(10) unsigned NOT NULL auto_increment PRIMARY KEY,

  `DAYS` varchar(45) NOT NULL,

)

 Table : tbl_passenger_details

tbl_passenger_details

CREATE TABLE  `airlinereservationsystem`.`tbl_passenger_details` (

  `id` int(10) unsigned NOT NULL auto_increment,

  `first_name` varchar(45) NOT NULL,

  `last_name` varchar(45) NOT NULL,

  `age` int(10) unsigned NOT NULL,

  `gender` char(1) NOT NULL,

  `registered_user_id` int(7) unsigned NOT NULL,

  PRIMARY KEY  (`id`),

  KEY `indx_registered_user_details` (`registered_user_id`),

  CONSTRAINT `FK1` FOREIGN KEY (`registered_user_id`) REFERENCES `tbl_reservation` (`user_id`) ON DELETE CASCADE ON UPDATE CASCADE

)

Relationship between tables 

APPLICATION DESIGN (CHAPTER 7)

CHAPTER  7

APPLICATION  DESIGN

7.1      User Accounts

7.1.1   General Description

The passenger ( also called  as the ‘user’) has 2 choices by the reservation system, whether he/she is a new user or a registered user and wants to check the availability of tickets or also buy them. The term ‘registered user’ mean a user who has earlier purchased the ticket through the reservation system (ARSystem) and would have been given a user id and a password. He/she would have his/her personal information stored in the database as ‘tbl_registration’. This ‘personal information’ would be henceforth referred to as ‘profile’. Such a user with a profile in tbl_registration shall be called a ‘registered user’. A registered user will be able to check the availability of tickets as well as buy a ticket by logging into the system.

A new user would either have to (a) register himself/ herself with the system by providing personal information or (b) log into the system as a new user to check the availability of ticket.

In case of ‘a’, the new user becomes a registered user.  In case of ‘b’, the new user would remain a new user.

 ‘Availability of tickets’ always refers to viewing the flight schedule for given days, the price of tickets and any discount offers. The system shall present the user with an option to exit from the system at any time during the  processes.

7.2      Registration and creation of user profile

7.2.1   General Description

The system shall require a user to register, in order to carry out any transactions with it except for checking the availability of tickets. It will ask the user for the following information atleast – a user id, a password, first name, last name, address, phone number, email address, sex, age, preferred credit card number. The system will automatically create a field and initialize it to zero in the user’s profile.

7.3      Checking Availability/Query Flight Details

7.3.1   General Description

 After logging the ARSystem, the home page will be displayed. The system shall request him to enter the following details – origin city and destination city. “City’ is a generic term and refers to a city or town as the case may be. The origin and destination cities would be entered as text through drop down provided by the system.

The system shall now ask the user to enter the following details - class, one-way or round trip, departure date and the number of adult passengers, children and infants, if any. ‘Class’ refers to Executive class/ Economy class. This choice shall be made by the user through a drop down menu indicating all the possible combinations of choices.

One-way/round trip shall be a radio button selection. ‘Departure date’ refers to  a single date entered through a calendar-like menu which will show dates in the current month and of the next month. In case, the trip is a round trip, the system shall also ask the user to enter the departure date on the return trip.

After the origin and destination cities are ascertained, the system shall now access the flight schedule database as ‘tbl_flight_info’ and checks if there is a direct operational service between the two cities.

Having taken all of the information, the system shall now access the flight schedule database ‘tbl_flight_info’ and queries it using the input provided by the user checks which of the flights on the schedule have seats available.

The system shall now refer to the flight schedule database as ‘tbl_geographical_cities’ , which contains list of cities from where the flights operates.

The system displays the results in a suitable form (a tabular form) with the following information depicted – for each flight number – the flight number, departure time in origin city, arrival time in destination city, the duration of the flight (taking into account the possibility of a change of time zone) and the number of seats available on that flight along with cost for one ticket.

There can be several flights between two cities and all of them will be listed for the particular date that the user wants to depart from the Origin City.

The user is now asked to check one flight number and time. In case of a round trip, the user is asked to check one for the onward trip and one for the return trip separately. The system will display a form to enter details of each passangers- first name, lastname, adult  and/or child and/or infant. After that the system will display the price of the ticket for the trip. This will be the sum of the prices for all the members of the travel party being represented by the user.

The system shall also list any rules regarding the cancellation of tickets – what percentage of the price will be refunded within what date ranges. This will be displayed as a table.

7.4    Making Reservations

7.4.1   General Description

After having taken the user through the steps, Checking Availability. The system will now ask the user if he wishes to buy the ticket. If yes, then he/she has first to register and become a registered user and then log onto the system.

If the user is already a registered user, and if he/she has logged on already, he can buy the ticket and the system will ask the user to check the submit button.

The system accesses his/her  profile and charges the price of the ticket to his/her credit card number or the other options given in the check boxes. It simultaneously generates a confirmation ticket and displays it to the user for him/her to note down. The ticket has been reserved.

7.5      Cancellation

7.5.1   General Description

The system shall also give the user an option to cancel a confirmed ticket.

For a confirmed ticket, the system will ask for the confirmation number and accesses tbl_reservation and presents the details of the trip reserved.

It then lists the applicable rules for cancellation of tickets and depending on the system date and the departure date, it displays the % of the amount that would be refunded if the user cancels the ticket.

After the user cancels the ticket, the system generates a cancellation number and displays it for the user to note down. It accesses tbl_reservation and updates it by incrementing the number of available seats on that flight by the number of travelers in the user’s party. It accesses DB-user and credits the refund amount to his credit card number.

7.6      Update Profile

7.6.1   General Description

The system shall enable the user to update his profile at any time. Changes can be made in fields including but not limited to address, phone number and preferred credit card number.

SYSTEM ANALYSIS & DESIGN (CHAPTER 6)

CHAPTER  6

SYSTEM ANALYSIS & DESIGN

6.1 SYSTEM ALALYSIS

Analysis of the existing system reveals four major components e.g. Customer/Passenger, Booking department, Database and Reports. A block diagram depicting these components are given below in the block diagram :

6.2 ER DIAGRAM

The ER diagram is drawn to have a better understanding of the whole scenario, it was used to conceptualize the phenomena, actions and interactions between various entities and to arrive at the specific requirements in a comprehensive manner. The ER diagram is attached with this SRS.

The overall logic structure of database can be expressed by ER-Diagram, (Entity Relationship Diagram), which is built up with components: Entity Sets (shown as rectangles), Attributes (shown as ellipses), Relationships (shown as diamond) and Links (shown as lines). An entity is a thing or object in the real world that is distinguishable from other objects e.g. Each passenger/customer, booking etc. The entities are described in a database by a set of attributes e.g. customer id, customer name, customer address etc. A relationship is an association among several entities e.g. confirm, valid, waiting etc.

6.3 DATA FLOW DIAGRAMS                           

Data flow diagrams (DFDs) reveal relationships among and between the various components in a program or system. DFDs are an important technique for modeling a system’s high-level detail by showing how input data is transformed to output results through a sequence of functional transformations. The DFD (also known as the bubble chart) is a simple graphical formalism that can be used to represent a system in terms of the input data to the system, various processing carried out on those data, and the output data generated by the system. DFD is  very simple formalism, simple to understand and use.

A DFD model uses a very limited number of primitive symbols to represent the functions performed by a system and the data flow among these functions. DFDs consist of four major components : entities, processes, data stores, and data flows. The symbols used to depict how these components interact in a system are simple and easy to understand. A set of DFDs provides a logical model that shows what the system does, not how it does it.

LEVEL 0 DATA FLOW DIAGRAMS

(CONTEXT DIAGRAM)

                                                                        Level 2 DFDs

LEVEL 2 DATA FLOW DIAGRAMs

MODE OF PAYMENT