Airline Reservation System

www.bscitmumbai.blogspot.com

Airline Reservation System

Submitted By: 10-ASHISH CHAURASIA

24-PRASHANT JAGTAP

- 1 - www.bscitmumbai.blogspot.com


56-KAMLESH SINGH



INDEXSr. No. Topic Pag

e

1. Project Scope 3

2. System Requirements 4

3. Entity Relationship Diagram 7

4. Database Designa. Table Structure 8b. Constraints 10c. Relationships 13

5. List of Processes 14

6. Data Flow Diagram 16

7. Limitations 21



This Project aims to model the working of an airway reservation system. The Project is built to model the reservation system as closely as

possible

Finding flight schedule information according to various constraints and condition.

Appropriate error checking.


PROJECT SCOPE


In this age, Computers are becoming the part of the human life which results into the growth of the reservation system. Many reservation system deals with computer Software whereas some interested in a automated reservation system.

We have introduced this software for managing the entire database of the reservation system for the automation of all aspects related to Airline Reservation System.

Before this software some the corresponding reservation system used to keep record in the form of handwritten documents but when a search for long time back record is needed then it becomes a headache of time consuming and power wastage for the company so the best way to handle this situation is to use this management software to improve the company’s performance.

This software is capable to keep track of entire company’s working and performance due to the following modules:

1. Employee:

These are the persons hired for working for the company. They are assigned to handle customers and manage the department also.

Employee usually updates the database as soon as reservation to the customer is done. The also make data entry of the employee for the passenger, ticket which includes flight details. This updates help Company to checkout the list of tickets booked for a particular flight.

2. Customer:

These are the person who doesn’t actually interact with the system but the indirect relation because they reserve ticket for a flight. Customer’s and employee’s details are been made to the system.

These all modules help to manage the system in its best way. Moreover, this system is introduced to meet the following user requirements:

1. Security:


SYSTEM REQUIREMENTS


It asks for login name (user id) and password for each user (employee) and manager also to enter into the system.

2. Compatibility with windows OS:

The software is actually designed to work under Windows platform. So the software is compatible with the Windows versions such as Windows 98, Windows XP, and Windows Vista.

3. Web Support:

The software can also jump directly to the web-markets through HTML links induced on the master-page of the software.

4. The master-page:

The master-page or welcome-page of this software contains the following modules in the form of links so one can easily jump to the required portion of the system:

a. Employee detail:

It includes the detail of all employees working in the company like name, ID, age, address, and many details. Access to this link is denied for all employees, only manager can access theses all records.

b. Customer detail:

It includes all details of the customers and the reservation done, different payment mode amount, date and time. All employees along with the manager have access to read these records.

c. Flights detail:

This link allows the employee to jump directly to the reservation system in the database. This will help them to understand at which different flights are available and their departure time.

5. For the implementation of my project the mirror H/W & S/W requirements as under


HARDWARE SOFTWARE

Pentium II to IV Window-9x,2000,2000serverAttempt 200 MHz MS-AccessRam –32MB MS-ExcelH.D .space-4xGB MS-WordFDD-CD ROM DRIVE-52x




HasBooks

ReceiveFor

Booked includes


ENTITY RELATIONSHIP MODEL

Department Employee Payment

Flight Details Ticket Passenger


Table Structure

Table: - Department

Column Name Data Type Length ConstraintDepartment_id Varchar2 8 PrimaryKeyDepartment_name Varchar2 25 Not null

Table: - EmployeeColumn Name Data Type Length ConstraintEmployee_id Varchar2 8 Primary KeyEmployee name Varchar2 30 Not nullEmployee add Varchar2 100 Not nullContact no Number 10Age Number 3 Not nullSalary Number 8 Not nullJoining date Date/Time Not nullLeave date Date/TimeLeave type Varchar2 10 Not nullDepartment_id Varchar2 8 Foreign KeyDesignation Varchar2 15 Not null

Table: - PassengerColumn Name Data Type Length ConstraintPassenger_id Number 8 Primary KeyPassenger name Varchar2 30 Not nullPassenger add Varchar2 100 Not null

Table: - TicketColumn Name Data Type Length ConstraintTicket_id Number 8 Primary Key Passenger_id Number 8 Foreign KeyEmployee_id Number 8 Foreign KeyFlight_Number Number 8 Foreign KeyPayment _id Number 10 Foreign KeyAirline Company Varchar2 15 Not nullSeat number Number 8 Not nullDate Date 15

Table: - Flight Details


DATABASE DESIGN


Column Name Data Type Length ConstraintFlight_Number Number 8 Primary KeyDate/Time Number Not nullDestination Varchar2 15 Not nullType_id Number 8 Foreign KeyTicket_id Number 8 Foreign KeyPassenger_id Number 8 Foreign Key

Table: - PaymentsColumn Name Data Type Length ConstraintPayment _id Number 10 Primary KeyPassenger_id Number 8 Foreign KeyTicket_id Number 8 Foreign Key Payment mode Varchar2 15 Not nullAmount Number 10 Not null.Date Date Not null.



Constraints

Table: - DepartmentColumn Name Constraint DescriptionDepartment_id Primary key It uniquely identify each record

from the department table.

Department_name Not null This Column cannot be null each department should have name.

Table: - EmployeeColumn Name Constraint DescriptionEmployee_id Primary Key It uniquely identify each

employee’s information from their id.

Employee_name Not null This column cannot contain null value the employee should have their name.

Employee_add Not null It cannot contain null value as employee must have an address.

Contact_no It can contain null value because contact number can exist or not.

Age Not null It cannot contain null value each Employee will have their age.

Salary Not null It cannot contain null value

Joining_date Not null It cannot contain null value

Leave_date It can contain null value.

Leave_type It can contain null value.

Department_id Foreign Key It is related to Department table.

Designation It can contain null value.

Table: - PassengerColumn Name Constraint Description

Passenger_id Primary Key It uniquely identify each passenger information from their id.

Passenger name Not null This column cannot contain Null value passenger Should have their name



Passenger add Not null It column cannot contain null value passenger should have their address. Table: - Ticket

Column Name Constraint Description Ticket_id Primary Key It uniquely identify each ticket information from their id. Passenger_id Foreign Key It is related to Passenger table.

Employee_id Foreign Key It is related to Employee table.

Airline Company Not null This column cannot contain null value as passenger decide the company.

Seat number Not null This column cannot contain null value as every passenger have their identical seat number. Date

Table: - Flight DetailsColumn Name Constraint Description

Flight_Number Primary Key It uniquely identify each Flight information from their id.

Date/Time Not null This column cannot contain null value as every flight have their specific date and time.

Destination Not null It cannot contain null value.

Type_id Foreign Key It is related to Ticket Type table.

Ticket_id Foreign Key It is related to Ticket table.

Passenger_id Foreign Key It is related to Passenger table.

Table: - PaymentsColumn Name Constraint Description

Payment _id Primary Key It uniquely identify Payment type information from their id Passenger_id Primary It uniquely identify each Foreign Key passenger information from their id.



Ticket_id Foreign Key It is related to Ticket table. Amount Not null This column cannot contain Null value as every flight have their amount paid. Date Not null It cannot contain null value as every payment done on a date



Relationships[ADD CONTENT FROM HERE]

LEFT ENTITY RIGHT ENTITY RELATIONSHIP CONSTRAINT

DEPARTMENT EMPLOYEE ONE-TO-MANY One department can have many employees.

EMPLOYEE TICKET ONE-TO-MANY One Employee can book one or many ticket

PASSENGER TICKET ONE-TO-MANY One Passenger can booked one or many ticket.

TICKET FLIGHT DETAILS ONE-TO-ONE One Ticket can have one or specific flight details

PAYMENT TICKET ONE-TO-MANY One Payment can be for one or many ticket




LIST OF PROCESSES


GENERAL ENQUIRY In this Process, if the customer request for information on flight or fare and getting the information

PASSENGER ENQUIRY If the passenger request for checking booking enquiry or checking New PNR information.

BOOKING If the passenger request for reservation and check the status of the confirm ticket.

FLIGHT ENQUIRY If the passenger request for flight information by checking database, we inform accordingly

FARE ENQUIRY If the passenger request for Fare enquiry for a particular flight by checking database we can inform accordingly.

NEW PASSENGER If the New Passenger comes he request to check for a particular flight seats are an available or not.

PASSENGER ENQUIRY If the Existing Passenger request to check whether existing PNR information.

ON THE SPOT If any Passenger come for on the spot reservation of the ticket.

STABD BY BOOKING If any Passenger comes for Stand By Booking or in advance booking for a particular flight.



PAYMENT MODE The Payment for a specific ticket, there can be a number of ways such as Cash, Credit, Cheque, and Debit


DATA FLOW DIAGRAM


Context Diagram: (Level 0)

Level 1: DFD of Airline Reservation System



LEVEL 2: DFD ON GENERAL ENQUIRY







LEVEL 2: DFD OF BOOKING



Since this management system is semi-automated causes a staff for data entry purpose which can switch to the human errors.

This reservation system cannot be used for Cancellation of ticket.


LIMITATIONS

Date post:	25-Nov-2014
Category:	Documents
Upload:	jayant-temkar
View:	107 times
Download:	0 times

Airline Reservation System

Documents