Download Airline Reservation System: A Project Report for BCA Students and more Study Guides, Projects, Research Applications of Computer Sciences in PDF only on Docsity!
AIRLINE RESERVATION SYSTEM
Project Report
For the partial fulfillment of the degree in
BACHELOR OF COMPUTER APPLICATION (BCA)
PROJECT GUIDE: Mr.Ankush Joshi SUBMITTED BY: Sanjana Agarwal Saloni Lohiya Sachin Padhlani Rohit Singh Ravi Negi
Faculty of Computer Science Applications
AMRAPALI GROUP OF INSTITUTE, HALDWANI
CERTIFICATE
This is to certify that the project entitled “ Airline Reservation System ” has been developed by BCA students of Amrapali Group of Institute, Haldwani towards partial fulfillment of the requirements for the award of the degree of Bachelor of Computer Science is a genuine record of the work carried out by Him/her under My Supervision and Guidance and the project report is the original work of student. She/he has worked on the project Airline Reservation System. She/he has used PHP, CSS, HTML, JAVASCRIPT and Xampp as Database for the project. His/her work is satisfactory. I wish him/her all the best for his bright future.
Date: 05/06/2017 Signature of Guide Place:Haldwani Mr.Ankush Joshi
DECLARATION
We hereby declare that the work in the project report entitled “ Airline Reservation System “ Amrapali Group Of Institute , Haldwani for the award of degree of “ BCA ” is an authentic record of my work carried out during the sixth semester Third year, 2017 under the supervision of Mr.Ankush Joshi .The matter embodied in this project report has not been submitted elsewhere by anybody for the award of any other degree/diploma.
NAME UNIVERSITYROLL NO CLASS
SanjanaAgarwal 1461330107 BCA 6sem, 3 year rd Saloni Lohiya 1461330106 BCA 6sem, 3rd year Sachin Padhlani 1461330060 BCA 6sem, 3rd year Rohit Singh 1461330059 BCA 6sem, 3 year rd Ravi Negi 1461330058 BCA 6sem, 3rd year
Software Requirement Specification
- Preface(Introduction)................................................................................. Particulars Page Nos.
- 1.1. Project Overview.................................................................................
- 1.2. Project Description ………………………………………………….
- 1.3. Definitions, Acronyms, and Abbreviations.......................................
- 1.4. References..........................................................................................
- Problem Definition....................................................................................
- 2.1. Existing System..................................................................................
- 2.2. Proposed System…………………………………………………....
- 2.3. Product Function…………………………………………………....
- 2.4. User Characteristics…………………………………………………
- 2.5. Constraints…………………………………………………………..
- 2.6. System Study………………………………………………………..
- 2.7. Assumptions and dependencies……………………………………..
- Feasibility Study…………………………………………………………
- 3.1. Technical Feasibility………………………………………………....
- 3.2. Operational Feasibility……………………………………………….
- 3.3. Economic Feasibility…………………………………………………
- 3.4. Interfaces…………………………………………………………….
- 3.5. Hardware Requirements……………………………………………..
- 3.6. Software Requirements……………………………………………....
- System Analysis…………………………………………………………...
- 4.1. Software Requirement Specification…………………………………
- 4.2. Communications Interfaces………………………………….............
- 4.3. Memory Constraints...........................................................................
- 4.4. Operations..........................................................................................
- 4.5. Site Adaptation Requirements............................................................
- 4.6. Functional Requirements....................................................................
- 4.6.1. Performance Requirements......................................................
- 4.6.2. Assumptions and Dependencies..............................................
- System Design...........................................................................................
- 5.1. Module Description............................................................................
- 5.2. Software System Attributes...............................................................
- 5.2.1. Reliability.................................................................................
- 5.2.2. Availability...............................................................................
- 5.2.3. Security....................................................................................
- 5.2.4. Maintainability.........................................................................
- 5.2.5. Portability.................................................................................
- 5.3. Organizing the specific Requirements.................................................
- 5.3.1. System Mode............................................................................
- 5.3.2. User Class.................................................................................
- 5.3.3. Objects.....................................................................................
- 5.3.4. Features....................................................................................
- 5.3.5. Stimulus....................................................................................
- 5.3.6. Response...................................................................................
- 5.3.7. Functional Hierarchy.................................................................
- Database Design.........................................................................................
- Designing forms………………………………………………………….
- Coding……………………………………………………………………
- System Testing……………………………………………………………8
- 9.1. Testing Methods……………………………………………………..8
- 9.2. Unit Testing, Class Testing………………………………………….
- 9.3. Test Cases…………………………………………………………...
- Conclusion……………………………………………………………….
- Future Scope……………………………………………………………..
PREFACE
With the fast development of computer technology, the software projects are growing and complexity. Software experts have recently sought to develop a more systematic and formal approach in the design, development and implementation of their software. This new approach has become necessary because the traditional methods of system development often yielded software characterized by late diversity, costliness, unreliability, and non-maintainability and nonuse ability.
In this new age of computing everything has been computerized, so how can we become isolate and untouched from this environment. That’s why keeping this thing in mind and an opportunity or probably a creativity to do such a task different and unique from others, we thought a way to develop this software.
This project has been developed in aim to aid and computerize an flight booking. While keeping in mind the user will find an easy and friendlier user interface to perform his task. The software has been made so user friendly that any person can use it easily without having any computer experience.
The entire project has been developed keeping in view of the distributed client server computing technology, in mind. The specification has been normalized up to 2NF to eliminate all the anomalies that may arise due to the database transaction that are executed by the general users and the organizational administration. The user interfaces are browser specific to give distributed accessibility for the overall system. The internal database has been selected as Database Mysql.
The Airline Reservation System project is an implementation of a general Airline
Ticketing website like Orbitz, which helps the customers to search the availability and prices of various airline tickets, along with the different packages available with the reservations.
This project also covers various features like online registration of the users, modifying the details of the website by the management staff or administrator of the website, by adding, deleting or modifying the customer details, flights or packages information. In general, this website would be designed to perform like any other airline ticketing website available online.
1.3. Definitions, Acronyms, and Abbreviations
Personal Details: Details of passengers such as user id, phone number, address, passport no, e-mail address etc.
Contact Details : Details of contact associated with the passenger.
SRS : System Requirement Specification
WWW : World Wide Web
MySQL: is a RDBMS based on SQL which is used for adding, removing, and modifying information in the database.
RDBMS: Relational Database Management System
HTML : Hypertext Markup Language
PHP : Hypertext Preprocessor
CSS: Cascading Style Sheet
HTTP : Hypertext Transfer Protocol
1.4. References
Software Requirement Specifications from Internet. Software Requirement Specifications, Airline Reservation System. IEEE (Institute of Electrical and Electronics Engineers) Guide to Software Requirements Specifications. www.slideshare.com www.google.com www.wikipedia.com www.project-airline-system-basics.com HTML for the World Wide Web with XHTML and CSS Guide, Fifth Edition IEEE Computer Society, 1998.
2.2. Proposed System:
The Proposed system ensures the complete freedom for users, where user at his own system can logon to this website and can book his ticket. Our proposed system allows only registered users to book the tickets, view timings and cancel their tickets.
In this Proposal the entire work is done on online and ticket with id is also provided for passengers as a print document. Here passengers can send their queries and suggestions through a feedback form.
To debug the existing system, remove procedures those cause data redundancy, make navigational sequence proper To build strong password mechanism.
Advantages:
User friendliness provided in the application with various controls. The system makes the overall project management much easier and flexible. It provides high level of security with different level of authentication.
2.3. Product Functions
The website will allow access only to authorized users with specific roles (Administrator- maintains the website, Company-Register the passengers, Passenger- Fills the details).
Following are the System Functions:
Passenger role:
On the register form, passenger should enter all their detail such as their name, passport number, Email and contact number.
Administration role
The system administrator must be able to: add, update and modify flights and view the customer details.
2.4. User Characteristics
End Users
All specific knowledge or skills are required from the feeder.
Educational level: Users should be comfortable with the English language. Experience: Users should have prior information regarding the online booking. Skills: Users should have basic knowledge and should be comfortable
Administrator
Administrator must be capable to manage user rights.
This system will not take care of any virus problem, which might occur either on the Client or the server system. Avoiding the use of pirated software and ensuring that floppies and other removable media are scanned for viruses before use could minimize the possibility of viral infection.
2.5. Constraints
The Information of all users, subjects and allocations must be stored in a database that is accessible by every connected system. MySQL used for database.
Users may access from any system connected to the online database. Users must have their correct usernames and passwords to enter into their accounts.
Feasibility Study
Preliminary investigation examines project feasibility. The likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:
Technical Feasibility Operation Feasibility Economic Feasibility
3.1. Technical Feasibility
The technical issue usually raised during the feasibility stage of the investigation includes the following:
Does the necessary technology exist to do what is suggested? Does the proposed equipment have the technical capacity to hold the data required to use the new system? Will the proposed system provide adequate response to inquiries, regardless of the number or location of users? Can the system be upgraded if developed? Are there technical guarantees of accuracy, reliability, ease of access and data security? Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’. The current system developed is technically feasible. It is a
web based user interface for audit workflow at NIC-CSD. Thus, it provides an easy access to the users.
The database’s purpose is to create, establish and maintain a workflow among various entities to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security.
The software and hardware requirements for the development of this project are not many and are already available in-house at NIC or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the
3.2. Operational Feasibility
Proposed projects are beneficial only if they can be turned out into information system. That will meet the organization’s operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following:
Is there sufficient support for the management from the users? Will the system be used and work properly if it is being developed and implemented? Will there be any resistance from the user that will undermine the possible application benefits? This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into
MY-SQL (BACKEND)
MySQL in July 2013, it was the world's second most widely used RDBMS, and the most widely used open-source client server model RDBMS. It is named after co- founder Michael Widenius's. The SQL abbreviation stands for Structured Query Language. The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements.
Apache
The Apache HTTP Server is web server software notable for playing a key role in the initial growth of the World Wide Web. In 2009 it became the first web server software to surpass the 100 million web site milestone. Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation. Since April 1996 Apache has been the most popular HTTP server software in use.
XAMPP
XAMPP is a small and light Apache distribution containing the most common web development technologies in a single package. Its contents, small size, and portability make it the ideal tool for students developing and testing applications in PHP and MySQL. XAMPP is available as a free download in two specific packages: full and lite. While the full package download provides a wide array of development tools, XAMPP Lite contains the necessary technologies that meet the Ontario Skills Competition standard.
System Analysis
System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system? What must be done to solve the problem? Analysis begins when a user or manager begins a study of the program using existing system.
4.1. Software Requirement Specification (SRS)
The software, Site Explorer is designed for management of web sites from a remote location. This section provides software requirements to a level of detail sufficient to enable designers to design the system an testers to test the system.
This section contains all of the functional and quality requirements of the system. It gives a detailed description of the system and all its features.
Introduction
Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system.
Scope: This Document plays a vital role in the development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
Developer’s responsibilities overview:
The developer is responsible for:
Developing the system, which meets the SRS and solving all the requirements of the system?
