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
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
21-11-2011, 10:05 AM
to get information qabout the topic"Airline Reservation System"refer the link bellow
https://seminarproject.net/Thread-airlin...ion-system https://seminarproject.net/Thread-airlin...tem?page=2 https://seminarproject.net/Thread-airlin...tem?page=3
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.
03-02-2012, 11:14 AM
to get information about the topic Online Theater Booking System full report ,ppt and related topic refer the link bellow
http://project-seminars.com/attachment.php?aid=16297 https://seminarproject.net/Thread-online...ing-system https://seminarproject.net/Thread-online...vr-cinemas https://seminarproject.net/Thread-airlin...tem?page=3 https://seminarproject.net/Thread-automa...rformances https://seminarproject.net/Thread-online...ing-system https://seminarproject.net/Thread-airlin...tem?page=2 https://seminarproject.net/Thread-airlin...ion-system https://seminarproject.net/Thread-airlin...tem?page=4
09-02-2012, 04:24 PM
Airline Reservation System
RA1810A23.doc (Size: 301.5 KB / Downloads: 80) 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, 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.
18-02-2012, 11:17 PM
hiii there.. can i have a copy of airlines reservation system in asp.net with database
09-03-2012, 03:24 PM
Airline Reservation System
airline reservation system (1).doc (Size: 90 KB / Downloads: 88) 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.
09-03-2012, 03:58 PM
PLZZZ HELP!! CAN I HAVE A CODE FOR AIRLINE RESERVATION SYSTEM IN ASP.NET OR VISUAL BASIC 2008!!!
24-03-2012, 03:16 PM
Airline Reservation System
AIRLINE RESERVATION SYSTEM.doc (Size: 146 KB / Downloads: 631) PROBLEM DEFINITION “Apple Airways” are one of the private airlines in India, which caters large number of people. It has about 10 planes in which 5 serves for domestic and 5 for international. As the company is doing good business, they want to make the reservation system as a computerized Airline Reservation System. The plane details, their departure and arrival time, source and destination are as follows. . 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. 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.
24-03-2012, 03:27 PM
AIRLINE RESERVATION SYSTEM
Ars2.doc (Size: 105.5 KB / Downloads: 79) 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. 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. Functional Requirements 3.1 User Accounts 3.1.1 The passenger, who will henceforth be called the ‘user’, will be presented with 3 choices by the reservation system, as the first step in the interaction between them. A user can choose one of these and his choice would be governed by whether he is a guest or a registered user and whether he wants to check the availability of tickets or also block/buy them. The terms ‘registered user’ and ‘guest’ are described below. 3.1.1.1 A user who has traveled by the airline earlier would have been given a user id and a password. He would have his personal information stored in the database referred to earlier in section 2 as ‘DB-user’ Registration and creation of user profile The system shall require a user to register, in order to carry out any transactions with it except for checking the availability of tickets. It will ask the user for the following information at the least – a user id, a password, first name, last name, address, phone number, email address, sex, age, preferred credit card number. The system will automatically create a ‘sky miles’ field and initialize it to zero in the user’s profile. 3.3 Checking Availability 3.3.1 After logging in a user (either a registered user or a guest), the system shall request him to enter the following details – origin city and destination city. “City’ is a generic term and refers to a city or town as the case may be. The origin and destination cities would be entered as text. 3.3.2 The system shall now refer to the flight schedule database, referred to as ‘DB-geography’ in section 2, and check if there is any ambiguity with the names of the cities. In case there are more than two cities with same name as entered by the user, the system shall list all of them (with more qualifications) and ask the user to select one of them. In case, either the origin or destination cities are not listed in DB-geography as being directly serviced by the airline, the system shall suggest the nearest city to which service is available, including the distance of the destination city from this nearest city.
13-06-2012, 11:59 AM
Airline Reservation System
airlinereservation.doc (Size: 327.5 KB / Downloads: 755) INTRODUCTION Generally, we are using SDLC for building database system. The six stages of the SDLC are designed to build on one another, taking the outputs from the previous stage, adding additional effort, and producing results that leverage the previous effort and are directly traceable to the previous stages. This top- down approach is intended to result in a quality product that satisfies the original intentions of the customer. PLANNING STAGE The planning stage establishes a bird's eye view of the intended software product, and uses this to establish the basic project structure, evaluate feasibility and risks Associated with the project, and describe appropriate management and technical Approaches. REQUIREMENTS DEFINITION STAGE The requirements gathering process takes as its input the goals identified in the high-level requirements section of the project plan. Each goal will be refined into a set of one or more requirements. These requirements define the major functions of the intended application, define operational data areas and reference data areas, and define the initial data entities. Major functions include critical processes to be managed, as well as mission critical inputs, outputs and reports. A user class hierarchy is developed and associated with these major functions, data areas, and data entities. DESIGN STAGE The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input. DEVELOPMENT STAGE The development stage takes as its primary input the design elements described in the approved design document. For each design element, a set of one or more software artifacts will be produced. Software artifacts include but are not limited to menus, dialogs, and data management forms, data reporting formats, and specialized procedures and functions. Appropriate test cases will be developed for each set of functionally related software artifacts, and an online help system will be developed to guide users in their interactions with the software.
27-06-2012, 02:06 PM
AIRLINE RESERVATION SYSTEM
AIRLINE RESERVATION SYSTEM.doc (Size: 43 KB / Downloads: 52) INTRODUCTION: Airline Reservation System (ARS) is a computerized system used to store and retrieve information and conduct transactions related to air travel. The systems was originally designed and operated by airlines, but were later extended for the use of travel agencies. Major ARS operations that book and sell tickets for multiple airlines are known as GLOBAL DISTRIBUTION SYSTEM (GDS). Airlines have divested most of their direct holdings to dedicated gds companies, who make their systems accessible to consumers through Internet gateways. Modern GDSes typically allow users to book hotel rooms and rental cars as well as airline tickets. Today, air travel information is linked, stored, and retrieved by a network of Computer Reservations Systems (CRS), accessible by multiple airlines and travel agents. The global distribution system (GDS) makes for an even larger web of airline information, not only merging the buying and selling of tickets for multiple airlines, but also making the systems accessible to consumers directly. GDS portals and gateways on the Web allow consumers to purchase tickets directly, select seats, and even book hotels and rental cars 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. Scope of the system: The name of this 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 a facility to book a ticket, modify or cancel a particular reservation but it does not provides the customers with details of cost of the tickets and it does not allow the customer to modify a particular part of his reservation and he/she can modify all his details. The project is aimed at exposing the relevance and importance of Airline Reservations Systems (ARS). It is projected towards enhancing the relationship between customers and airline agencies through the use of ARSs , there by easing the flight ticketing and selling process and all air traveling operations. Need of Airlines System: A few factors that direct us to develop a new system are given below: 1) Faster System 2) Accuracy 3) Reliability 4) Informative 5) Reservations and cancellations from anywhere to any place Drawbacks of the existing system: The Drawbacks of the existing system can be categorized as that of 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. Automated system: With the invent of latest technology if we don’t update our system then our business result in losses gradually with time. The automated systems contains the tools of latest trend i.e. computers printers, fax, internet etc. The systems with this technology are very fast, accurate and user-friendly. But these systems cannot be trusted in the case of security of the data and a supervisor is always required to check the software for version updates and maintenance. But those systems need to be updated on a regular basis so as to maintain the integrity.
27-06-2012, 02:35 PM
Airline Reservation System
Airline Reservation System.pdf (Size: 152.5 KB / Downloads: 497) INTRODUCTION PURPOSE AND MOTIVATION 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. PROJECT OVERVIEW 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. for the applications I would be developing in the future. USER CHARACTERISTICS There are two kinds of users for the Airline Reservation System. One is the customer and the other is the administrator. The customers do not need to have any prior training to use the application. However, instructions for making flight and motel reservations would be provided to them on the airline website. The administrators would however need to be trained in order to use the application. CONSTRAINTS Incase of changes made to the database, the application should be able to show the updated information on the website, without much delay. The database for the project is designed to be of moderate size. Currently, the application is designed to be able to run in Internet Explorer. The Airline Reservation system will be designed in such a way that, it can be run on a Windows XP/2000 and IIS server. The .NET technology will be used to code the project and SQL server 2000 will act as the database for the project. The project will run on Internet Explorer and it should be installed on User’s system.
30-07-2012, 11:44 AM
to get information about the topic "web based online airline reservation system " full report ppt and related topic refer the link bellow https://seminarproject.net/Thread-airlin...tem?page=4 https://seminarproject.net/Thread-airlin...tem?page=2 https://seminarproject.net/Thread-airlin...?pid=77356 http://seminarprojectsshowthread.php?tid=10490&google_seo=4BO4++&pid=77356
01-08-2012, 12:01 PM
AIRLINE RESERVATION SYSTEM
AIRLINE RESERVATION.doc (Size: 481 KB / Downloads: 64) INTRODUCTION PROBLEM STATEMENT The purpose of the “AIRLINE RESERVATION” is to create convenient and easy-to-use online system for passengers, trying to buy airline tickets so that people can make reservations online without the hassle of meeting travel agents. It intends to check all the available airline databases and return a string of results, which can help them in their travel plans. This Is Database Application for maintaining customer’s database. SYSTEM ANALYSIS System analysis is the way of studying a system with an eye on solving its problem using computer. It is the most essential part of the development of a project of a system analysis System analysis consists of system element, process and technology. To analyze a system, has to study the systems in details. The analyst has to understand the functioning and concept of the system in detail, before design the appropriate computer based system that will meet all the requirements of the existing system. The system analyst has to carry out a customary approach to use the computer for problem solving. System analysis includes the following basic concepts IDENTIFICATION OF NEEDS A computer reservations system (or central reservation system) (CRS) is computerized system used to store and retrieve information and conduct transactions related to air travel. Originally designed and operated by airlines, CRSes were later extended for the use of travel agencies. Major CRS operations that book and sell tickets for multiple airlines are known as global distribution systems (GDS). Airlines have divested most of their direct holdings to dedicated GDS companies, who make their systems accessible to consumers through Internet gateways. Modern GDSes typically allow users to book hotel rooms and rental cars as well as airline tickets. They also provide access to railway reservations in some markets although these are not always integrated with the main system. WORK DONE BY OTHER The existing system is manual entry of up keeping of the details of the persons who are registered already. And it is very difficult for each person to come to the office. Users can also enquire about the tickets through phones. It is very diffficult for the user to remember all the details that they received through phones. And it is also very difficult to calculate how many people’s registered in a month by hand. This requires quite a lot of time and wastage of money as it requires quite lot of manpower to do that. Another factor that takes into account that is the possibility of errors and which requires verification and checking of data relating to various operations which is done manually. Data's are stored globally and are retrieved in the same manner. Most of the data are hidden from outside the world. The limitations of existing system are that it is not all personalized. It cannot be used for personal and quick reference. Even the other staff members can make quick entries if the responsible person is not present. PROPOSED SOLUTION The modern computerized system is developed with the aim to overcome the drawbacks of existing system. The proposed system has got many advantages. People from different parts of the world can register very easily. The new system is more personalized. It is maze in such a manner that all the new users can understand all the options in it very easily. It is made in a quick and easy referential manner. This system helps the user to go through the rates quoted by different travel agencies and select the convenient rate that is suitable for him. Access to all important matters are not always locked and can be opened easily at the time of urgency. The advantages of proposed system are that security is maintained in the new system. Securities for all important data are maintained confidentially. As it is easily understandable and user friendly, quick entries can be made in this system. CONCLUSION The project report entitled "AIR TICKET RESERVATION" has come to its final stage. The system has been developed with much care that it is free of errors and at the same time it is efficient and less time consuming. The important thing is that the system is robust. Also provision is provided for future developments in the system. The entire system is secured. This online system will be approved and implemented soon |
|