Software Requirements Specification (SRS)

Airline Ticket System

SRS 1.1

17/01/2008

Team 11

Ankara

Computer Engineering & ATILIM UNIVERSITY

Supervisor

Dr. Murat Koyuncu

1
Revision Page

Overview: Software requirement specifications (SRS) document is a description of the

expected software features, constraints, interfaces and other attributes. Aim of this document is to

document the agreed requirements with the project supervisor; to provide the basis for design; to

provide the basis for system test.

Target Audience: Airline Companies

Team Member: Giray Gumrah && Mustafa Kemal Pekturk

Version Control History:

Version Final

Primary Author(s): Mustafa Kemal Pekturk && Giray Gumrah

Description of Version: SRS 1.1

Date Completed: 17/01/2008

Signatures of Approval

Contents
2
Revision Page..........................................................................................................................................2

1.INTRODUCTION...................................................................................................................................4

1.1Product Overview 4

2.SOFTWARE REQUIREMENTS SPECIFICATION.......................................................................................6

2.1 External Interface Requirements 6

2.1.1User Interfaces6

2.1.2Hardware Interfaces 7

2.1.3 Software Interfaces 7

2.1.4 Communications Protocols 8

2.2 Software Product Features10

2.2.1 Functional Requirements 10

2.2.2 Non-Functional Requirements 11

2.3 Software System Attributes 11

2.4 Database Requirements 12

3. ADDITIONAL MATERIAL....................................................................................................................13

3.1 REFERENCES 13

3.1.1 Websites: 13

3.2.1 Documents: 13

3
INTRODUCTION

1.1 Product Overview

Our project is the airline ticket system. In this project, our aim is to find optimal ways to go to

the place where customers want to go. One of the ways is that customers reach destination in

shortest time period. If customers concern about time, money is unimportant for them. Another

one is that customers reach destination by spending lowest fee. In this situation, if customers

concern about money, time is unimportant for them. Optimality guarantees lowest fee or shortest

time.

In the final part of the project, steps of product are finished by us. Product is made up of

associated documentation and computer programs. SPMP, SRS, SDD and STD are the steps of

the associated documentation. In these steps, we introduce characteristics of project like defining

requirements, making prototype for customers and scheduling a project. Secondly, our software

is a web application. Internet programming is mostly used in our project. Customers must use

internet for reaching our system. When we look at computer programs, they include databases,

collection of programs which are related to finding optimal paths with algorithms, graphical user

interface for visual projection. There are two databases. First one of them keeps flight

information about airline companies. Flight information is planes arrival and departure times.

Second database keeps user information. Why it can keep? Because, users are took information

about promotions and opportunities by registering themselves to this accounting system. Also,

we and airline companies know who our customers are by keeping their information. Another
4
one of the collection of computer programs finds optimal way to go to the place where customers

want to go with using optimizations algorithms. In the web browser, user chooses one way to go

to the place. When user chooses, algorithms start to work at the back side of the product. Then, it

returns answer for what user wants. Final part of the computer programs is graphical user

interface (GUI). Interface provides environment for users and developers to communicate each

other. Users buy and reserve tickets by this interface. In addition, it is also web-based interface.

Finally, we explain our product characteristics. Our software product is a web-based

application. Internet programming, database and algorithm are used in the product. At the bottom

parts of this documentation, we mention about external interface requirements, software product

features, software product attributes and database requirements.

5
2. SPECIFIC REQUIREMENTS

2.1 EXTERNAL INTERFACE REQUIREMENT

2.1.1 User Interface Requirements

User interface is used to provide communication between users and system. Our product should

have communication between them. Because, Airline Ticket System is a web-based system and it

should get input from users for processing. Firstly the system should ask to its users about where

they will go, when they will go, which option they will use (least money or least time).Users will

enter their desired place, date period and they will select an option (least time or least money) for

finding the optimized path. The system gets these inputs by using user interface. Then, the

system will study to find an optimized path for users according to least money or least time

constraint which is selected by users. After that, the system will give appropriate output for users

via user interface. Finally users will see the optimized path at their screen according to their

selected option.

User interface elements should be easy to understand. Part of user interface should be well-

organized on screen and the parts should be concatenated right. When users look at the interface,

they understand which pane is used for which purpose. Each task of an interface should be

specified clearly and users should use them correctly. For example, when users press to any

button on interface, they should know which operations are done by pressing this button.

The user interface should be easy to learn. When users use the user interface, they should know

which element is used to which operations. We should teach using of the user interface to users

6
simply. If it is hard to learn, then teaching will take long time and there will be an extra cost for

teaching of product.

The interface actions and elements should be consistent. When users press any button, required

actions should be done by the system.

The screen layout and color of the user interface should be appealing. When users look at the

screen, it will have a nice vision. Colors will be selected clearly, thus eyes of users wont be

tired.

2.1.2 Hardware Interface Requirements

Airline Ticket System is a web-based project. So any personal computer, which has an internet

browser, is enough to use this system.

2.1.3 Software Interface Requirements

In Airline Ticket System, users will use application program via the user interface program.

When database management system access is required, the system establishes a connection to the

database management system, once the connection is created; the client program can

communicate with the database management system. A standard called Open Database

Connectivity (ODBC) provides an application programming interface (API), which allows

client-side programs to call database management system, as long as PC has the necessary

software installed. Most database management system vendors provide ODBC drivers for their

systems. A user can actually connect to several database management system and send query and

transaction requests using the Open Database Connectivity (ODBC) API, which are then
7
processed at the server site. Any query results are sent back to user, which can process or display

the result as needed.

The ODBC specification offers a procedural API for using SQL queries to access data. An

implementation of ODBC will contain one or more applications, a core ODBC library, and one

or more database drivers. The core library, independent of the applications and DBMS, acts as an

interpreter between the applications and the database drivers, whereas the database drivers

contain the DBMS specific details. Thus a programmer can write applications that use standard

types and features without concern for the specifics of each DBMS that the applications may

encounter. Likewise, database driver implementers need only know how to attach to the core

library. This makes ODBC modular.

2.1.4 Communication Protocol Requirements

Hypertext Transfer Protocol (HTTP) shall be used to provide a communication between system

and users. Because, Airline Ticket System is a web-based system which should be reached on

World Wide Web by users. Hypertext Transfer Protocol (HTTP) is a communications protocol

which is used to transfer or convey information on intranets and the World Wide Web. Its

original purpose was to provide a way to publish and retrieve hypertext pages. Development of

HTTP was coordinated by the W3C (World Wide Web Consortium) and the IETF (Internet

Engineering Task Force), culminating in the publication of a series of RFCs, most notably RFC

2616 (June 1999), which defines HTTP/1.1, the version of HTTP in common use. HTTP is a

request/response protocol between a client and a server. The client making an HTTP request,

such as a web browser, is referred to as the user agent. The responding server, which stores or

creates resources such as HTML files and images, is called the origin server. In between the user

8
agent and origin server may be several intermediaries, such as proxies, gateways, and tunnels.

HTTP is not constrained to using TCP/IP and its supporting layers, although this is its most

popular application on the Internet. Indeed HTTP can be implemented on top of any other

protocol on the Internet, or on other networks. HTTP only presumes a reliable transport; any

protocol that provides such guarantees can be used. Typically, an HTTP client initiates a request

by establishing a Transmission Control Protocol (TCP) connection to a particular port on a host

(port 80 by default; see List of TCP and UDP port numbers). An HTTP server listening on that

port waits for the client to send a request message.

9
2.2 Software Product Features

2.2.1 Functional Requirements

The system should have login and signup functionality for users and airline

personnel to create and access accounts.

The system should allow logged in users to make flight reservations.

The system should allow logged in users to cancel flights.

The system should allow logged in airline personnel to edit flight details.

The system should allow user to update his profile.

The system should be able to generate final reports.

10
2.2.2 Non-Functional Requirements

The system should be web-based system. Users should use the system via internet. Thus, when

they want to go anywhere and book a flight ticket efficiently, they need to have only

internet.

Each user should have a user account. The system should ask the username and password to

users. It doesnt permit to unregistered access for reservation.

2.3 Software System Attributes

Reliability: When user wants to call the system over a given period of time, the system should

correctly deliver services as expected by the user. The reliability of the system shall be

good if it delivers services as specified. Otherwise, reliability is bad and it shall produce

unexpected output. So, program should be changed according to right situation.

Availability: When the system has any request at any given time, system should be available, it

should be up and running and able to deliver useful service at this time. The availability of the system

shall be good if it delivers services when it is requested. Otherwise, if requests are not responded at any

given time then it implies bad availability.

Security: The system should resist accidental or deliberate intrusions, when users operate on the

system. If the system should not resist accidental or deliberate intrusions, then important data such as

credit card number, id number, username, etc. which belongs to user, shall be stolen by hacker. Thus,

security of the system shall be low and trust of users shall be ruined. So, security of the system is very

important for users.

11
Maintainability: When the system is used, new requirements may emerge. When these

requirements are emerged, the system should be changeable to accommodate these requirements for

maintaining the usefulness of the system. If the system is not maintainable, then the system can not be

modified for new requirements. In this situation, a new system should be developed for provide new

requirements. The maintainability is important for avoiding from cost.

Performance: The system should use the minimum part of memory. The processes of the system

should use the processor most efficiently. User should finish operation in the least time interval.

Repairability: When the system is used, system failures are inevitable. The disruption caused by

failure can be minimized if the system can be repaired quickly. So, the system should be possible to find

the problem, access the component that has failed and make changes to fix that component. When the

system has a repair, the source code should be modified.

2.4 Database Requirements

In our project, there are two types of databases. One of them keeps user information. Information

is user name, surname, country, city, password, e-mail address and address. It is necessary to

keeping users information in the database. For example, if one user buys more than two or three

tickets by using our system, the system shall provide some discounts on ticket fee for this user.

By this way, company increases its profit.

Another type keeps companies flight information. Information is company name, departure time,

arrival time, locations (source and destination), price of flight and time which is between

departure to arrival time. For example, if we think our system, there are five companies. So,

there are five databases. Each of the companies has a one database. The system shall set up

12
relationship between the databases to find an optimal ways to go to the place where customers

want to go.

Finally, we have to create databases. If they are invalid, system cant work properly. We can only

store information in the databases.

3. ADDITIONAL MATERIAL

3.1 REFERENCES

3.1.1 Websites:

www.google.com
www.wikipedia.org

3.2.1 Documents:

Documentation.pdf
IEEE- 830.pdf
Software Engineering Seventh Edition Ian Sommerville
Note: All documents are provided by our department.

13