AIRLINE RESERVATION SYSTEM

Submitted to:
Ms. Dimple chawla Assistant Professor

Submited by:
Deepika (09212304412) Deepti.K(09612304412) Surjeet Kaur(03312304412)

CONTENTS
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Covering Page of Project Report A Level Project Certificate from Accredited Institute Organization To Whom It May Concern Declaration Acknowledgement Introduction Purpose Scope Objective A Complete Analysis and Design Reports Technical Feasibility Economical Feasibility Operational Feasibility Risk Analysis & Management Advantages System specifications

13. 14. 15.

16.

System Requirements *Requirement analysis 1 *Requirement analysis 2 *Srs Hardware Requirements Introduction to Programming Language Introduction to the C++ Language Architectural design Data Dictionaries Flow Chart Context Diagram Output Screen Coding Biblography

17. 18. 19. 20. 21 22 23 24 25 26.

Project Report
Executive Director, DOEACC Society, 6,CGO Complex Lodhi Road New Delhi-110003 Sir, I am submitting my A Level Project for evaluation. Details of my Registration and postal address, etc is as under: Regn. No: 461707 Name: Level A

MANJULA KINDRA

Fathers Name: SH. SHYAM SUNDER KINDRA Address: (a) Residential Address: 6/629,SANT COLONY RAILWAY ROAD BAHADURGARH HARYANA TELE. NO :- 01276 -394227

E-mail Address : [email protected]

AIRLINE RESERVATION SYSTEM ORGANIZATION

The Organization under which AIRLINE RESERVATION SYSTEM is developed, at MAHAN(DELHI), the registered instituted. Under this center all types of software are developed, like Web site development, Application in visual Basic, Application in Oracle with developer 2000, Application in power Building in Visual C++, C, C++, FoxPro & more.

MAHAN COMPUTER SERVICES(India)Ltd. GN-12,shivaji enclave,near shivaji college New delhi 110027

Teleno: 2591683

TO WHOM IT MAY CONCERN

It is to state that the student Manjula kindra, Reg No 461707 Course A Level has successfully completed his project titled Airline Reservation System,at MAHAN, NEWDELHI, under my guidance. With the best of my knowledge regarding the development of this project, it is being done for the first time by the student and I can assure the concerned authorities that it is the original work of the student and in no way is being copied from anywhere or submitted to any other University or so for the completion of any course of study.

Signature Of the Student Date:

Signature Of Project Guide Date:

DECLARATION
I (Manjula Kindra A level Reg. no - 461707) declare that the presented work (project on AIRLINE RESERVATION SYSTEM) is an original on and has not been submitted earlier to DOEACC Society or to the any other institution for fulfillment oft he requirement of any course of study.

Signature of student: Date :

ACKNOWLEDGEMENT
When a person is doing some serious work where a lot of help from a people concerning is needed, one feel specially obliged towards them. Life of any human being is full of interactions. This project report has come to existence with great labour and help from the university. In the entire assignment involved activities full of challenges. My heartfelt thanks goes to honorable teachers and guides whose valuable guidance and knowledge bring this project in this in this form. I am also really very thankful to all staffs and friends at MAHAN(NEW DELHI),, who extended co-operation towards the preparation of this project report.

INTRODUCTION
This project develop a user friendly AIR RESERVATION SYSTEM that performs the following operations like:

Reservation. Cancellation. Enquiry of the flights. List of passangers etc.

PURPOSE OF THE PROJECT

The purpose of the document is to describe all the valid requirements for the projected automated system for air reservation. It also describes the various limitations & assumptions for the system. It explores the various intricacies of this softwareengineering project.

SCOPE OF THE PROJECT

This document describes the requirement of the system. It is meant for the use of developers in the basic context. But in the larger context, it is an insight into the system and will also validate the final delivered system. Any changes made to the requirements in the future will have to go through a formal change approval. The developers in this case are wholly responsible for clarifications, where necessary, and will not make any alteration without a valid person.

OBJECTIVES OF THE SYSTEM

The objective of the project is to reserve the seats for the passengers as per their convenience and also make them able to cancel the reserved seats. According to the passenger applications, it will perform the following functions: It will display the flights schedule in which passenger can reserve the seats or cancel reservation. It will reserve the seats according to different flight fairs. It will display the passenger list of different flights. It will provide the enquiry facility to the passengers. It will display the full information about the passengers who have reserve a seat in the flight.

Justification For Choosing The Preferred Alternative And Its Economic, Technical & Operation Benefits

* *

After initial study it has been found that the system is feasible. For the feasibility of the project following points has been considered.

1. Technical Feasibility: The system is technically feasible as the AIRLINE RESERVATION SYSTEM has all the required software & hardware equipment. For the development they have all the required software like Windows 98, Window NT etc. While the machine on which the project is being developed has the following configurations: * * * * * Pentium IV 2.4 GHz 128 M.B RAM 40 G.B Hard Disk A Color Monitor (14) And all the other necessary equipment.

2. Economical Feasibility : The system is also economically feasible. I think it does not matter as the proposed system has many benefits. Specially intangibles benefits like passangers satisfaction, reducing repetitive works

for operator, decision support for management with enquiry reports, etc. And no doubt, these intangible benefits matter more than tangible assets specially when customer service is concerned.The only major tangible cost also does not matter because center can utilize the software in future by adding more & more feature to it. After fully analyzing the economical feasibility it has been found that benefits easily outweigh the all costs involved for system generation & system running. 3. Operational Feasibility : After carefully considering all the operational aspects it has been found that the system is operationally feasible, too, as the project is being supported by the management as well ass the user. Moreover, this system is also not causing any harm, as it is not going to Produce poorer reports Make slow performance of individual or system Loose access to information Loose control from system The system will also, off course, leave a better impact on customer and other concerned people and hence it is operationally feasible.

Risk Analysis And Management

Risk is defined as an exposure to the chance of injury or loss. A risk is a potential problem it might happen, it might not. In terms of Software projects Risk implies that there is an adverse effect on cost, quality or schedule.Every one associated with the software has responsibility of managing the risk. That is if everyone participated and paid close attention to all the details during the early phase of the software development many risk can be avoided. Software development can avoid having risk by doublechecking their schedule, product size, estimates regarding costs of the development etc.Customer can help avoid risk by providing all necessary software information during the early phase of the development.( to be self analyzed here) Software development team can avoid risk by getting all the details of the equipment that are provided or are accessible to them. Client can avoid risk by making all necessary business changes before initiating request for the software.

PROACTIVE RISK STRATEGY It begins long before technical work is initiated & it's primary objective is to avoid risk & manage it in case the risk becomes a reality.

Potential Risks are identified Their probability & impact are assessed Risks are ranked by importance A plan is established for managing the risk A contingency plan is developed to respond in case the risk becomes a reality.

RISK IDENTIFICATION We used the following risk item checklist to help in identifying the risks:

Product Size: This risk involves misjudgment on behalf of the customer and also the software development team. If the customer fails to provide the proper size of the product that is to be developed it will cause major problems for the completion of the project. If software development team misjudges the size and scope of the project, team may be too small or large for the project thus spending too much money on project or not finishing project at all because of shortage of finances. The size of this product is moderate. Hence any change incorporated needs to be tested intensively. Its overall impact on the whole software needs to be taken into account.

Customer Characteristics: The user must be an expert. So this software must provide for interactive, user-friendly interface with special features for an expert. Also there must be proper communication between the customer and the developer so that requirements are specified clearly and completely.

Process Definition: Process risk involves risks regarding product quality. If the product developed does not meet the standards set by the customer or the development team it is a failure. This can happen because of the customers failure to describe the true business need or the failure of the software development team to understand the project and than to use proper equipment and employees to finish the project. Selected Process Model must be followed properlyso that good quality software is delivered on time.

Development Environment: If client fails to provide al the necessary equipment for the development and execution of the software this will cause the software to become a failure. Ill be using Turbo C++ to develop this software, there is a great familiarity with working on this language.

Technology to be built: Technology risk involves of using technology that already is or is soon to be obsolete in development of the software. Such software will only be functional for short period of time thus taking away resources

from the customer. Technology is not very new; we are trying to enhance it. Moreover since software similar to each module is present in the Bank, we can compare each module.

Staff size and experience: This risk is totally dependent on the ability, experience and willingness of the software development team members to create the working product. If the team members are not experience enough to use the application necessary to develop the software it will keep pushing the development dates until its too late to save the project. I have adequate time to develop the software, but lack the experience to develop it.

ADVANTAGES OF THE PROJECT

This system is more convenient for both passengers & the airways staff members than the conventional manual system. It provides easy, fast & accurate retrieval of the information. Its efficiency in both space & time is better than the conventional system. Following are the advantages of the system: It contains full information about the flights. It does not require manual processing of the transactions.

The staff crew is reduced due to the automated transactions & reduced number of booking on other means. Suiting to the future needs and requirement, the system can be scaled and enhanced. Reserving and cancellation of seats in the flights are very easy for the passengers and staff members as well.

SYSTEM SPECIFICATION
We have used the following .DAT files to fulfill the requirement of the project.
1. TICKET .DAT FILE: - This file is used to perform the following functions. This file is used to add records of various flights for

which tickets are to be reserved by passengers. This file stores the list of various flights for enquiry purpose. This file is used to modify and cancel the ticket. This file is used to delete the records of various flights.

2. PASSENGER .DAT FILE: - This file is used to perform the following

functions. This file is used to store the information about the passengers who reserves a seat in any flight. This file is used to display the list of passengers in a given flight. This file is used to display information about the passengers for the given ticket number. This file is used to delete the record of passenger for the given flight number or given ticket number.
3. TEMP .DAT FILE:- This file is used to perform the following functions.

This file is used to store the ticket records temporarily for deletion

purpose.

This file is used to store the passengers record temporarily for deletion purpose.

SYSTEM REQUIREMENT

Airline management project is a user input requirement project. In this the user has to input some data to get the output or some information. User has to input the code according to which he/she will get the desired output. This project has made different .DAT files according to which it will respond. Following block diagram depicts the user input design of the air reservation project.

Input

Response

User

System

User

REQUIREMENT ANALYSIS -1
It is done to take a deeper look at the softwares role-to understand the specific requirements that must be achieved to build high quality software.It is done in the following steps:1.Data Requirements are identified 2.Functional Requirements are identified 3.Behavioural requirements are identified Requirements are refined and analysed to assess their clarity,completeness and consistency. Why is it important?

If we dont analyse,its highly likely that well build a very elegant software solution that solves the wrong problem.The result is wasted time and money,personal frustration and unhappy customers. What is the work product formed? An effective representation of the software must be produced as a consequence of requirements analysis Software requirements analysis is broken down into five areas of effort: 1.Problem recognition 2.Evaluation and synthesis 3.Modeling 4.Specification 5.Review PROBLEM RECOGNITION Goal:- Recognition of the basic problem elements as perceived by the customer/users. Problems identified in a old resrvation sysytem 1. Checking for availability of a flight was quite difficult. 2. Checking for number of seats available in flight. 3. Before cancellation of a ticket,We have to check all the passangers records whether anyone has reservecd it or not. It was time consuming and cumbersome. Problem evaluation It is the next major area of effort for analysis.The analyst must define all externally observable data objects.Evaluate the flow and content of information,define and elaborate all software functions,understand software behaviour in the context of events that affect the system,establish system interface characteristics and uncover additional design constraints.

Once problems have been identified,the analyst determines what information is to be produced by the new system and what data will be provided to the system. . In the system to be developed we have the following inputs : 1. 2. 3. 4. 5. Passanger name/Code Passanger address Flight s.no Flight class Ticket no (necessary at time of cancellation)

We have the following outputs : 1. List of all passangers 2. List of all flights 3. Tells whether a passanger has record or not

SOLUTION SYNTHESIS Upon evaluating current problems and desired information(input and output),the analyst begins to synthesize one or more solutions.To begin,the data objects,processing functions and behaviour of the system are defined in detail. Data objects 1. Flights 2. Passanger Processing functions 1. To reserve a ticket for the passanger

2. To cancel a ticket for the passanger 3. To maintain the records of the passanger 4. To maintain the records of the flights Behaviour of the system 1. To reserve a ticket for a passager.The system asks for a passangers name ,passangers age,passangers addresss and passangers sex. 2. To cancel a ticket for the passanger.The system asks for the ticket number of the passanger. 3. To maintain the records of the filghts .The system asks for a flight serial number,flight number,flight route that is the starting and the destination point of the flight and about the flight fair that is by economy or executive class. 4. As per the record of passanger it will display passangers name,addresss,sex and age and the flight number of the passanger. 5. It displays the class of passanger by which he/she reserved a ticket by entering the ticket number.

REQUIREMENT ANALYSIS -2
Requirements Analysis is a software engineering task that bridges the gap between system level requirements engineering and software design.Requirements Engineering activities result in the specification of softwares operational characteristics ( functions, data and behavior ). It allows the software engineer to refine the software allocation and build models of the data, functional and behavioral domains that will be treated by the software.

Software Requirements analysis may be divided into five areas of effort : 1 Problem Recognition 2 Evaluation and Synthesis 3 Modeling 4 Specification 5 Review

PRODUCT REQUEST The customer requires a user-friendly software package with graphical user interface which will enable him to store information about his daily transactions, manage account creation and deletion request (for various types of accounts) and check the account status in a quick and efficient manner. The software also provides a password mechanism which prevents any undue data modification and to prevents any illegal access from intruders. Applications that may help ease load from the users mind. The application should comprise of different easy

to operate user screens for each module. Overall maintenance of entire data entries should be accurate and easily accessible.

FAST Facilitated Application Specification Technique was used to specify requirements in detail. The goal of FAST was to identify the problem, propose elements of the solution, negotiate different approaches, and specify a preliminary set of solution requirements in an environment that was conducive to the accomplishment of the goal. The customer and the developer justified the need that the software must be engineered. FAST resulted in the following Specifications

 List of objects Objects(Modules) that are part of the system and perform functions: Reservation of ticket Cancellation of ticket Enquiry about flights Passangers record

Objects that are used by the system: Data in the form of System Date and Time Operands & Operators

Information stored in the database (Internal File Handling).

Performance Criteria: Accuracy Fast Access to Database Speedy Calculations Complete and Concise Results Efficient User-Software Interface, hence provide for Graphical User Interface

Software Requirement Specification

Generally, the software Requirement Specification (SRS) is a document that completely describes what the proposed software should do without describing how the software will do it. The basic goal of the requirement phase is to produce the SRS, which describe the complete external behavior of the proposed software.There are three major parties interested in a new system; the client, the user, and the developer client, the users, and the developer.SRS is the medium through which the client and user needs are accurately specification; indeed SRS from the basis of software development.

HARDWARE AND SOFTWARE REQUIREMENTS

MINIMUM REQUIREMENTS Hardware Requirements o PC XT or 486 o 8 MB Ram o VGA/SVGA Monitor Software Requirements o Operating System DOS o Borland Turbo C++ Compiler 2.0 o BGI Graphics Driver

RECOMMENDED Hardware Requirements o Pentium or Higher o 64 MB Ram or Higher o 16 bit true Colour Monitor or Higher Software Requirements o Operating System Windows 98 or XP o Borland Turbo C++ Compiler 3.0 or higher. o BGI Graphics Driver

INTRODUCTION TO PROGRAMMING LANGUAGE

Programming Language: Programming Language, in computer science, artificial language used to write a sequence of instructions (a computer program) that can be run by a computer. Similar to natural languages, such as English, programming

languages have a vocabulary, grammar, and syntax. However, natural languages are not suited for programming computers because they are ambiguous, meaning that their vocabulary and grammatical structure may be interpreted in multiple ways. The languages used to program computers must have simple logical structures, and the rules for their grammar, spelling, and punctuation must be precise. Programming languages vary greatly in their sophistication and in their degree of versatility. Some programming languages are written to address a particular kind of computing problem or for use on a particular model of computer system. For instance, programming languages such as Fortran and COBOL were written to solve certain general types of programming problemsFortran for scientific applications, and COBOL for business applications. Although these languages were designed to address specific categories of computer problems, they are highly portable, meaning that they may be used to program many types of computers. Other languages, such as machine languages, are designed to be used by one specific model of computer system, or even by one specific computer in certain research applications. The most commonly used programming languages are highly portable and can be used to effectively solve diverse types of computing problems. Languages like C, C++,PASCAL, and BASIC fall into this category.

A Brief History Of C++

Bjarne Stroustrup at Bell Labs initially developed C++ during the early 1980's. It was designed to support the features of C such as efficiency and low-level support for system level coding. Added to this were features such as classes with inheritance and virtual functions, derived from the Simula67 language, and operator overloading, derived from Algol68. Don't worry about understanding all the terms just yet, they are explained in About's C++ tutorials. C++ is best described as a superset of C, with full support for object-oriented programming. This language is in wide spread use.

ARCHITECTURAL DESIGN
It represents the structure of the software system, the architectural style it will take, the data and program components their properties and interrelationships; that are required to build a computer-based system. Architectural style is a descriptive mechanism, which differentiates software from another. Depending on the requirements of software 2 different architectural styles are used:

1) Call and Return Architecture : This style enables a software designer to

achieve a program structure that is relatively easy to modify and scale. Main program / subprogram architecture decomposes function into a control hierarchy where a main program invokes a number of program components, which in turn may invoke still other components This is valid throughout the software and individually for applications which do not involve a database.
2) Data-Centered Architecture : The key concept behind this style is A

data store( e.g. a file or a database) resides at the center of this architecture and is accessed frequently by other components that update, add, cancel, or otherwise modify data within the store. We chose this style as our software has Applications Record Generation, Transaction - which focus on data stored in a database. MAPPING REQUIREMENTS INTO SOFTWARE ARCHITECTURE Transform Flow: Information enters the system along paths that transform external data into an internal form. These paths are identified as Incoming Flow. At the kernel of the software, a transition occurs. Incoming data are passed through a transform center and begin to move along paths that lead out of the software. This data constitutes outgoing flow. This sequential flow present in a segment of a data flow diagram is referred to as transform flow. Transaction Flow: When in a data flow diagram, a single data item called a transaction that triggers other data flows along one of many paths characterizes information flow, transaction flow is said to exist. Data moves along an incoming path, which converts external information into a transaction. The transaction is evaluated and based on its value; flow along one of many action paths is

initiated. The hub of information flow from which many action paths emanate is called a transaction center. Transform Mapping: It is a set of design steps that allows a DFD with transform flow characteristics to be mapped into a specific architectural style. Transaction Mapping: It is a set of design steps that allows a DFD with transaction flow characteristics to be mapped into a specific architectural style.

Data Dictionaries
list of Flights
Element name
1. Flight number 2. Flight serial number 3. Flights fare

Identifier
flight.no. s.no. fare

Data Type
alpha numeric numeric numeric

Format

4. Flights route

from to

character

List of Passangers
Element name
1. Passangers name 2. 3. 4. 5. 6. Passangers age Passangers sex Passangers address Flight number Ticket number

Identifier
name age sex address flight-no: ticket no

Data Type Format

character numeric character alpha numeric alpha numeric numeric

FLOW CHART OF AIRLINE RESERVATION SYSTEM

This is the main structure of the program Airline reservation..This ouputs shows us the information which we can reterive from this program after entering the choice,e.g.you can reserve or cancel the ticket or u can do enquiry about the flights or can do enquiry about the passangers but you have to enter the choice inenter the

choice column.So this output suggest thw whole processing of the program.

This output tell us about the procedure you have to follow for the reservation of the ticket.First you have to enter the s.no. of the flight that is by which flight you want to go after this you have to enter the class by which you want to go that is economic class or by executive class.

This output shows that we have to enter the name ,address,age and sex of the female for issuing the ticket.,After enterting the requirements we would be able to get a ticket.

This output shows the result as a Ticket issued.this is the ticket which we get.

This output tells us about the cancellation of the ticket.if u want to cancel your ticket you have to enter the ticket no ,which you want to cancel

After entering the ticket number the system will ask about the confirmation of the cancellation of the ticket . If you want to cancel the ticket press y otherwise press n

This ouput shows the cancellation of the ticket.It means that the ticket has been cancelled.

This output tell us abput the passangers info .,wat u want to know about passanger u can know by selecting a choice

This output will show you about the list of flights.

This output give you information about the passanger.you can know about the passanger by entering the flight number.

BIBLIOGRAPHY
Books Referred:

Concepts of C++ By: Robert Lafore Concepts of C++ By:G.S.Baluja Let us C By: Yashwant Kanitkar Let us C++ By: Yashwant Kanitkar Computer Science for Class XII By: Sumita Arora Data Structures By: R B Patel