Software Requirement Specification on ONLINE BOOKING TICKET SYSTEM

SUBMITTED TO:
Mr. RAMANATHAN L

SUBMITTED BY:
SAHIL ALIPURIA (09BCE503) JASKARAN SINGH (09BCE087)

Software Requirements Specification

1. Introduction
Online Air Ticket Booking system is to provide an option to customers to book the tickets online and to check the confirmation online. This system will help the this company to sell the flight tickets online. Unless like in the previous stage people as to walk into travel agency or this company ticket counter to buy the tickets. And also to check the flight timings. This problem is overcome introducing this system...

1.1 Purpose
The purpose of Software Requirements Specification (SRS) document is to describe the external behavior of the online ticket booking system. Requirements Specification defines and describes the operations, interfaces, performance, and quality assurance requirements of this system. The document also describes the nonfunctional requirements such as the user interfaces. It also describes the design constraints that are to be considered when the system is to be designed, and other factors necessary to provide a complete and comprehensive description of the requirements for the software. The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion of the system.

1.2 Scope
The Software Requirements Specification captures all the requirements in a single document. It shall:  Update/add/delete airport information (by administrator)  Update/add/delete airline company and air flight information (by administrator)  Update/add/delete user reservation information (by administrator)  Flight inquiry through basic search: by date, time and airport (or city) of departure and return flights, respectively, and number of passengers  Flight inquiry through advanced search: by one-way/round-trip/multi-city, preference for nonstop, arrival date/time, airline, flight number, and flight class  Flight booking and payment process  Flight reservation modification and cancellation  Frequent user login  Frequent user information management  Dashboard: possible interesting flights for login users, last minute deals, etc.

The features that are described in this document are used in the future phases of the software development cycle. The features described here meet the needs of all the users. The success criterion for the system is based in the level up to which the features described in this document are implemented in the system.

1.3

References

IEEE SRS Template

1.4 Overview
The SRS will provide a detailed description of the Online Ticket Booking System. This document will provide the outline of the requirements, overview of the characteristics and constraints of the system. 1.4.1 Section 2: This section of the SRS will provide the general factors that affect the product and its requirements. It provides the background for those requirements. The items such as product perspective, product function, user characteristics, constraints, assumptions and dependencies and requirements subsets are described in this section. 1.4.2 Section 3: This section of SRS contains all the software requirements mentioned in section 2 in detail sufficient enough to enable designers to design the system to satisfy the requirements and testers to test if the system satisfies those requirements.

2. Overall Description Product Perspective

OTBS is an Internet-based application executing on a Web server and connected to enterprise databases. As shown in Figure 1, OTBS accepts and processes requests from two patrons: end users (customers) and system administrators. Besides the local server database (for storing reservation records), OTBS also integrates databases from airlines and airports. The system is expected to have a Web user interface for customers and an authorization based Web interface for administrators. Its final release has merits of being efficient and precise in flight searching, consistent in booking transaction processing and secure in credential data transmission. Figure 1: Context diagram for OTBS

Customers Flights Search flight

Book flight

Administrator

Manage OTBS

Updates Flight information

Airport information

Airline Database

Airport Database

User characteristics
Customer (favored): A customer is any person who uses OTBS to book air flight ticket(s). Customers have Internet access to OTBS Internet-based user interface to book their flights. They may want to travel among all airports in the India, prefer any date and time, favor any airline as well as various demands such as arrival time, flight class or non-stop. They require an easy-to-use and trustable online air flight reservation system. They need to be fully informed about all available flights before booking, secure assurance when making reservation and flexibility to view, modify or cancel their reservations after having made them. Administrator: An administrator may be a dedicated staff whose responsibility is managing OTBSs back-end databases. They may wish to update/add/delete any information in existing reservation database or user registration database. They may need to create and manage temporary views of fetched records from the databases of airlines and airports. They also need to be convinced that their operations will not affect the correctness of user transactions.

Constraints
y y y y y The information of all the users must be stored in a database . The ticket booking security system must be compatible with the Internet applications. Limited to HTTP/HTTPS. Security issues might crop up. No multilingual support.

Assumptions and dependencies

y y y The users have sufficient knowledge of computers. The administrator is already created. The users know the English language, as the user interface will be provided in English.

3. Specific Requirements
. This section describes in detail all the functional requirements.

3.1 Functionality

3.1.1 Logon Capabilities Input: Username and Password Process: y There can be two types of users: Admin and customer. Both will be have to enter the username and password but admin will have right to edit the database and can make changes in the site whereas customer can only make transactions. y When the users enter the login button they are directed to a new page where they have different options. y The logon facility will be available for 24 hours. Output: Home page is displayed after logging in. 3.1.2 Password change Input: Old and new password. Process: Customer must enter his old password and new password two times correctly. Output: After successfully updating the password a message referring to the same is displayed.

3.1.3 Feedback Input: The feedback the user wants to send to the admin will be allowed to enter in a textbox and his name, email id through which he wants the response about the feedback. Process: The query will be stored into the database in front of the specific customer name. Output: Admin gets to know about the change in the database. 3.1.4 Latest Flight Schedule Procedure Input: The customer will have to enter the place from where he wants the flights via which place and to which destination and finally press view details buttons Process: The source entered will be checked in the database and all the flights starting from that source will be retrieved and the customer will have to select the suitable flight. Output: The customer will be shown all the suitable flights suitable to him and he can decide which flight he wants to travel through.

3.1.5 Account Registration Procedure: Input: The user will have to enter his personal details like mobile no, name, and birthdate, email id etc. and will have to enter the suitable username and password that he wants to keep. Process: The entries made by the user will be stored in the database and he will be registered in the site Output: The user will enter into his account after registering into the site. 3.1.6 Login Home Page Input: The user will have to select the source and the destination, date of journey and the number of seats he wants to book and click book. The user will be shown about all the flights with their timing and the number of seats available in that particular one and user can select the most suitable one Process: The script will check the availability of the seats in that flight between that source and destination on that day. Output: If the seats are available then the seats will be reserved on temporary basis. 3.1.7 Booking Details Input: It will retrieve the input given by the user in the previous booking form. Process: The previous entries made will be stored in the database and will be used in the succeeding forms. Output: The user will get a form which will show the printed ticket. 3.1.8 Payment procedure Input: The customer will be asked to enter the cardholder name, the card no and the pin number. Process: The card no and pin number will be verified with the corresponding card holder name and if that account holds sufficient amount to carry out that transaction. Output: If the verification executes successfully then the amount will be deducted from that account and ticket will be booked finally.

3.2

Usability
y y The system shall allow the users to access the system from the Internet using HTML or its derivative technologies. The system uses a web browser as an interface. Since all users are familiar with the general usage of browsers, no specific training is required.

The system is user friendly and self-explanatory.

3.3 Reliability
The system has to be very reliable for handling huge numbers of users simultaneously, it has to successfully handle a set traffic and allow proper modification of databases. 3.3.1 Availability The system is available 100% for the user and is used 24 hrs a day and 365 days a year. The system shall be operational 24 hours a day and 7 days a week. The admin will have the option to disable and enable links based on the Exam timing 3.3.2 Mean Time between Failures (MTBF) The system will be developed in such a way that it may fail once in a year. 3.3.3 Mean Time to Repair (MTTR) Even if the system fails, the system will be recovered back up within an hour or less. 3.3.4 Accuracy The accuracy of the system is limited only by the system failure. 3.3.5 Access Reliability The system shall provide 100% access reliability.

3.4 Performance
3.4.1 Response Time The Home page should be able to be downloaded within a minute using 56k modem. The information is refreshed every two minutes. The access time for a mobile device should be less than a minute. The system shall respond to the member in not less than two seconds from the time of the request submittal. The system shall be allowed to take more time when doing large processing jobs like making a NEFT transaction. 3.4.2 Administrator Response The system shall take as less time as possible to provide service to the administrator. 3.4.3 Throughput It solely depends on the users ability and choice; throughput could be dealt in terms of the number of hits by users of our portal. 3.4.4 Capacity The system should be capable of handling 2500 users at a time. 3.4.5 Resource Utilization The resources are modified according the user requirements and also according to the number of transactions done by the users.

3.5 Supportability
The system designers shall take in to considerations the following supportability and technical limitations. 3.5.1 Internet Protocols The system shall be comply with the TCP/IP protocol standards and shall be designed accordingly. 3.5.2 Maintenance The maintenance of the system shall be done as per the maintenance contract. 3.5.3 Standards The coding standards and naming conventions will be as per the American standards.

3.6 Design Constraints

3.6.1 Software Language Used The languages that shall be used for coding the System are Active Server Pages (ASP), Java Servlets, Java Server Pages (JSP), HTML, JavaScript and VBScript. For working on the coding phase of the Online Tutorial System, the Internet Information Services (IIS) Server needs to be installed. 3.6.2 Development Tools Will make use of the available Microsoft Visual Studio for working. Also will make use of the online references available for developing programs in ASP, HTML and the two scripting languages, JavaScript and VC#Script. 3.6.3 Class Libraries Will make use of the existing C# libraries available for ASP.NET. Also we need to develop some new libraries for the web-based application. Also will develop new programs using JSP and scripting languages

3.7 On-line User Documentation and Help System Requirements

Online help is provided for each feature available in the system. All the applications provide an on-line help system to assist the user. The nature of these systems is unique to application development as they combine aspects of programming (hyperlinks etc.) with aspects of technical writing (organization, presentation). The user manual describes the use to administrator and students. It also describes the use of application on mobile systems. User manual should be available both as hard copy and also online.

3.8 Purchased Components

The System Administrator will need to purchase the license for IIS Server. It is available with Windows Environment, so the system need not purchase any licensing products.

3.9 Interfaces
3.9.1 User Interfaces The system shall make use of the existing Web Browsers such as Google Chrome or Netscape. The user-interface of the system shall be designed as shown in the userinterface prototypes.

HOME PAGE

The above picture is a snapshot of the Homepage of the website. The various tabs are displayed here and the customer can browse for flights here, he just needs to fill the from and to tab and the concerned flight gets displayed.

ACCOUNT LOGIN PROCEDURE

This is a snapshot of the account login page. When a user wants to book a flight he needs to register first on the website. The above page registers a new user as well as the registered users can login through this page.

LATEST FLIGHT SCHEDULE PROCEDURE

The above is a snapshot of the Latest Flight schedule. The schedule for the selected flight gets displayed.
FEEDBACK PROCEDURE

The above is a snapshot of the customer feedback form. The customer can give us his/her feedback on any issue.

ACCOUNT REGISTRATION PROCEDURE

The above is a snapshot of the new user registration. The customer has to fill in the required fields for registering the websites. Any invalid information given by the user may lead to deactivation of account.

LOGIN HOME PROCEDURE

The above is a snapshot of the Login Home Page. This page is member services area. From here one can update ones membership profile, change passwords or view ones contact information.

SELECT FLIGHT PROCEDURE

The above is the snapshot of the Select Flight Page. The information about the selected flight gets displayed here.

BOOKING DETAILS PROCEDURE

The above snapshot is of the booking details page. When a user books a flight before payment the booking details gets displayed so that the user can verify them and proceed further.

PAYMENT PROCEDURE

The above is the snapshot of the payment gateway. After the user confirms the flight details the payment gateway page opens and the user enters his valid card details and confirms his booking. 3.9.2 Hardware Interfaces The existing Local Area Network (LAN) will be used for collecting data from the users and also for updating and modifying the attendance. 3.9.3 Software Interfaces A firewall will be used with the server to prevent unauthorized access to the system.

3.10 Licensing Requirements

The usage is restricted to only who is registering the site and accepts all the terms and conditions.

3.11 Legal, Copyright, and Other Notices

Online Ticket Booking System is a trademark and cannot be used without the consent of the developer.

3.12 Applicable Standards

The ISO/IEC 6592 guidelines for the documentation of computer based application systems will be followed.

3.13 Supporting Information

The use-case storyboards or the user-interface prototypes are not available. The appendices are not to be considered as part of the requirements.