ARYANs Version 1.

0
Software Requirements Specifications Date:11-12-2010
SRS

Revision History
Date Version Description Author
11-12-2010 1.0 SYNOPSIS ARYANs
ARYANs Version 1.0
Software Requirements Specifications Date:11-12-2010
SRS
Table of Contents
1.0 Introduction………………………………………………………………………………………………….

1.1 Purpose………………………………………………………………………………………………………..

1.2 Scope……………………………………………………………………………………………………………

1.3 Definitions , Acronyms and Abbreviations………………………………………………………..

1.4 References……………………………………………………………………………………………………

1.5 Technologies to be used………………………………………………………………………………..

1.6 Overview……………………………………………………………………………………………………..

2.0 Overall Description……………………………………………………………………………………....

2.1 Product Perspective……………………………………………………………………………………..

2.2 Software Interface………………………………………………………………………………………..

2.3 Hardware Interface………………………………………………………………………………………

2.4 Architecture Diagram…………………………………………………………………………………...

2.5 Database Design

(a) ER Diagram………………………………………………………………………………………

(b) DFD Diagram……………………………………………………………………………………

2.6 Assumptions and Dependencies……………………………………………………………………

3.0 Specific Requirements………………………………………………………………………………….

3.1 Supplementary Requirements………………………………………………………………………..

 ARYANs Version 1.0
Software Requirements Specifications Date:11-12-2010
SRS

1 Introduction:
1.1 Purpose

The history of airline reservations systems began in the late 1950s when
American Airlines required a system that would allow real-time access to flight
details in all of its offices, and the integration and automation of its booking and
ticketing processes. As a result, Sabre (Semi-Automated Business Research
Environment) was developed and launched in 1964. Sabre's breakthrough was its
ability to keep inventory correct in real time, accessible to agents around the world.
Prior to this, manual systems required centralized reservation centers, groups of
people in a room with the physical cards that represented inventory, in this case,
seats on airplanes.

The software which we are going to develop will help the customer to book
the tickets through internet from anywhere. It gives the information about the
availability of tickets, arrivals and departure timings of flights. According ticket
status reservations for the passengers will be made. All onward or return
reservations must be reconfirmed whenever there is a break-journey. If the
passenger wants to cancel the ticket he/she can cancel the ticket but two days before
the journey date.

1.2 Scope
 There are three basic users: Administrator, Staff and
Passengers.
 All users have their own profiles in CAR.
 Passengers can view their profile, booking-detail.
 Passengers are allowed to view the details of reservation and
cancellation of tickets.
ARYANs Version 1.0
Software Requirements Specifications Date:11-12-2010
SRS

1.3 Definition, Acronyms and Abbreviations

 CAR-Centralized Airline Reservation: It is the web application that provides

the facilities for the customer to book the tickets through internet from
anywhere.

 Java Script: Java Script is an object oriented scripting language use to

enable programmatic access to objects within both the client application.

 RAD-Rational Application Development: Is a development tool that helps to

design web pages and also helps to design the diagrams like ER, database
schema diagrams and to generate DDL.

 DB2:DataBase2: DB2 is a family of relational database management system

(RDBMS) products from IBM that serve a number of different operating
system.

 JSP-Java Server Pages: It is used to create dynamic web content.

 J2EE-Java 2 Enterprise Edition: A programming platform which is a part of

java platform for developing and running distributed java.

 HTML-Hyper Text Markup Language: It is used to develop web pages

 HTTP-Hyper Text Transfer Protocol: It is a service protocol.

1.4 References
 IEEE SRS Format.
 Project specification requirement provided by IBM.
ARYANs Version 1.0
Software Requirements Specifications Date:11-12-2010
SRS

1.5 Technologies to be used

 Application architecture-JAVA, J2EE.

 Web server-Apache Tomcat 6.0.
 Development tool-RAD
 Database Platform-DB2
 Design Tool-XML

1.6 Overview of the document

The CAR SRS consists of two sections namely overall description.

 Overall description: This describes the major role of the system components
and interconnections of the hardware components.

 Specific requirements: Describes the role and functions of the users.

2 Overview Description
2.1 Product Perspective

ARYANs Version 1.0

Software Requirements Specifications Date:11-12-2010
SRS

HTTP/HTTPS
END USER

SYSTEM TCP/IP
USER

Apache TomCat

DB2
ARYANs Version 1.0
Software Requirements Specifications Date:11-12-2010
SRS

2.2 Software Interface

 Client on internet: Web Browser, operating system (any).
 Client on intranet: Web Browser, operating system (any).
 Web server: Apache Tomcat 6.0.
 Database server: DB2, OS(Windows7)
 Development End: RAD (HTML, J2EE), DB2, Java Script, OS (Windows7), web
server.

2.3 Hardware Interface

Client Side

Processor RAM Disk Space

Internet Explorer Any standard

6.0/ Processor 128MB Nil
Mozilla/Any other
standard browser

Server Side

Netbean 6.8 Pentium 4, 1.8GHz 1GB 1GB

DB2 Pentium 4, 1.8GHz 1GB 1GB (Excluding

Data Size)
 2.4 Architecture Diagram

1 2

JSP Request

XML ARYANs Version 1.0

Software Requirements Specifications Date:11-12-2010
SRS

SERVLET

Responce RELATIO DB2

NAL
DATABA
3
SE
Apache TomCat 6.0

INTERNET

ADMIN STAFF PASSENGER

2.5Database Design
 ER diagram for booking
 ER diagram for cancellation
ARYANs Version 1.0
Software Requirements Specifications Date:11-12-2010
SRS
ARYANs Version 1.0
Software Requirements Specifications Date:11-12-2010
SRS

 DFD (Data Flow Diagram).

2.6 Assumption and Dependencies

The assumptions of CAR software are

 Here admin’s profile is by default created

 Administrator can easily update the information immediately.

 Information backup should be taken anytime.

 All the information should be available in 24x7.

ARYANS Version 1.0

Software Requirements Specifications Date:11-12-2010
SRS
3 Specific Requirements:

i. A passenger should be able to login to the server through the first page of the
application by using his/her user id and password.

ii. Then passenger can check the availability of the flights for the particular
destination and then he can choose the flight.

iii. After that, passenger can check the status of availability of the seats in order to
book the ticket.

iv. If the seats are available, then he can book the ticket by filling up the required
details in the form given in the application.

v. A passenger can choose a particular class in which they want to travel.

vi. A passenger can pay the amount through debit/credit cards.

vii. A passenger can cancel the reservation before the departure of the flight .

ARYANs Version 1.0

Software Requirements Specifications Date:11-12-2010
SRS
3.1 Supplementary Requirements:

i. Secure access of confidential data (user’s details). SSL can be used.

ii. 24 X 7 availability.

iii. Better component design to get better performance at peak time.

iv. Flexible service based architecture will be highly desirable for future extension.
ARYANs Version 1.0
Software Requirements Specifications Date:11-12-2010
SRS

Bapuji Educational Association (Regd)

Bapuji Institute of Hi-Tech Education
KUVEMPU UNIVERSITY

ARYANs

“CENTRALIZED AIRLINES
RESERVATION”

PROJECT ASSOCIATES
BC080802 ADIB ULLA
BC080820 ASIF.R
BC080837 FAHIM BASHA.M

BC080862 MADHUJIT BHATTACHARJEE

BC080944 SYED ILIYAZ

Bapuji Institute of Hi-Tech Education

DAVANAGERe-04
ACADAMIC YEAR 2008-2011
1