2. CERTIFICATE
This is to certify that the project work entitled “AIR TICKET RESERVATION” in C++ which is being submitted by me in partial fulfillment of the requirement for award of the B. Tech in the directorate of Uttar Pradesh Technical University, Lucknow is an authentic work carried out by me under the supervision and guidance of Er. Nidhi Tyagi. The matter embedded in this project work has not been submitted earlier for the award.
Er. Deepak Singh Rathour
S.I.T.E. (Meerut)
(Signature of lecturer) 

3. Declaration by the student
We hereby declare that the project entitled “ AIR TICKET RESERVATION” in C++,has been done by us and is submitted under the summer training for B.Tech (VI th sem),Subharti Insitute Of Technology And Engineering, Meerut.
All the information, facts & figures used in different parts of Project Development are gathered by me. It is first hand in nature and is based on my intensive research. Any resemb -lance from existing work is purely coincident in nature.
Siddharth Srivastava
B.Tech (7th sem)
Batch ( )
S.I.T.E., Meerut 

4. ACKNOWLEDGEMENT
We wish to avail this opportunity to express my sincere gratitude, deepest sense of indebtness to my lecturer Er. Nidhi Tyagi for his continuous valuable guidance, constant encouragement and meticulous help during the period of my project work.
Last, but not the least ,I express my sincere and profound gratitude to my parents for their encouragement, help and support in the project. I am also thankful to our friends who have helped me during this period.    Siddharth Srivastava

5. INDEX TITLE OF PROJECT INTRODUCTION OBJECTIVES PROJECT CATEGORY SDLC
TITLE OF PROJECT
INTRODUCTION
OBJECTIVES
PROJECT CATEGORY
SDLC
INPUT MODULES
DATA FLOW IN THE PROJECT
DATA STRUCTURES
8.1. DATA FLOW DIAGRAM
8.2. ENTITY RELATIOSHIP DIAGRAM
TOOLS AND ENVIRONMENT
HARDWARE AND SOFTWARE SPECIFICATIONS
11. OUTPUT OF THE PROJECT 
12. FUTURE SCOPE
13. FURTHER ENHANCEMENTS
14. BIBLIOGRAPHY
15. GLOSSARY    

6. TITLE OF PROJECT The title of the project is ‘Air Ticket Reservation’.
Guide: Er. Deepak Singh Rathour
Made By: Siddharth Srivstava
( ) 

7. OBJECTIVES Air ticket booking Ticket cancellation
Passenger’s record can be checked.
Enquiring can be done.
List of passengers can be shown.

8. . SYSTEM DEVELOPMENT LIFE CYCLE
SYSTEM ANALYSIS
Identification Of The Need
The success of a system depends largely on how accurately a problem is defined, thoroughly investigated, & properly carried out to the choice of solution. Analysis is a phase in which the requirements for a new system are identified. System analysis is a detailed study of the various operations performed by a system & their relationships within & outside of the system. The question is: what must be done to solve the problem?  During analysis data are collected on the available files, decision points & transaction handle by the parent system. Data flow diagram, interviews, onsite observation, questionnaires are used as a logical system model & tools to perform the analysis.
Studied strengths & weaknesses of the current system.
Determined “what” must be done to solve the problem.
Prepared a functional specifications document.

9. FEASIBILITY STUDY
The result of the feasibility study is a formal proposal. This is simply a report a formal document detailing the nature and
scope of the proposed solution. The proposal summarized what          is known and what is going on to be done. Three key considerations are involved in the feasibility analysis:
1. Economic,
2. Technical,
3. Operational.    Economic Feasibility: Economist analysis is the most frequent   used method for evaluating the effectiveness of a candidate system. More commonly known as cost/benefit analysis, the procedure is to be determining the benefits and saving that are expecting from the candidate system and compare them with costs.

10. Technical Feasibility: Technical feasibility centers, around the existing computer system hardware, software etc. and to what extent it can support the proposed edition. If the budget is a serious constrains then the project is judge not feasible.
Operational Feasibility: It is common knowledge that computer installations have something to do with turnover, transfers, retraining and changes in employee job status.
Therefore, it is understandable that the introduction of a candidate system requires special efforts to educate, sell, and train the staff on new ways of conducting business.   

11. System Design
The most creative & challenging phase of the system life cycle
is system design. The term design describes a final system & the process by which it is developed. It refers to the technical
specification that will be applied in implementing the candidate system.
The First step is to determine how the output is to be produced   & in what format. Samples for the output (& input) are also
presented.
The Second step is input data & master files (data base) have to be designed to meet the requirements of the proposed output. The operational (processing) phases are handled through program construction & testing including a list of the programs needed to meet the system’s objective & complete documentation. Finally, details related to justification of the system on the user & the organization are documented & evaluated by management as a step toward implementation.
To design the system we must note the following points:
To identify the Software Components which satisfy the system Design.
To design & document the Software Components & the linkage.
In this component the software components & relevant interfaces are to be identified.

12. Identify Relevant Interfaces
Interaction with existing internal systems.
Interactions with existing external systems.
Network connections.
Standard Input Formats.
Standard Output Format
IMPLEMENTATION
Implementation is the process of having systems personnel check out & put new equipment into use, train users, install the new application & construct any files of data needed to use it.
This phase is less creative then than system design. Depending on the size of the organization that will be involved in using the application & the risk involved in its use, system developers may choose to test the operation in only one area of the firm with only one or two persons. Sometimes, they will run both old & new system in parallel way to compare the results. In still other situations, system developers stop using the old system one day & start using the new one the next.
VALIDATION
Software testing is one element of a broader topic that is often referred to as Verification & Validation (V & V). Verification refers to the set of activities that ensure that software correctly implements a specific function. Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements. Boehm states this in another way:

13. Verification: “Are we building the product right?”
Validation: “Are we building the right product?”
The definition of V & V encompasses many of the activities that we have referred to as Software Quality Assurance. Verification & Validation encompasses a wide array of SQA activities that include formal technical reviews, quality & configuration audits,   performance monitoring, simulation, feasibility study, documentation review, database review, algorithm analysis, development testing, qualification testing, & installation testing. Although testing plays an extremely important role in V&V, many other activities are also necessary. Testing does provide the last bastion from which quality can be assessed &, more pragmatically, errors can be uncovered. But testing should not be viewed as a safety net. As they say,  “You can’t test in quality. If it’s not there before you begin testing, it won’t be there when you’re finished testing”. Quality is
incorporated into software throughout the process of software engineering.

14. TESTING
Testing plays an important role in quality assurance of the software. Testing is a dynamic method for verification and validation. With the help of testing we observe the failure of the system in terms of logical and runtime errors.
As the goal of testing is to detect any errors in the program,
different flavors of testing are often used to test module or a      small collection modules and the focus is on detecting coding errors in modules. To accomplish this objective, two different categories of test case design techniques are used.
White box testing:
White box focuses on the program control structure. Test cases are derived to ensure that all statement in the program control
structure. Basis path testing, a white box testing techniques, makes use of program graph (or graph matrices) linearly independent test that will ensure coverage.
Black-box testing: The black-box testing is used to demonstrate that the software functions are operational, that input is properly produced, and that the integrity of external information is maintained. A black box test examines some fundamental aspect of the system with little or no regard for the internal logical structure of the software.

15. Testing Process MAINTENANCE
The maintenance of existing software can account for over 60 percent of all effort expended by a development organization, & the percentage continues to rise as more software is produced. Unlimited readers may ask why so much maintenance is required & why so much effort is expended. Much of the software we depend on today is on average 10 to 15 years old. Even when these programs were created using the best design & coding techniques known at the time & most were not, they were created when program size & storage space were principle concerns. They were then migrated to new platforms, adjusted for changes in machine & operating system technology & enhanced to meet new user needs all without enough regard to overall architecture.
Software maintenance is, of course, far more than “fixing mistakes”. We may define maintenance by describing four activities that are undertaken after a program is released for use. There are four different maintenance activities: collective maintenance, adaptive maintenance, preventive maintenance or enhancement, & preventive maintenance or reengineering. Only     about 20 percent of all maintenance work is spent “fixing mistakes”.  The  remaining  80  percent  is spent adapting existing systems to changes in their external environment, making enhancements requested by users, & reengineering an application for   future use..   

16. Data Requirements
Reservation requires as input details of the person who wants to travel through plane.
Once input is complete, a summary of input information is provided before the saving of the data file, and the subsequent booking is done.

17. DATA FLOW IN THE PROJECT
The data flow within the database components is explained below through some examples.
The main entities in the model are: Flight, Route, Ticket and Scheme.
1. An example of data flow between these entities is as soon as a user makes a query for flights running between two cities on a certain date. 
•The Route table is scanned in conjunction with the airport tables to get a listing of all the airports in the start and end cities (note that there can be multiple airports in a city).
•The flightroutescheme relationship is checked for appropriate dates.
•Data about flight seat availability is retrieved by a loop in the C++ program. This is done to take into account multiple stops.       
•Roundtrip requests are correctly managed to match start and end points. Steps above are repeated to get data regarding the return flight.

18. The other major part of the model is the interrelation between profiles and ticket bookings. Data flow occurs between the
profiles, passenger tickets and the flight and route entities      through the fligh troute ticket relation.
An example of the data flow is as follows:
A person logged in wants to retrieve info about all tickets booked by him:
•The booking profile is scanned to find the list of all ticket ids.
•The ticket ids are used to find the flightids and routeids through the flightroutescheme relation.
•The route id is then used to scan the route table and get the start and end airport ids.
•This is used to scan the airport tables to find the cities. 
•The times of arrival/departure are found from the flightroutescheme table.
Another important part of the project was to ensure consistent booking across multiple stops.

19. . Transactions and sample queries:
Some of the functionalities are:
•Any person can query for flight scheduled according to specified conditions.
•A Person can book/cancel a ticket only after he logs in.
•A user can sign up for a profile if he doesnt have one already.     
The user has options to
1.Book tickets
2.Edit Profile information
3.Cancellation of tickets
4.View all current tickets booked by him
5.Exit    •A person can get all information regarding a ticket if he keys in the ticketID.
•A person can get all information about a flight if he keys in the flightID.
•A person can get the schedule of all flights running for the next 20 days.  

20. DATA STRUCTURES

21. 10. HARDWARE AND SOFTWARE SPECIFICATIONS Hardware:
9. TOOLS AND ENVIRONMENT
Tools used are:
Back-End: File Handling
Front-End: C++
Environment:
Operating System : Windows xp
10. HARDWARE AND SOFTWARE SPECIFICATIONS
Hardware:
CPU : Intel P II and compatible
Memory 128MB
Software:
O.S :   Windows XP
Front End : C++
Back-End : File Handling
Language : C++

22. OUTPUT OF THE PROJECT
The output of the project will be in the form of various reports telling us about:
the flights available.
the source and destination.
the fair of economic and executive class.
the record of passengers.
the enquiry to be done.
the list of passengers.

23. Form1:  MAIN FORM 

24. Form2:  LIST OF FLIGHTS   

25. Form3: CANCELLATION FORM

26. Form4: EDITTING PASSENGER’S RECORD

27. Form5: TICKET INFORMATION

28. Form6: ENQUIRY OF FLIGHTS

29. Form7: LIST OF PASSENGERS IN PARTICULAR FLIGHT

30. FURTURE SCOPE
Our project can be used in future as a part of a large scale  Air Ticket Rservation.  
FURTHER ENHANCEMENTS
The system can be further enhanced to a web based application. 

31. 14.  BIBLIOGRAPHY 
Elias M. Awad , System Analysis And Design ,Galgotia Publication(P) Ltd. New Delhi (2000).
Igor Hawryszkiewych, Introduction To System Analysis And Design , Fourth Edition , Prentice Hall Of India Private Limited, New Delhi(2000).
Roger S. Pressman ,Software Engineering – A Practitioner’s Approach, Fifth Edition, McGraw Hill International Edition, New Delhi.
Object Oriented Programming wih C++ (Third Edition) by E. Balagurusamy
Let Us C++ by Yashwant Kanitkar
Computer science C++ by Sumita Arora, Gautam Sarkar
Complete reference of  C++

32. . GLOSSARY
Analysis               Breaking a problem into successively      manageable parts for individual study.
Attribute             A data item that characterizes an object.
Cost/Benefit       Purpose of comparing projects savings benefits to projected costs to decide whether a system’s change is justified.
Database          Store of integrated data capable of being directly addressed for multiple users; it is organized so that various files can be accessed through a single reference based on the relationship among records in the file rather than the physical location.
DBMS               The Software that determines how data must be structured to produce the user’s view; & maintain & update the system.
Data flow           A movement of data in a system from a point of origin to specific destinations – indicated by a line & arrow.
Data-Security Protection of data from loss, disclosure,  modification or destruction.
Data-Structure A logically related set of data that can be                   decomposed into lower level data elements; a group of  data handled as a unit. 

33. Design        The process of developing the technical and operational specification of candidate system for implementation.
Feasibility     The procedure that identifies, describes and evaluates the candidate system and selects the best system for the job.
File                Collection of the related records organized for a  particular purpose; also called a data set.
Flow Chart    Graphic picture of logical steps and sequence                                                  involved in a procedure or a program.
Form                    A physical carrier of data of information.
Gantt chart     A static system model used for scheduling; portrays output performance against time.
Implementation  In system development- a phase that focuses on user training, site preparation & file conversion for installing a candidate system.

34. Maintenance         Restoring to its original condition.
Normalization  A process of replacing a given file with its logical equivalent; the   object is to derive simple files with no redundant elements.
Operating         In database machine based software that facilitates the availability of information or reports through the DBMS.
Password           Identity authenticator a key that allows access to a program system or procedure.
PERT               Program Evaluation & Review Techniques. A flow system model used to manipulate various values as a basis for determining the critical path to interpret these relationships & to relate them back to the real world as a control technique.
Record               A collection of aggregates or related items of data treated as a unit.

35. Source Code       Procedure or format that allows enhancements on a software package.
System                Regular or orderly arrangement of components or parts in a connected & interrelated series or whole; a group of components necessary to some operation.
System Design    A detailed concentration on the technical & other specifications that will make the new system operational.
SDLC           (System Development Life Cycle) A structured sequence of phases for implementing an information system.

36. System Testing 
Testing the whole system by the user after major      program and subsystem have been tested.
Unit Testing 
  Testing that changes made in new or existing system.
Validations
  Checking the quality of software in both simulated
& live environments