Airline Reservation System Presentation

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 33

Project Presentation

Airline Reservation System


CONTENT
1. Introduction
2. Module Description
3. Need of Software
4. Data Flow Diagram
5. E-R Diagram
6. System Requirements
7. Database Design
8. ScreenShot
9. Testing And Implementation
10.Conclusion
11.Bibliograpghy
INTRODUCTION
The "Airlines Reservation System" has been developed to override the
problems prevailing in the practicing manual system. This software is
supported to eliminate and in some cases reduce the hardships faced by
this existing system.

The application is reduced as much as possible to avoid errors while


entering the data.

It also provides error message while entering invalid data. No formal
knowledge is needed for the user to use this system. Thus by this all it
proves it is user-friendly.

Airlines Reservation System, as described above, can lead to error free,


secure, reliable and fast management system.

It can assist the user to concentrate on their other activities rather to
concentrate on the record keeping. Thus it will help organization in
better utilization of resources.
MODULE DESCRIPTION
•Login Module: Used for managing the login details.

•Passenger Module: Used for managing the detail of passengers.

•Domestic Booking Module: Used for managing the details of Domestic


Flight Booking.

•International Booking Module: Used for managing the details of Foreign


Flight Booking.

•Reservation Module: Used for managing the information and detail of


the Flights.

•Cancellation Module: Used for cancel the ticket reservations.

•Payment Module: Used for managing the Bills of flight booking.

•Reports Module: Used for managing the reports of the system.


NEED OF SOFTWARE
To reduce workload.

To reduce the delay in processing time.

To reduce the delay in bill generation.

To provide the user-friendliness in all possible ways.

To provide greater flexibility.

Make maintenance changes easy.

To store data in a centralized location to reduce redundancy and


increase consistency.
FLOW DIAGRAM
DATA FLOW DIAGRAM
Zero Level Data Flow Diagram:
First Level Data Flow Diagram:
Second Level Data Flow Diagram:
E-R DIAGRAM
SYSTEM REQUIREMENTS

 Hardware Requirements:-
 

Processor : Intel(R) Pentium(R) CPU 2127U @ 1.90GHz


Primary Memory (RAM) : 4 GB or Above
Secondary Memory (Hard disk) : 20 GB or Above
 
 Software Requirements:
 
Operating System : Windows 7 or above
Front End tool : VB.NET
Back End tool : SQL Server
DATABASE DESIGN
Login and Registration Database:-
Passenger Database:-
Flights Booking Database:-
Reservation Database:-
Payment Database:-
SCREENSHOT
Login:
Home:
New Passenger:
Domestic Flight Booking:
International Flight Booking:
Reservation:
Cancellation:
Payment:
Bills Generation:
Tickets Generation:
TESTING AND
IMPLEMENTATION

System Testing is a type of software testing that is performed on a


complete integrated system to evaluate the compliance of the system with
the corresponding requirements.

System Testing is carried out on the whole system in the context of


either system requirement specifications or functional requirement
specifications or in the context of both. 

Testing is a set of activities that can be planned in advance and


conducted systematically. Testing begins at the module level and work
towards the integration of entire computers based system. Nothing is
complete without testing, as it is vital success of the system.
System Testing Process: System Testing is performed in the following steps:

Test Environment Setup: Create testing environment for the better quality
testing.

Create Test Case: Generate test case for the testing process.

Create Test Data: Generate the data that is to be tested.

Execute Test Case: After the generation of the test case and the test data,
test cases are executed.

Defect Reporting: Defects in the system are detected.

Regression Testing: It is carried out to test the side effects of the testing
process.

Log Defects: Defects are fixed in this step.

Retest: If the test is not successful then again test is performed.


Unit Testing:
Unit testing focuses on the verification of smallest unit of software design
of the module. To check whether each module in the software works
properly so that it gives desired outputs to the given inputs.

All validations and conditions are tested in the module level in unit test.

In our system, Unit testing has been successfully handled. The test data
was given to each module in all respects and have got desired output. Each
module has been found working properly.

Black Box Testing:


Black Box Testing methods focus on the functional requirements of the
software.

This testing attempts to find errors in the following categories: incorrect or


missing functions, interface errors, errors in data structure or external
database access, performance errors and initialization errors and termination
errors.

In our system, Black Box testing has been successfully handled. The test
input data was given has got desired output.
User Acceptance Testing:

The performance of user interactive testing is actually the user show. The
user gives live data and checks whether software is giving specified outputs.

Implementation:

Implementation is the phase where the system goes for actual


functioning. Hence in this phase one has to be cautious because all the
efforts undertaken during the project will be fruitful only if the software is
properly implemented according to the plans made.

The implementation phase is less creative than system design. It is


primarily concerned with user training, site preparation and file
conversion. Depending on the nature of the system, extensive user
training may be required.
CONCLUSION

 Our project is only a humble venture to satisfy the needs to manage


their project work. Several user friendly coding have also adopted.
This package shall prove to be a powerful package in satisfying all
the requirements of the system. The objective of software planning
is to provide a frame work that enables the manger to make
reasonable estimates made within a limited time frame at the
beginning of the software project and should be updated regularly
as the project progresses.
BIBLIOGRAPHY

Google for problem solving

https://www.tutorialspoint.com/vb.net/

http://www.javatpoint.com/vb.net-tutorial

http://www.tutorialspoint.com/mysql/
THANK YOU

You might also like