Air Ticket Booking System SRS

Software Requirements Specifications
(SRS) – Air Ticket Booking System

Software Requirements Specifications (SRS)
Version 1.2
Private
DOCUMENT INFORMATION
Category Information
Document Software Requirements Specifications (SRS)
Author(s) Amna Maqbool
Status Approved
Reviewer(s)
Approver(s)
Issue Date
Distribution Development Team, Project Team
DOCUMENT REVISION HISTORY
Author Date Version Description Rationale

Version 1.2
Private
Table of Contents
Section 1 Introduction ................................................ 3
1.1 Purpose ................................................ 3
1.2 Scope .................................................. 3
1.3 Problem Statement ...................................... 3
1.4 Client Needs ........................................... 3
1.5 Business Processes ..................................... 4
1.6 Solution Summary ....................................... 4
1.7 Assumptions ............................................ 4
Section 2 Description ................................................ 4
2.1 Functional Requirements ................................ 4
2.1.1 Requirement No.1 .................................... 4
2.1.2 Requirement No.2 .................................... 6
2.1.3 Requirement No.3 .................................... 7
2.1.4 Requirement No.4 ................................... 12
2.1.5 Requirement No.5 ................................... 15
2.1.6 Requirement No.6 ................................... 16
2.1.7 Requirement No.7 ................................... 19
2.1.8 Requirement No.8 ................................... 20
2.1.9 Requirement No.9 ......... Error! Bookmark not defined.
2.1.10 Requirement No.10 ...... Error! Bookmark not defined.
2.1.11 Requirement No.11 ...... Error! Bookmark not defined.
2.2 System Interfaces ................................... 22
2.3 Non-Functional Requirements ........................... 22
2.3.1 Performance ........................................ 22
2.3.2 Maintainability .................................... 22
2.3.3 Efficiency ......................................... 22
2.3.4 Interoperability ................................... 22
2.3.5 Reusability ........................................ 22
2.4 Quality Attributes .................................... 23
2.4.1 Correctness ........................................ 23
2.4.2 Availability ....................................... 23
2.4.3 Usability .......................................... 23
2.5 Abbreviations & Acronyms .............................. 23
Version 1.2
Private
Section 1 Introduction
1.1 Purpose
Purpose of this document is to describe all the requirements required to build an online system to
manage flights and passengers to east the flight management. It will help end users and
development team to understand what is actually required in order to deliver a system in one go.
This document contains all the functional and non-functional requirements to be developed and
tested.
1.2 Scope
This document covers all the requirements for the online flight management system to ease flight
management and to create a convenient and easy to use application for passengers, trying to buy
online tickets. This online system will help the customers to search the availability of tickets. This
online system will also cover features like:
 Online registration of users
 Modifying the details of system by system administrator/system manager
1.3 Problem Statement

People often want to book their seats/tickets online to travel around. Most of the time they need to
go to booking offices for this purpose which is a hectic job to do these days. With world converting
into a global space, there is a dire need of a system where people may reserve and buy their
seats/tickets online in just a few clicks. Although many such online systems exits, but there is not
a single system which facilities web and mobile (Android & IOS) users simultaneously.
1.4 Client Needs

An automated flight booking system (web and mobile app) where users can reserve and buy their
tickets online to travel around. This online system will also be used by system administrators to
facilitate customers
 by adding, deleting or modifying the customer details
 by adding, deleting or modifying flights or packages information
1.5 Intended Audience

This project is mainly intended for two types of audiences. One is the customer or the end-user
and the other is the administrator of the website.
Version 1.2
Private
1.6 Business Processes

1. Login
2. Latest Flight Deals
3. Flexible Fare Choices
4. Facilities
5. Where We Fly
6. Quick Links
1.7 Solution Summary

A new online system needs to develop with such a composite requirement. System will be in form
of a web app and mobile app (Android & IOS), which will allow users to reserve their tickets
online using a single platform. Users can search for latest flight deals, facilities being provided to
them during flight and flexible fare choices. System administrator can add, delete and modify
customer details and flight related information.
1.8 Assumptions
Following assumptions are considered before implementing the solution:
 Users have working internet connection and have basic knowledge of computer and/or
mobile
 System administrator are aware of computer and/or mobile and have working internet
connection.
Section 2 Description
2.1 Functional Requirements
All the functional requirements are described in detail as following:
2.1.1 Requirement No.1

Like all the other airline websites available online, the user can access the home page of the online
system. At home page, user can look up information regarding flights, deals and packages.
Version 1.2
Private
2.1.1.1 Screen Layout
Figure 1
Figure 2
Version 1.2
Private
2.1.1.2 Business Rules

 User can access the home page of flight reservation system by using URL.
 User can access the home page of the flight reservation system by downloading app on IOS
and/or Android operating system.
 User can access home page only when he has stable internet connection available.
2.1.1.3 Requirements Priority
Very High

This function allows a registered user to login his account using his username and password. If a
user is not registered, the system shall allow the user to register himself using ‘Register Now’
button as shown in figure 3.
Figure 3
Figure 4
Version 1.2
Private

 Username and Password are mandatory fields.
 Username must be unique.
 When users presses ‘Sign In’ without entering username and password, system should
prompt user to enter username and password.
 System should validate if “Username” is already registered.
 Password should be 8 characters longer and mix with upper and lower case letters and
numbers.
 Username must be 6 characters long and should not allow special characters.
 Password should be encrypted in password field.

Very High

User can use the ‘Flight’ option, as shown in figure 5, to book flights using online flight
management system. The system shall present the user with information on all current flights. The
user may then select a pair (from and to) of flights on which to purchase seats. The user can also
select a pair of dates (departure date and return date) of flights on which to purchase seats. Finally,
the system shall guide the user to complete the process by using ‘Find Flight’ option.
Figure 5
Version 1.2
Private
Figure 6
Figure 7
Version 1.2
Private
Figure 8
Figure 9
Version 1.2
Private
Figure 10
Figure 11
Figure 12
Version 1.2
Private
Figure 13
Figure 14
 By using ‘Select Your Destination’ option, user will enter ‘From’ and ‘To’ city as shown
in figure 6 and 7.
 By using ‘Select Your Dates’ option, user will enter ‘Departure Date’ and ‘Return Date’
as shown in figure 8 and 9.
 User using ‘Cabin’ option, user will select cabin against which he wants to view flight
details as shown in figure 10.
 Following cabin options will be available in the system:
a. All
b. Economy
c. Executive Economy
d. Business
 By using ‘Guest’ option, user will select his guests as shown in figure 11.
 By using ‘Book Your Flight’ option, user will select his flight option as shown in figure
12. Following flight options will be available in the system:
a. Return
b. One Way
c. Multicity
Version 1.2
Private
 By using ‘Find Flight’ option as shown in figure 13, user will be able to search all the
available flights against the information provided by him.
 All the available option against provided information will be displayed on screen as shown
in figure 14.

Very High

User can use the ‘Schedule’ option, as shown in figure 15, to query flight schedules based upon
simple input criteria. If any flights match the criteria, the system will display information.
Figure 15
Version 1.2
Private
Figure 16
Figure 17
Version 1.2
Private
Figure 18
Figure 19
Figure 20
Version 1.2
Private

 By using ‘Select Your Destination’ option, user will enter ‘From’ and ‘To’ city as shown
in figure 16 and 17.
 By using ‘Select Your Dates’ option, user will enter ‘Departure Date’ as shown in figure
18.
 By using ‘Proceed’ option, as shown in figure 19, user will be able to see all the available
flights against information provided by him.
 All the available option against provided information will be displayed on screen as shown
in figure 20.

Very High

User can use the ‘Web Check-In’ option, as shown in figure 21. Web check-in is an online process
by which passenger(s) will be able to check-in through the flight management system’s website
prior to their arrival at the airport.
Figure 21
Figure 22
Version 1.2
Private
Figure 23

 By entering ‘PNR’ and ‘Surname’, user will be able to check-in prior to his arrival.
 ‘Enter PNR’ and ‘Enter Your Surname’ will be mandatory fields to proceed with ‘web
check-in’ option as shown in figure 22.
 By using ‘Check In’ option, as shown in figure 23, user will be able to perform check-in
before reaching the airport to save his time.

Very High

User can use the ‘Flight Status’ option, as shown in figure 24, to view flight information that
matches input criteria. ‘Flight Status’ option will help user to know whether ‘departure time’ and
‘arrival time’ are according to schedule or not.
Figure 24
Version 1.2
Private
Figure 25
Figure 26
Figure 27
Version 1.2
Private
Figure 28
Figure 29
Version 1.2
Private

 By using ‘Airport City’ option, user will enter the city from where he will be flying as
shown in figure 25.
 By using ‘Departing On’ option, user will enter the departure date on which he will be
flying as shown in figure 26.
 By using ‘Proceed’ option, as shown in figure 27, user will be able see details of flight as
per provided information.
 After clicking ‘Proceed’ button user will be able to see all the departure and arrival details
against his query as shown in figure 28 and 29.

High

Users shall be able to see popular carmakers on home page of the website.
Figure 30
Figure 31
Figure 32
Version 1.2
Private

 By using ‘My Booking’ option, user will be able to view his booking details as shown in
figure 30.
 By entering ‘PNR’ and ‘Surname’, user will be able to view his detailed booking
information as shown in figure 31.
 ‘Enter PNR’ and ‘Enter Your Surname’ will be mandatory fields to proceed with ‘My
Booking’ option.
 By using ‘View Booking’ option, as shown in figure 32, user will be able see detailed
information about his booking based on inputs provided.

High

User can view the ‘Latest Flight Deals’ on home page of flight management system.
Figure 33
Version 1.2
Private

 All the latest flight deals will be available flight management system’s home page.
 User will be able to see details about latest deals based on his choice.

Medium
Version 1.2
Private
2.2 System Interfaces

2.2.1.1 User Interfaces
Users will interact with the system through an application that can be accessed through computer
and/or mobile.
2.2.1.2 Software Interfaces
System will use .Net on front end and MySQL on backend as database.
2.3 Non-Functional Requirements

2.3.1 Performance
 System should search specific cars within 3 seconds.
 Response time of the system should be less than 2 second most of the time.
 System shall be able to handle at least 1000 transactions/inquiries per second.
 System shall show no visible deterioration in response time as the number of users or flight
schedule data increases.
2.3.2 Maintainability
 The administrators and flight in chargers should maintain correct schedules of flights.
 Proper user messages should be shown to user in case of exceptions.
2.3.3 Efficiency
System should be able to handle 100000 users at a time.
2.3.4 Interoperability
This new system shall minimize the effort required to couple it to another system, such as flight
schedule database system.
2.3.5 Reusability
90% of the components of the web app and mobile app should be reusable in any other similar
kind of system.
Version 1.2
Private
2.4 Quality Attributes

2.4.1 Correctness
 The flight should start from correct start terminal and should reach the correct destination.
 System should search all the flights available in the system that matched with search string.
2.4.2 Availability
The flight should be available on the specified date and specified time as many customers are doing
advance reservations.
2.4.3 Usability
 The flight schedules should satisfy a maximum number of customer’s needs.
 The web interface should be intuitive and easily navigable. Users should be able to
understand the menu and options provided by the system.
 The mobile interface should be intuitive and easily navigable. Users should be able to
understand the menu and options provided by the system.
 The system shall provide an easy-to-use graphical interface similar to other existing
reservation system so that the users do not have to learn a new style of interaction.
2.5 Abbreviations & Acronyms

Abbreviations & Acronyms Full Form
SRS Software Requirements Specifications
Table 1: Abbreviations & Acronyms

Air Ticket Booking System SRS

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Air Ticket Booking System SRS

Hochgeladen von

Copyright:

Verfügbare Formate

Software Requirements Specifications

(SRS) – Air Ticket Booking System

DOCUMENT REVISION HISTORY

Author Date Version Description Rationale

1.3 Problem Statement

1.4 Client Needs

1.5 Intended Audience

1.6 Business Processes

1.7 Solution Summary

2.1.1 Requirement No.1

2.1.1.1 Screen Layout

2.1.1.2 Business Rules

2.1.2 Requirement No.2

2.1.2.1 Screen Layout

2.1.2.2 Business Rules

2.1.2.3 Requirements Priority

2.1.3 Requirement No.3

2.1.3.1 Screen Layout

2.1.3.3 Requirements Priority

2.1.4 Requirement No.4

2.1.4.1 Screen Layout

2.1.4.2 Business Rules

2.1.4.3 Requirements Priority

2.1.5 Requirement No.5

2.1.5.2 Business Rules

2.1.5.3 Requirements Priority

2.1.6 Requirement No.6

2.1.6.2 Business Rules

2.1.6.3 Requirements Priority

2.1.7 Requirement No.7

2.1.7.1 Screen Layout

2.1.7.2 Business Rules

2.1.7.3 Requirements Priority

2.1.8 Requirement No.8

2.1.8.2 Business Rules

2.1.8.3 Requirements Priority

2.2 System Interfaces

2.2.1.2 Software Interfaces

2.3 Non-Functional Requirements

2.4 Quality Attributes

2.5 Abbreviations & Acronyms

Das könnte Ihnen auch gefallen