ASK HERE

project topics · 21-04-2010, 11:50 PM

Airline Reservations Systems contain airline schedules, fare tariffs, passenger reservations and ticket records.An airlineâ„¢s inventory contains all flights with their available seats. The inventory of an airline is generally divided into service classes (e.g. First, Business or Economy class) and up to 26 booking classes, for which different prices and booking conditions apply. Inventory data is imported and maintained through a Schedule Distribution System over standardized interfaces. One of the core functions of the inventory management is the inventory control. Inventory control steers how many seats are available in the different booking classes, by opening and closing individual booking classes for sale. In combination with the fares and booking conditions stored in the Fare Quote System the price for each sold seat is determined.

Users access an airlineâ„¢s inventory through an availability display. It contains all offered flights for a particular city-pair with their available seats in the different booking classes. This display contains flights, which are operated by the airline itself as well as code share flights which are operated in co-operation with another airline. The availability of seats of other airlines is updated through standard industry interfaces. Depending on the type of co-operation it supports access to the last seat (Last Seat Availability) in real-time. Reservations for individual passengers or groups are stored in a so-called Passenger Name Record (PNR). Among other data, the PNR contains personal information such as name, contact information or special services requests (SSRs) e.g. for a vegetarian meal, as well as the flights (segments) and issued tickets. Some reservation systems also allow to store customer data in profiles to avoid data re-entry each time a new reservation is made for a known passenger. In addition most systems have interfaces to CRM systems or Customer Loyalty applications (aka Frequent Traveler Systems). Before a flight departs the so-called Passenger Name List (PNL) is handed over to the Departure Control System that is used to check-in passengers and baggage. Reservation data such as the number of booked passengers and special service requests is also transferred to Flight Operations Systems, Crew Management and Catering Systems. Once a flight has departed the reservation system is updated with a list of the checked-in passengers (e.g. passengers who had a reservation but did not check in (No Shows) and passengers who checked in, but didnâ„¢t have a reservation (Go Shows)). Finally data needed for revenue accounting and reporting is handed over to the administrative systems

projectsofme · 29-09-2010, 04:27 PM

The Airline Reservation System is source code is given here...[attachment=4625]

07-10-2010, 09:44 AM

[attachment=5234] source code in java

seminar surveyer · 08-10-2010, 02:15 PM

[attachment=5426]

Introduction

The Airline Reservations System (ARS) was one of the earliest changes to improve efficiency. 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 which supports travel agencies and other distribution channels in making reservations for most major airlines in a single system.

Airline Reservations Systems contain airline schedules, fare tariffs, passenger reservations and ticket records. An airline's direct distribution works within their own reservation system, as well as pushing out information to the GDS. A second type of direct distribution channel are consumers who use the internet or mobile applications to make their own reservations.

There are 5 modules in this project.

1. Administrator Module.

Enables the airline administrator to perform all administrative functions and manage inventory over LAN or the Internet. The administrator can define or modify routes, fares, schedules and assign or deny access rights for qualified travel agents and other authorized users.

2. Reservation Agent Module.

Allows the airlines reservation agents to make and modify reservations on the LAN or over the internet. The reservation agents could be stationed at any airline office location.

3. Passenger Module.

This module enables online customers to make reservations, view their bookings, make special service requests and define their preferences over the web.

4.Payment.

Provides the airline with the ability to set up various travel agents and give them reservations capabilities over the Internet. The travel agents are able to display and offer discounted fares to passengers.

5.Cancellation.

The system should allow the user to cancel the existing booking. In this cancellation very helpful in all the travelers.

seminar surveyer · 16-10-2010, 10:51 AM

[attachment=6248]

PROBLEM DEFINITION
The definition of our problem lies in manual system and a fully automated system.
Manual system : The system is very time consuming and lazy. This system is more prone to
errors and sometimes the approach to various problems is unstructured.
Technical system : With the advent of latest technology if we do not update our system then
our business result in losses gradually with time. The technical systems contains the tools of latest
trend i.e. computers printers, fax, Internet etc. The systems with this technology are very fast,
accurate, user-friendly and reliable.
.
Need of Airlines system
A few factors that directs us to develop a new system are given below -:
1) Faster System
2) Accuracy
3) Reliability
4) Informative
5) Reservations and cancellations from any where to any place

projectsofme · 18-10-2010, 04:10 PM

[attachment=6487]

AIRLINE RESERVATION SYSTEM

INTRODUCTION

PROBLEM STATEMENT
The web based “airline reservation system” project is an attempt to stimulate the basic concepts of airline reservation system. The system enables the customer to do the things such as search for airline flights for two travel cities on a specified date, choose a flight based on the details, reservation of flight and cancellation of reservation.

The system allows the airline passenger to search for flights that are available between the two travel cities, namely the “Departure city” and “Arrival city” for a particular departure and arrival dates. The system displays all the flight’s details such as flight no, name, price and duration of journey etc.
After search the system display list of available flights and allows customer to choose a particular flight. Then the system checks for the availability of seats on the flight. If the seats are available then the system allows the passenger to book a seat. Otherwise it asks the user to choose another flight.
To book a flight the system asks the customer to enter his details such as name, address, city, state, credit card number and contact number. Then it checks the validity of card and book the flight and update the airline database and user database. The system also allows the customer to cancel his/her reservation, if any problem occurs.

System Requirements Specification
HARDWARE:
PROCESSOR : PENTUIUM IV 2.6 GHz
RAM : 512MB DD RAM
MONITOR : 15” COLOR
HARD DISK :250 GB
CDDRIVE : LG52X
KEYBOARD : STANDARD 102 KEYS
MOUSE :OPTICAL MOUSE

SOFTWARE:
FORNT END :JAVA,HTML,SERVLETS
BACKEND : ORACLE 10i
OPERATING SYSTEM : WINDOWS XP

IDENTIFICATION OF ACTORS
Actors are not part of system.
Actors represent anyone or anything that interacts with (input to receive output from) the system.
An actor is someone or something that:
 Interacts with or uses the system.
 Provides input tot and receives information from the system.
 Is external to the system and has no control over the use cases.
Actors are discovered by examining:
 Who directly uses the system?
 Who is responsible for maintaining the system?
 External hardware used by the system.
 Other systems that need to interact with the system.
The need of the actor are used to develop use cases. This insures that the system will be what the user expected.

dharmil007 · 20-01-2011, 04:15 PM

hey @ projects of me can u pls. give me that airlinewalla project

source of the project

summer project pal · 01-02-2011, 05:20 PM

AIRLINE RESERVATION SYSTEM PROJECT
PROBLEM DEFINITION
The aim of the system is to automate the system of airline ticket reservation. The manual system is very time consuming and lazy. This system is more prone to errors.
The Need of Airlines system:
The major attraction of the system lies in its advantages such as
-Faster System
-Accuracy
-Reliability
-Informative
-Reservations and cancellations from any where to any place

SYSTEM ANALYSIS
The block diagram of the system is given in the report . It contains the AIRLINE RESERVATION SYSTEM in the centre. The booking department is connected to it. It sends the customer request to the system, flight maintenance, bookaing and cancellation etc. The block called the reports is also there. It does the functions such as the PASSENGER LIST, CONFIRMED LIST, WAITING LIST, CANCELLATION LIST etc. The database stores all the data. The system requests and writes data from the database. The accessed data may include the information such as the Passenger list,Fleet info, concession, Flight information,Fare details etc. The stored data may include Ticket reservation, Cancellation,Request for inquiry etc.

Full details of the project is available here:
http://scribddoc/12809826/Airline-Reservation-SystemVb

neha gargust · 04-02-2011, 07:55 PM

srs on airways reservation

seminar class · 07-03-2011, 12:21 PM

presented by:
Kaavya Kuppa

[attachment=9674]
Project Overview
 The main objective of this project is to design and develop an Airline Reservation System.
 This project is mainly intended for the customers, who use the airline websites to make reservations on flights.
 This system will be implemented in C#.NET and SQL Server 2000 will act as the database.
 The main motivation for the project comes from my interest to learn new technologies, like C# and ASP.NET.
 Creating a web-based online application would give me more experience using these technologies.
 Database design was also one of my major objective for choosing this project.
Use Case Diagrams
 Customer Use Case Diagram
 Use Case Diagrams continued
 Administrator Use Case Diagram
 System Functionality
 The functionality for the project is divided among the users and administrators of the Airline Reservation System.
 User Functionality
 Administrator Functionality
 User Functionality
 New Registration
 Edit personal details
 Login/Logout
 Book flights
 Book motels, packages along with the airline ticket reservations
 Contact the airline company
 View the booking instructions online
 Administrator Functionality
 Login/Logout
 Add/Delete/Modify customer information
 Add/Delete/Modify flight information
 Add/Delete/Modify package or motel information
 Cancellation of Reservations
 E-mail Confirmation
 Modify details of web-page
Cost Estimation Model
 The Constructive Cost Model, also known as the COCOMO model ,has been designed in 1981 by Barry Boehm, to give an estimate of number of man months it will take to develop a software product.
 The model also estimates the development schedule for the project in months and gives us a schedule distribution for all the major phases of a project.
Cost Estimation Model continued
 The Airline Reservation System project has an average complexity and fair flexibility. Thus, this project is classified as an organic project under the COCOMO model.
 The equations as they are modified for the organic projects are as follows:
 Effort = 3.2 * EAF * (Size) ^ 1.05
 Time = 2.5 * (Effort) ^ 0.38 where
 Effort = number of staff months (PM)
 EAF = effort adjustment factor
 Size = number of lines of code for completed product. It is measures in KLOC (thousands of lines of code)
 Time = total number of months
Cost Estimation Model Continued
 Effort = 3.2 * 0.45 * 3.0 ^ 1.05 = 4.56 staff months
 Time = 2.5 * 4.56 ^ 0.38 = 4.44 months (development time)
 Gantt Chart
 Architecture Elaboration Plan
 Revision of the Vision document
 Revision of the Project Plan
Architecture Design
 Developing Prototype
 Test Plan
 Formal Technical Inspections
 Formal Requirements Specification
 Phase 2 Presentation
Project Plan (Phase 1)
 Vision Document 1.0
 Project Plan 1.0
 Software Quality Assurance Plan
 Presentation 1
Project Plan (Phase 2)
 Action items identified during phase I
 Vision Document 2.0
 Project Plan 2.0
 Formal Requirement Specification
 Architecture Design
 Test Plan
 Formal Technical Inspection – submitted by two individual MSE students
 Executable Architecture Prototype
 Phase 2 Presentation
Project Plan (Phase 3)
 Action items identified during phase II
 User Manual
 Component Design
 Source Code
 Assessment Evaluation
 Project Evaluation
 Test Results
 References
 Formal Technical Inspections - submitted by two individual MSE students
 Final MSE presentation

seminar class · 18-03-2011, 03:06 PM

[attachment=10505]
AIRLINE RESERVATION SYSTEM
SOFTWARE REQUIREMENTS SPECIFICATION
1. INTRODUCTION
1.1. PURPOSE
The main purpose of this software is to reduce the manual errors involved in the airline reservation process and make it convenient for the customers to book the flights as when they require such that they can utilize this software to make reservations, modify reservations or cancel a particular reservation.
1.2 SCOPE
The name of the software is “AIRLINE RESERVATION SYSTEM”. This software provides options for viewing different flights available with different timings for a particular date and provides customers with the facility to book a ticket, modify or cancel a particular reservation but it does not provide the customers with details of cost of the ticket and it does not allow the customer to modify a particular part of his reservation and he/she can modify all his details.
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
ARS-Airline Reservation System
LAN-Local Area Network
GUI-Graphical User Interface
OS-Operating System
RAM-Random Access Memory
MB-Mega Bytes
GB-Giga Bytes
Mbps-Mega bits per second
HDD-Hard Disk Drive
1.4 REFERENCES
The books and materials referred during the pre-development stages of the project include
1. Software Engineering-A Practitioner’s Approach
By Roger S. Pressman
2. Software Engineering-By James Peters
1.5 OVERVIEW
The rest of the document deals about all the main features of this software each will its purpose and its main functions. It also gives details about the interface with other products and related functionality of each product.
2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
The “ARS” software is an independent application. It is a self-contained product. The system interfaces, user interfaces and hardware interfaces related with this software are defined as follows.
2.1.1 System Interfaces
The client systems should be able to share the data available in the data base through the network connection.
2.1.2 User Interfaces
The screen formats and menu structure should be in such a way that even have users will find it easy to use. The product must be use-friendly and very inter-active. The functionality provided by the system like displaying error messages should adapt itself to the different users of the software.
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
Name of the language: Visual Basics
2.1.5 Communication Interfaces
There is an LAN used for communication among the different client systems to be used.
2.1.6 Memory Constraints
The system would require disk space of 10 GB and a 256 MB HDD and 64 MB RAM for client systems.
2.1.7 Operation
The users can first make a reservation in a particular flight for a particular date and time. The system provides the customer with a pin code which gives him access to either make any changes in his reservation or cancel a reservation. These must also be back up of data to enable any easy recovery from any features.
2.1.8 Site Adaptive Requirements
The “ARS” software is an independent and self-contained product and no modification are required to adapt to a particular installation.
2.2 PRODUCT FUNCTIONS
The major functions include
• Providing flight details
• Flight bookings for a particular destination, date and time and also providing with a pin code.
• Allowing the customer to modify or cancel his reservation provided the correct pin code is given.
• Displaying a report of the number of people flying in a particular flight.
2.3 USER CHARACTERISTICS
No technical experience is required basic knowledge of handling system is sufficient.
2.4 CONSTRAINTS
• Regulatory policies: It is a mandatory that no text book must be left empty or contains insufficient data.
• Hardware limitations: There must be a 64 MB on board memory
• Control functions: The software must be very user-friendly and display appropriate error messages.
• Interfaces to other applications: Not applicable.
• Parallel operations: It must support many users simultaneously.
• Reliability requirements: Data redundancy and use of special/blank characters must be avoided.
• Safety/security considerations: The application must be exited always normally.
• Higher order language requirements: VB
2.5 ASSUMPTIONS AND DEPENDENCIES
It is assumed that the details of the cost of ticket are already known to the customer. Future changes like providing different types of flights with different classes like business class, economic class will allow the customers to benefit from one facility.
2.6 APPORTIONING OF REQUIREMENTS
The necessity of providing options to customer to choose their seat or to choose for economic or business class can be delayed until future versions of the software are developed
3. SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACE REQUIREMENTS
3.1.1 User Interfaces
The interface must be easy to understand. The user interface includes
• SCREEN FORMATS/ORGANIZATION: The introductory screen will be the first to be displayed which will allow the users to choose either of the two options, viewing flight detail or booking a ticket.
• WINDOW FORMAT/ORGANIZATION: When the user chooses some other option, then the information pertaining to that choice will be displayed in a new window which ensures multiple windows to be visible on the screen and the users can switch between them.
• DATA FORMAT: The data entered by the users will be alpha numeric.
• END MESSAGES: When there are some exceptions raising error like entering invalid details, then error messages will be displayed prompting the users to re-enter the details.

seminar class · 07-04-2011, 11:21 AM

[attachment=11832]
AIRLINE RESERVATION SYSTEM (ARS)
Background
This project deals with the development of a Software Requirements Specification (SRS) document that specifies what an airline reservation system should and should not do. The SRS document is divided into five sections namely
1. System Objectives
This section lists all the goals and objectives of the system categorized based on the viewpoint of the airline company and the customer (passenger). These are higher-level goals which are somewhat broad in nature. They help in a top-down development of the SRS.
2. System Context
This section clearly depicts the environment and boundaries of the ARS and the entities with which it interacts. It helps us see how the system fits into the existing scheme of things. What the system will do by itself and what it expects other entities to do is clearly delineated.
3. Functional Requirements
This section is the bulk of the document and precisely states the functions of the system – what it should do and what it should not. This section is split into subsections modeled after the real world activities like reserving tickets, rescheduling tickets etc. Freedom from ambiguity and navigability were kept in mind while documentation. A consistent terminology has been followed throughout and the terms are explained in the appendix. The subsections follow a logical sequence that reflects the real world. For example, a customer cannot reschedule a ticket unless he has bought one earlier and cannot buy one unless he has checked its availability.
4. Non-functional Requirements
These are quality requirements that stipulate the performance levels required of the system for various kinds of activities. Numerical lower and upper limits set conditions on the response times, access times etc of the system. Sometimes, tradeoffs are necessary among various non-functional requirements.
5. Future Requirements
These are the specifications which are not provided for now in the current version of ARS but which could be incorporated into future versions. Some of these need advanced technologies and interfaces with other systems. The ARS could be designed in future to enhance the existing capabilities or add entirely new ones.
The assumptions and limitations of the ARS have been interspersed in the SRS to present the same in their proper context.
1. System Objectives
1.1 The Airline Reservation System (ARS) is a software application to assist an airline with transactions related to making ticket reservations, which includes blocking, reserving, canceling and rescheduling tickets.
1.2 From the viewpoint of the airline -
1.2.1 Minimize repetitive work done by the system administrator and reservation clerks.
1.2.2 Maintain consistency among different access modes, e.g. by phone, by web, at the information desk and across different physical locations. The users should be basically taken through the same steps by the system as they go through in conventional desk-reservation systems.
1.2.3 Maintain customer information in case of emergency, e.g. flight cancellation due to inclement weather. The profile can also be used by the airline company to track user preferences and travel patterns to serve them better, plan routes, for better marketing and efficient scheduling of flights.
1.2.4 Maximize the revenue of the airline company by various means:
1.2.4.1 Increase awareness among frequent travelers about various special offers and discounts.
1.2.4.2 Minimize the number of vacant seats on a flight and maximize flight capacity utilization.
1.2.4.3 Maintain the capability to adopt a flexible pricing policy. The price of the tickets should be dynamically determined based on how early, before the date of departure, the customer buys the ticket.
1.3 A survey conducted by airline companies shows that users of an existing reservation system would respond favorably to an ARS that satisfied or helped them satisfy the following objectives:
1.3.1 Reduce effort and frustration for travelers in scheduling a trip, especially by reducing the search effort for the flight they need to take.
1.3.2 Show all possible combinations and itineraries available for a pair of origin-destination cities.
1.3.3 Reduce redundancy in the information required from the customers in order for them to buy tickets, create user accounts etc.
1.3.4 Check the validity of input data and give a feedback to the user in case of errors or inconsistency.
1.3.5 Provide flexible access modes to users – internet, telephone, PDA.
1.3.6 Protect customers’ privacy concerns.
1.3.7 Make it easy for travelers to check the ticket status or make changes to their trip.
2. System Context
2.1 The ARS will provide the following types of easy-to-use, interactive, and intuitive graphical and telephonic interfaces.
2.1.1 The ARS will provide an easy-to-use, intuitive Graphical User Interface (GUI) as part of the Clerk/Administrator’s working desktop environment.
2.1.2 The ARS will also provide an interactive GUI, on the World Wide Web for the general customers.
2.1.3 The above two ARS interfaces shall help provide the following functionalities to the users - access to the ARS to check the flight schedule, availability of seats, ticket price and to block, reserve, cancel, and reschedule tickets.
2.1.4 The ARS will also provide an easy-to-use, simple telephonic user interface, which can be accessed by the customers through telephone or cell phone from anywhere. This interface shall provide access, only to the following functionalities, namely, check flight schedule and check ticket status including any change in the flight timings. The functionality available through this telephonic interface is limited because of security constraints.
2.2 The system and its environment and the interactions between them are depicted in the diagram below.

Udhaya0000 · 09-07-2011, 09:39 AM

Can anyone send the project coding for airline reservation system

smart paper boy · 21-07-2011, 12:01 PM

[attachment=14688]
FEASIBILITY STUDY
Feasibility study is to check the viability of the project under consideration. Theoretically various
types of feasibilities are conducted, but we have conducted three type of feasibilities explained as
under.
ECONOMIC FEASIBILITY
With the manual system the operating cost of the system is about 60 Lacks P.A.. This cost
comprises salary of 25 people, stationary, building rent, electricity, water, telephone etc. But with
the new system this reoccurring cost comes out to be about 20 Lacks P.A. Hence the new system is
economically feasible.
TECHNICAL FEASIBILITY
The new system requires only 6 trained person to work with the system and in overall 10 people
per office are sufficient. So we will identify 6 best people from existing system and train them.
As our existing system is purely manual, so we need a one time investment of Rs 4 Laks for the
purchase of 7 computers, 5 Ticket printers, a laser printer, AC and networking etc. It requires 20
Lacks PA as a operating cost.
With the above details our system is technically feasible as after investing 24 Lacks in a year, the
company is still saving Rs 25 Lacks PA.
OPERATIONAL FEASIBILITY
The new solution is feasible in all sence but operationally it is not. The new system demands the
expulsion of at least 15 people from the company. It creates an environment of joblessness and fear
among the employees. It can lead to an indefinite strike in the company also. So the management
must take corrective actions prior in advance in order to start the further proceedings.

smart paper boy · 30-08-2011, 12:59 PM

[attachment=15560]

Code:
import java.io.*;

import java.sql.*;

import javax.servlet.*;

import javax.servlet.http.*;

public class add extends HttpServlet

{

     String Error,str,str1,fno,end,s1,cap;

     int end1,end2,cap1;

     Connection con;

     Statement st;

     ResultSet rst;

     public void init(ServletConfig config)throws ServletException

     {

       super.init(config);

       try

       {

          Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

          con=DriverManager.getConnection("jdbc:odbc:DSN","scott","tiger");

       }

       catch(Exception e)

       {

        Error="Exception in init:"+e;

       }

     }

     public void doGet(HttpServletRequest req,HttpServletResponse res)throws ServletException,IOException

     {

          PrintWriter out=res.getWriter();

          res.setContentType("text/html");

          fno=req.getParameter("flight_no");

          end=req.getParameter("ending_seatno");

          end1=Integer.parseInt(end);

          end2=end1+1;

          cap=req.getParameter("capacity");

          out.println("<html><body>");

          out.println("<script>");

          out.println("function nam()");

          out.println("{");

          out.println("var a=document.forms[0].cat.value;");

          out.println("if(a.length == 0)");

          out.println("{");

          out.println("alert(\"Null field\");");

          out.println("document.forms[0].cat.focus();");

          out.println("return;");

          out.println("}");

          out.println("else");

          out.println("{");

          out.println("for(i=0;i<a.length;i++)");

          out.println("{");

          out.println("var b=a.substring(i,i+1);");

          out.println("if(!(b >='a' && b <= 'z' || b >='A' && b <= 'Z'))");

          out.println("{");

          out.println("alert(\"Enter alphabets only\");");

          out.println("document.forms[0].cat.focus();");

          out.println("document.forms[0].cat.value=\"\";");

          out.println("return;");

          out.println("}");

          out.println("}");

          out.println("}");

          out.println("document.forms[0].cat.value=a;");

          out.println("}");

          out.println("function total()");

          out.println("{");

          out.println("var a=document.forms[0].ticket.value;");

          out.println("if(a.length == 0)");

          out.println("{");

          out.println("alert(\"Null field\");");

          out.println("document.forms[0].ticket.focus();");

          out.println("return;");

          out.println("}");

          out.println("else");

          out.println("{");

          out.println("for(i=0;i<a.length;i++)");

          out.println("{");

          out.println("var b=a.substring(i,i+1);");

          out.println("if(!(b >=0 || b <= 9))");

          out.println("{");

          out.println("alert(\"Enter the valid number only\");");

          out.println("document.forms[0].ticket.focus();");

          out.println("document.forms[0].ticket.value=\"\";");

          out.println("return;");

          out.println("}");

          out.println("}");

          out.println("}");

          out.println("document.forms[0].ticket.value=a;");

          out.println("}");

          out.println("function check(){");

          out.println("var p= document.forms[0].end.value");

          out.println("if(p.length == 0)");

          out.println("{");

          out.println("alert(\"Null field\");");

          out.println("document.forms[0].end.focus();");

          out.println("document.forms[0].end.value=\"\";");

          out.println("return;");

          out.println("}");

          out.println("else");

          out.println("{");

          out.println("var x=parseInt(document.forms[0].start.value);");

          out.println("x.toString();");

          out.println("var y=parseInt(document.forms[0].end.value);");

          out.println("y.toString();");

          out.println("if(y<=x)");

          out.println("{");

          out.println("alert(\"ending seat no is less than starting seat no verify!\");");

          out.println("document.forms[0].end.focus();");

          out.println("document.forms[0].end.value=\"\";");

          out.println("}");

          out.println("var a="+cap);

          out.println("a.toString();");

          out.println("var b=parseInt(document.forms[0].end.value);");

          out.println("b.toString();");

          out.println("if(b>a){");

          out.println("alert(\"ending seat no is greater than total capacity\");");

          out.println("document.forms[0].end.focus();");

          out.println("document.forms[0].end.value=\"\";");

          out.println("}");

          out.println("else");

          out.println("{");

          out.println("for(i=0;i<p.length;i++)");

          out.println("{");

          out.println("var b=p.substring(i,i+1);");

          out.println("if(!(b >=0 && b <=9))");

          out.println("{");

          out.println("alert(\"Enter numbers only\");");

          out.println("document.forms[0].end.focus();");

          out.println("document.forms[0].end.value=\"\";");

          out.println("return;");

          out.println("}");

          out.println("}");

          out.println("}");

          out.println("}");

          out.println("return;}");

          out.println("</script>");

          out.println("<h2><center><u>Add Flight Details </u></center></h2>");

          try

          {

                   st=con.createStatement();

                   out.println("<center><form method=post action=\"http://localhost:8080/servlet/insert2\">");

                   out.println("<table>");

                   out.println("<tr><td><label>Flight No:</label></td><td><input size=20 name=fno value="+fno+" readonly></td>");   

                   out.println("<td><label>Category:</label></td><td><input size=20 name=cat></td></tr>");

                   out.println("<tr><td><label>Cost Of Tickets:</label></td><td><input size=20 name=ticket onfocus=\"nam()\"></td>");

                   out.println("<td><label>Start Seat No:</label></td><td><input size=20 name=start value="+end2+" readonly onfocus=\"total()\"></td></tr>");

                   out.println("<tr><td><label>Ending Seat No:</label></td><td><input size=20 name=end onblur=\"check()\"></td></tr></table>");

                   out.println("<input type=hidden name=cap value="+cap+">");

                   out.println("<input type=submit value=submit>");

                   out.println("</form></center>");

          }

          catch(Exception e1)

          {

           out.println("Exception in connection:"+e1);

          }

          out.println("</body></html>");

     }

}

vikas dhiman · 20-11-2011, 01:40 PM

please send me thre online airline reservation system in php with source code and database

plse send me the online airline project in php with souce code and database

**seminar addict** · 21-11-2011, 10:05 AM

to get information qabout the topic"Airline Reservation System"refer the page link bellow

http://studentbank.in/report-airline-reservation-system

http://studentbank.in/report-airline-res...tem?page=2

http://studentbank.in/report-airline-res...tem?page=3

Emmanuel Ololade Adeyemi · 02-02-2012, 05:57 PM

This is a very nice work and I want to make this as my project topic.can i get the program for the implementation of this project? Pls.
Thanks.

**seminar addict** · 03-02-2012, 11:14 AM

seminar paper · 09-02-2012, 04:24 PM

Airline Reservation System

[attachment=17373]
SYSTEM DESIGN

In this phase initially I had designed E-R diagram of the processes , in order to identify various entities and relation ship set ,entity set ,attributers, page link attributes The Diagram of this process as under.
After this step We had tried design the data base for the new system and normalized it
The tables motivated in data dictionaries enclosed as annex II is an out come of this step

ALGORITHM

In this phase further I had designed algorithms for various technical sub problem a few than are enclosed here with.

RESERVATION

• A PERSON COME TO RESERVED ATICKET.

CANCELLATION

• A PASSENGER COME TO CANCEL THE TICKET

• THEN THE SYSTEM OPEN THE DELET FORM

• THEN CLICK SHOE COMMAND

• IT DISPLAY ALL THE PASSENGER LIST

• THEN SELECT THE PNR NUMBER AND CLICK DELET OPTION

• THE SYSTEM SHOW RECORD IS DELETED.

WHEN PASSENGER COME TO RESERVED A TICKET THEN SYSTEM FIND OUT THE FLIGHT DETAILS.

SYSTEM CLICK FLIGHT DETAILS OPTION THEN THE FLIGHT DETAILS FORM OPEN

THOSE SYSTEM ARE FOLLOWED .

FLIGHT_DETALS:-

• . IN FLIGHT DEAILS WE FIRST CREATE A FORM.

• . THEN WE MAKE ALL TEXT BOX.

• . WE CREATE COMMAN BOX..
• . IN THIS FORM WE ARE USE VARIOUS COMMAND BOX THOSE ARE

• PREVIOUS,FIRST,NEXT, ADD,NEW,UPDATE, DELETE, SAVE

• . IN THIS FORM WE ADD NEW FLIGHT RECORD AND UPDATE IT THEN THE

• VALU IS GO TO THE DATABASE.

• .WHEN WE CLICK NEXT , LAST , PREVIOUS, FIRST COMMAND BUTTON

• THEN IT SHOW VARIOUS THING SERIALLY.

• THEN HE GIVES HIS FULL DETAILS

• IN CUSTOMER FORM THOSE DETAILS WERE WRITTEN.

• THEN COMPUTER CHEQUE THE DATE WHAT DATE THE PERSON RESER VED

• DATE WISE IT CHEQUE THE FLIGHTS

• IF THE FLIGHT IS FLING THAT DAY

• THEN SYSTEM JUSTIFY THE SPECIFIC FLIGHT ID

• IT CHEQUE ITS SEAT CLASS.

fairooz · 18-02-2012, 11:17 PM

hiii there.. can i have a copy of airlines reservation system in asp.net with database

seminar paper · 09-03-2012, 03:24 PM

Airline Reservation System

[attachment=18163]

AIRLINE RESERVATION SYSTEM (ARS)

Background
This project deals with the development of a Software Requirements Specification (SRS) document that specifies what an airline reservation system should and should not do. The SRS document is divided into five sections namely
1. System Objectives
This section lists all the goals and objectives of the system categorized based on the viewpoint of the airline company and the customer (passenger). These are higher-level goals which are somewhat broad in nature. They help in a top-down development of the SRS.
2. System Context
This section clearly depicts the environment and boundaries of the ARS and the entities with which it interacts. It helps us see how the system fits into the existing scheme of things. What the system will do by itself and what it expects other entities to do is clearly delineated.
3. Functional Requirements
This section is the bulk of the document and precisely states the functions of the system – what it should do and what it should not. This section is split into subsections modeled after the real world activities like reserving tickets, rescheduling tickets etc. Freedom from ambiguity and navigability were kept in mind while documentation. A consistent terminology has been followed throughout and the terms are explained in the appendix. The subsections follow a logical sequence that reflects the real world. For example, a customer cannot reschedule a ticket unless he has bought one earlier and cannot buy one unless he has checked its availability.
4. Non-functional Requirements
These are quality requirements that stipulate the performance levels required of the system for various kinds of activities. Numerical lower and upper limits set conditions on the response times, access times etc of the system. Sometimes, tradeoffs are necessary among various non-functional requirements.
5. Future Requirements
These are the specifications which are not provided for now in the current version of ARS but which could be incorporated into future versions. Some of these need advanced technologies and interfaces with other systems. The ARS could be designed in future to enhance the existing capabilities or add entirely new ones.
The assumptions and limitations of the ARS have been interspersed in the SRS to present the same in their proper context.

1. System Objectives

1.1 The Airline Reservation System (ARS) is a software application to assist an airline with transactions related to making ticket reservations, which includes blocking, reserving, canceling and rescheduling tickets.
1.2 From the viewpoint of the airline -
1.2.1 Minimize repetitive work done by the system administrator and reservation clerks.
1.2.2 Maintain consistency among different access modes, e.g. by phone, by web, at the information desk and across different physical locations. The users should be basically taken through the same steps by the system as they go through in conventional desk-reservation systems.
1.2.3 Maintain customer information in case of emergency, e.g. flight cancellation due to inclement weather. The profile can also be used by the airline company to track user preferences and travel patterns to serve them better, plan routes, for better marketing and efficient scheduling of flights.
1.2.4 Maximize the revenue of the airline company by various means:
1.2.4.1 Increase awareness among frequent travelers about various special offers and discounts.
1.2.4.2 Minimize the number of vacant seats on a flight and maximize flight capacity utilization.

fairooz · 09-03-2012, 03:58 PM

PLZZZ HELP!! CAN I HAVE A CODE FOR AIRLINE RESERVATION SYSTEM IN ASP.NET OR VISUAL BASIC 2008!!!

**seminar details** · 12-10-2012, 01:46 PM

to get information about the topic "airline reservation system" full report ppt and related topic refer the page link bellow

http://studentbank.in/report-project-rep...ion-system

http://studentbank.in/report-airline-res...e=threaded

**seminar details** · 16-11-2012, 01:38 PM

to get information about the topic "airline reservation system" full report ppt and related topic refer the page link bellow

http://studentbank.in/report-airline-res...em-details

http://studentbank.in/report-airline-res...e=threaded

http://studentbank.in/report-project-rep...ion-system

Possibly Related Threads...
Thread		Author	Replies	Views	Last Post
	air ticket reservation system full report	project report tiger	16	46,874	08-01-2018, 02:33 PM Last Post: RaymondGom
	Online Ticket Reservation System for Cinema Halls	Electrical Fan	16	19,338	04-07-2016, 03:10 PM Last Post: visalakshik
	Project Report on Airline Reservation System	computer girl	1	7,232	01-11-2012, 01:52 PM Last Post: seminar details
	E-Ticket Airline Reservation System (ETRS)	smart paper boy	1	2,872	03-02-2012, 11:43 AM Last Post: seminar addict
	Lane Reservation for Highways – International conference	project topics	0	869	02-05-2011, 10:11 AM Last Post: project topics
	SOMATHEERAM BEACH RESORT-ONLINE RESERVATION	Zigbee	0	1,319	03-09-2010, 12:39 AM Last Post: Zigbee
	Online Movie Reservation	project topics	0	1,908	21-04-2010, 11:56 PM Last Post: project topics
	Flight Reservation	mechanical wiki	0	2,254	08-09-2009, 01:49 PM Last Post: mechanical wiki
	Development of a feature rich, practical online Tickets reservation system for Cinema	computer science crazy	0	1,495	04-09-2009, 05:00 AM Last Post: computer science crazy
	Airlines Reservation System for Air Industry Ã‚Â	mechanical engineering crazy	0	1,388	28-08-2009, 02:49 AM Last Post: mechanical engineering crazy

Important Note..!

ASK HERE