CHAPTER 1

PROJECT DESCRIPTION
1.1 INTRODUCTION

The main purpose of this vision document is to list the requirements of the Airline
Reservation System project. This document also helps us to collect and analyze the ideas
gathered for the project. This vision document will be subject to change, if more requirements
are added to the project. This document is mainly prepared to set stage for the design phase of
the project. The document being prepared is the first version of vision document for the Airline
Reservation System project. C#.NET is a new technology which is being used a lot in the IT
field. My interest to learn this new technology has prompted me to take up this project, which
would set the stage for the applications I would be developing in the future. 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. 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. An airline reservation system (ARS) is part of the so-
called passenger service systems (PSS), which are applications supporting the direct contact with
the passenger. ARS eventually evolved into the computer reservations system (CRS). A
computer reservation system is used for the reservations of a particular airline and interfaces with
a global distribution system (GDS) which supports travel agencies and other distribution
channels in making reservations for most major airlines in a single system.
1.2 EXISTING SYSTEM

The created system will ease airline booking create account to the client, save details
about client, gives menu of trips and their costs and dates to be reserved and there is a customer
care services and details about the company and how to contact them. In few countries of a
person wants to book a flight ticket, he use to follow one of these things.

DISADVANTAGES

 Manually goes to the airport and book his ticket.

 Downloading the ticket form as paper document, filling it manually and submitting it at
airport.
 Fill the ticket form on system and get the print our as paper documents to submit it at
airport.
 Booking the ticket at some particular registered ticket counters in online
 Even above approaches make a ticket booking online, it was not completely done

1.3 PROPOSED SYSTEM

The proposed system ensures the complete freedom for user, where user at his own
system can logon to this website and can book his ticket. Our proposed system allows only
register users to book the tickets, view timings and cancel their tickets. In this proposal the
online work is done on online and ticket with id is also providing for passengers as a print
document. Here passengers can send their queries and suggestions through a form.

ADVANTAGES

 User friend lines 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.
1.3.1 HARDWARE REQUIREMENTS
 Processor : Dual core processor 2.6.0 GHz
 RAM : 1GB
 Hard disk : 160 GB
 Compact Disk : 650 MB
 Keyboard : Standard keyboard
 Monitor : 15 inch color monitor
1.3.2 SOFTWARE SPECIFICATION
 Front End : .NET
 IDE : dream weaver
 Back End : My SQL

Software description
What is .NET?
When .NET was announced in late 1999, Microsoft positioned the technology as a
platform for building and consuming Extensible Markup Language (XML) Web services. XML
Web services allow any type of application, be it a Windows- or browser-based application
running on any type of computer system, to consume data from any type of server over the
Internet. The reason this idea is so great is the way in which the XML messages are transferred:
over established standard protocols that exist today. Using protocols such as SOAP, HTTP, and
SMTP, XML Web services make it possible to expose data over the wire with little or no
modifications to your existing code.
Since the initial announcement of the .NET Framework, it's taken on many new and
different meanings to different people. To a developer, .NET means a great environment for
creating robust distributed applications. To an IT manager, .NET means simpler deployment of
applications to end users, tighter security, and simpler management. To a CTO or CIO, .NET
means happier developers using state-of-the-art development technologies and a smaller bottom
line. To understand why all these statements are true, you need to get a grip on what the .NET
Framework consists of, and how it's truly a revolutionary step forward for application
architecture, development, and deployment.
NET Framework
Now that you are familiar with the major goals of the .NET Framework, let's briefly
examine its architecture. As you can see in Figure 1-2, the .NET Framework sits on top of the
operating system, which can be a few different flavors of Windows and consists of a number of
components .NET is essentially a system application that runs on Windows.
Conceptually, the CLR and the JVM are similar in that they are both runtime infrastructures that
abstract the underlying platform differences. However, while the JVM officially supports only
the Java language, the CLR supports any language that can be represented in its Common
Intermediate Language (CIL). The JVM executes byte code, so it can, in principle, support many
languages, too. Unlike Java's byte code, though, CIL is never interpreted. Another conceptual
difference between the two infrastructures is that Java code runs on any platform with a JVM,
whereas .NET code runs only on platforms that support the CLR. In April, 2003, the
International Organization for Standardization and the International Electro technical Committee
(ISO/IEC) recognized a functional subset of the CLR, known as the Common Language
Interface (CLI), as an international standard.
This development, initiated by Microsoft and developed by ECMA International, a
European standards organization, opens the way for third parties to implement their own versions
of the CLR on other platforms, such as Linux or Mac OS X. For information on third-party and
open source projects working to implement the ISO/IEC CLI and C# specifications The layer on
top of the CLR is a set of framework base classes. This set of classes is similar to the set of
classes found in STL, MFC, ATL, or Java. These classes support rudimentary input and output
functionality, string manipulation, security management, network communications, thread
management, text management, reflection functionality, collections functionality, as well as
other functions.
On top of the framework base classes is a set of classes that extend the base classes to
support data management and XML manipulation. These classes, called ADO.NET, support
persistent data management—data that is stored on backend databases. Alongside the data
classes, the .NET Framework supports a number of classes to let you manipulate XML data and
perform XML searching and XML translations. Classes in three different technologies (including
web services, Web Forms, and Windows Forms) extend the framework base classes and the data
and XML classes. Web services include a number of classes that support the development of
lightweight distributed components, which work even in the face of firewalls and NAT software.
These components support plug-and-play across the Internet, because web services employ
standard HTTP and SOAP.
Web Forms, the key technology behind ASP.NET, include a number of classes that allow
you to rapidly develop web Graphical User Interface (GUI) applications. If you're currently
developing web applications with Visual Interdev, you can think of Web Forms as a facility that
allows you to develop web GUIs using the same drag-and-drop approach as if you were
developing the GUIs in Visual Basic. Simply drag-and-drop controls onto your Web Form,
double-click on a control, and write the code to respond to the associated event. Windows Forms
support a set of classes that allow you to develop native Windows GUI applications. You can
think of these classes collectively as a much better version of the MFC in C++ because they
support easier and more powerful GUI development and provide a common, consistent interface
that can be used in all languages.
The Common Language Runtime
 Automatic memory management
 Cross-language debugging
 Cross-language exception handling

Inside the Common Language Runtime

The common language runtime enables code running in its execution environment to
have features such as security, versioning, memory management and exception handling because
of the way .NET code actually executes. When you compiled Visual Basic 6 forms applications,
you had the ability to compile down to native node or p-code. Visual Studio.net offers a rich set
of development tools that hide a lot of the complexity inherent in working with the .NET
Framework. This reduces time spent both learning the product and developing applications.
When Visual Studio .NET is installed, the CLR and the .NET Framework classes are also
installed. These are command line applications that are built without a graphical user interface
(GUI) and which can be executed from, and interact with, a DOS Window. In addition to their
intrinsic value, they can be particularly useful for testing sections of code to ensure proper
functionality

WINDOWS FORMS

 These are rich-client applications that are built around a GUI similar to desktop
applications written using Visual FoxPro 7.0. New features for client applications
developed in the .NET Framework include visual inheritance, code-free resizing,
automatic control updates, and new controls.

WEB FORMS

 These are browser-based applications that are built around a GUI with special controls.
Web form applications are written using ASP.NET.

XML WEB SERVICES

 These are applications that define XML Web services that can be consumed by other
XML Web services or applications either on a local network or exposed on the Internet.
Because they are based on HTTP and XML, the information they transfer can be passed
through firewalls.

Overview of ASP.NET

ASP.NET is used to create programmable Web pages as part of Web form

applications. Not only can ASP.NET produce dynamic Web pages, but it can also tailor
them to the browser being used by the user. Development in ASP.NET is much easier
because it contains a wide range of object-oriented server-side controls ready for use in
applications. ASP.NET actually supports four different types of control:

HTML server controls

 These are programmable HTML elements that are exposed to the server. HTML server
controls expose an object model that maps very closely to the HTML elements that they
render.

WEB SERVER CONTROLS

These controls have more built-in features than HTML server controls. Web server
controls include not only form-type controls, such as buttons and text boxes, but also
special-purpose controls, such as a calendar. Web server controls are more abstract than
HTML server controls in that their object model does not necessarily reflect HTML
syntax.

VALIDATION CONTROLS

These are controls that incorporate logic and that can be attached to an input control to
test what the user enters. Some validation controls check for a required field, a specific
value or pattern of characters, that a value falls within a specified range, and so on.

USER CONTROLS

These are custom controls created as Web Forms pages. Web Forms user controls can be
embedded in other Web Forms pages and provide an easy way to create menus, toolbars,
and other reusable elements.
 CHAPTER 2
LOGICAL DEVELOPMENT

2.1 DATA FLOW DIAGRAM

A two-dimensional diagram explains how data is processed and transferred in a system.

The graphical depiction identifies each source of data and how it interacts with other data
sources to reach a common output. Individuals seeking to draft a data flow diagram must identify
external inputs and outputs, determine how the inputs and outputs relate to each other, and
explain with graphics how these connections relate and what they result in.
Data flow Symbols:
Symbol Description

An entity. A source of data or a destination

for data.

A process or task that is performed by the

system.

A data store, a place where data is held

between processes.

A data flow.
LEVEL 0

DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole system or
process being analyzed or modeled. It’s designed to be an at-a-glance view, showing the system
as a single high-level process, with its relationship to external entities. It should be easily
understood by a wide audience, including stakeholders, business analysts, data analysts and

Login Store the data

Admin

Passenger
Retrieving the data
 Register
Store the data

Login
Retrieving the data

Passenger
Flight
details Store the data

Fare
enquiry Retrieving the data
 Register
Store the data

Login
Retrieving the data

Passenger
Booking
counters Retrieving the data

Transaction
Store the data

Register
Store the data

Login
Retrieving the data

Protector
Request
Store the data

Fig 2.2.1. Level 1 Data flow diagram

2.2 ARCHITECTURAL DIAGRAM
The Architecture Design document is to discuss the architectural design for the Online
Reservation System project in a clear and concise form. This design document will give a
detailed description of the presentation tier, the middle tier and data tier which consists of
graphical diagrams for the Airline Reservation System. The Unified Modeling Language (UML)
is a standardized visual specification language for object modeling. Thus, the class diagrams and
the sequence diagrams depicted in the Architecture design document will be developed
according to the UML standard notation.

Airline Passenger
reservation Airlines
enquiry booking
management management
management

Airline
reservation
system
Booking
Passenger
enquiry
management
management
Ticket booking
management

Fig 2.2.1 architectural diagram

 CHAPTER 3
DATABASE DESIGN
3.1 DATA DICTIONARY

3.2TABLE DESIGN

3.3 RELATIONSHIP DIAGRAM

An entity-relationship diagram (ERD) is a data modeling technique that graphically

illustrates an information system's entities and the relationships between those entities. An ERD
is a conceptual and representational model of data used to represent the entity framework
infrastructure.

Fig3.3.3ER diagram
CHAPTER 4
PROGRAM DESIGN

4.1 MODULE DESCRIPTIONS

 Admin
 Flight management module
 Service
 Report
 Frequent flyer

4.1.1 ADMIN MODULE

In admin login module admin will login with their specified username and password such that
they can perform the function they had to be.

4.1.2FLIGH MANAGEMENT MODULE

In this module admin can add flight details and also he/she can modify and delete the flight
details. This module derives the user like on which dates flight flights available and how many
seats are available to book a ticket and also this module will help the frequent flyer to know the
how many he/she needs to travel from one point to another point with free ticket.

4.1.3 SERVICE MODULE

In this module the administration can add the services provided by the airline service and he can
also modify the services .He has to add service from source to destination and distance between
two points.
4.1.4 REPORT MODULE

In this module the data from the database will be shown in tabular format as report to the users of
this system

4.1.5 FREQUENT FLYER MODULE

In this module the flyer should register to access this system. Frequent flyer means, the person
who travel frequently by air. The frequent flyer should login to the system, to utilize the benefits
of the frequent flyer offered by particular airline services. This system maintains the complete
details of the registered user and also its facilitate to update and modify the details of the user. In
this module the user can book a ticket and see the status of the flight between two points.
 CHAPTER 5
SYSTEM TESTING

5.1 Testing

Testing is a series of different tests that whose primary purpose is to fully exercise the
computer based system. Although each test has a different purpose, all work should verify that
all system element have been properly integrated and performed allocated function. Testing is
the process of checking whether the developed system works according to the actual requirement
and objectives of the system. The philosophy behind testing is to find the errors. A good test is
one that has a high probability of finding an undiscovered error. A successful test is one that
uncovers the undiscovered error. Test cases are devised with this purpose in mind. A test case is
a set of data that the system will process as an input.

5.1.1 Types of Testing:

5.1.2 System testing

After a system has been verified, it needs to be thoroughly tested to ensure that every component
of the system is performing in accordance with the specific requirements and that it is operating
as it should including when the wrong functions are requested or the wrong data is
introduced. Testing measures consist of developing a set of test criteria either for the entire
system or for specific hardware, software and communications components. For an important
and sensitive system such as an electronic voting system, a structured system testing program
may be established to ensure that all aspects of the system are thoroughly tested.

Testing measures that could be followed include:

 Applying functional tests to determine whether the test criteria have been met
 Applying qualitative assessments to determine whether the test criteria have
been met.
 Conducting tests in “laboratory” conditions and conducting tests in a variety of
“real life” conditions.
  Conducting tests over an extended period of time to ensure systems can
perform consistently.
 Conducting “load tests”, simulating as close as possible likely conditions while
using or exceeding the amounts of data that can be expected to be handled in an
actual situation.
Test measures for hardware may include:

 Applying “non-operating” tests to ensure that equipment can stand up to expected levels
of physical handling.
 Testing “hard wired” code in hardware (firmware) to ensure its logical correctness and
that appropriate standards are followed.

Tests for software components also include:

 Testing all programs to ensure its logical correctness and that appropriate design,
development and implementation standards have been followed.
 Conducting “load tests”, simulating as close as possible a variety of “real life” conditions
using or exceeding the amounts of data that could be expected in an actual situation.
 Verifying that integrity of data is maintained throughout its required manipulation.

5.1.3 Unit testing

The first test in the development process is the unit test. The source code is normally divided into
modules, which in turn are divided into smaller units called units. These units have specific
behavior. The test done on these units of code is called unit test. Unit test depends upon the
language on which the project is developed. Unit tests ensure that each unique path of the project
performs accurately to the documented specifications and contains clearly defined inputs and
expected results. Functional and reliability testing in an Engineering environment. Producing
tests for the behavior of components (nodes and vertices) of a product to ensure their correct
behavior prior to system integration.
5.1.4 System testing

Several modules constitute a project. If the project is long-term project, several developers write
the modules. Once all the modules are integrated, several errors may arise. The testing done at
this stage is called system test. System testing ensures that the entire integrated software system
meets requirements. It tests a configuration to ensure known and predictable results. System
testing is based on process descriptions and flows, emphasizing pre-driven process links and
integration points. Testing a specific hardware/software installation. This is typically performed
on a COTS (commercial off the shelf) system or any other system comprised of disparate parts
where custom configurations and/or unique installations are the norm.

5.1.5 Integration testing

Testing is which modules are combined and tested as a group. Modules are typically code
modules, individual applications, source and destination applications on a network, etc.
Integration Testing follows unit testing and precedes system testing. Testing after the product is
code complete. Betas are often widely distributed or even distributed to the public at large in
hopes that they will buy the final product when it is release.
 CHAPTER 6
CONCLUSION
The “airline reservation system” was successfully designed and is tested for accuracy and
quality. During this project we have accomplished all the objectives and this project meets the
needs of the organization. The developed will be used in searching, retrieving and generating
information for the concerned requests. The advantages that are with this proposed system are
Reduced entry work, Easy retrieval of information ,Reduced errors due to human intervention,
User friendly screens to enter the data, Portable and flexible for further enhancement ,Web
enabled and Fast finding of information requested.
 CHAPTER 7
REFERENCES

BIBLIOGRAPHY

Book reference:

[1]ASP.NET 3.5 Unleashed, by Stephen Walther. SAMS Publishing, ISBN

[2]Microsoft ASP.NET and AJAX: Architecting Web Applications, by Dino Esposito. Microsoft
Press, ISBN [3]SQL Server MVP Deep Dives, by Paul Nielson and 52 other MVPs.

[3]ASP.NET MVC Framework Unleashed, by Stephen Walther.

Nov 10, 2009

Web Reference:

https://www.itprotoday.com/web-application-management/top-books-aspnet-developers

https://www.sanfoundry.com/best-reference-books-asp-net/
 CHAPTER 8

APPENDICES

8.1 – SOURCE CODE

8.2 _O/P SCREENS