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 Practitioners 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,
Reference: http://www.seminarprojects.com/Thread-airline-reservation-system? page=3#ixzz1cwVl398p

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 easyto-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/Administrators 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
Reference: http://www.seminarprojects.com/Thread-airline-reservation-system? page=3#ixzz1cwVxmxda

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

Reference: http://www.seminarprojects.com/Thread-airline-reservation-system? page=3#ixzz1cwW4spXG Java source code

import import import import

java.io.*; java.sql.*; javax.servlet.*; 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","sco tt","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);

Reference: http://www.seminarprojects.com/Thread-airline-reservation-system? page=3#ixzz1cwWH2F2S