ONLINE BUS TICKET RESERVATION SYSTEM

(OBTRS)
SRS Document

By : TEAM 1
Prathaam Modi
Amisha Agrawal
Tejodeep Bose
 TABLE OF CONTENTS
1. INTRODUCTION .....................................................................................................................4

1.1 ..PURPOSE .................................................................................................................5

1.2 ..SCOPE ........................................................................................................................6

1.3 ..DEFINITIONS, ACRONYMS AND ABBREVIATIONS...................................................6

1.4 ..REFERENCES.............................................................................................................7

1.5 ..OVERVIEW...................................................................................................................7

2. OVERALL DESCRIPTION ...........................................................................................................8

2.1 PRODUCT PERSPECTIVE..................................................................................................10

2.1.1 SYSTEM INTERFACES ....................................................................................................10

2.1.2 USER INTERFACES.........................................................................................................10

2.1.3 HARDWARE INTERFACES ..............................................................................................11

2.1.4 SOFTWARE INTERFACES.................................................................................................11

2.1.5 COMMUNICATION INTERFACES.....................................................................................12

2.1.6 MEMORY CONSTRAINTS...............................................................................................12

2.1.7 OPERATIONS ................................................................................................................13

2.1.8 SITEADAPTATION..........................................................................................................13

2.2 PRODUCT FUNCTIONS.....................................................................................................13

2.3 USER CHARACTERISTICS...................................................................................................14

2.4 CONSTRAINTS.................................................................................................................14

2.5 ASSUMPTIONS AND DEPENDENCIES................................................................................15

2.6 APPORTIONING OF REQUIREMENTS ...............................................................................15

3. SPECIFIC REQUIREMENTS.......................................................................................................16

3.1 EXTERNAL INTERFACE REQUIREMENTS................................................................16

3.2 FUNCTIONAL REQUIREMENTS ..............................................................................17

3.2.1 FUNCTIONS..............................................................................................17

3.3 PERFORMANCE
REQUIREMENTS.............................................................................................18

3.4 DESIGN CONSTRAINTS .........................................................................................................19

3.5 SOFTWARE SYSTEM ATTRIBUTES.........................................................................................19

3.5.1 RELIABILITY .......................................................................................................................19

3.5.2 AVAILABILITY....................................................................................................................19

3.5.3 SECURITY..........................................................................................................................19

3.5.4 MAINTAINABILITY .............................................................................................................20

3.5.5 PORTABILITY ....................................................................................................................20

3.6 OTHER REQUIREMENTS ......................................................................................................20

4. APPENDIX.............................................................................................................................20

4.1 USE CASES..........................................................................................................................21

4.2 ..STATE DIAGRAMS.............................................................................................................24

According to the IEEE Std. 830-1998, IEEE Standard for

Software Requirements Specifications, the first version of
the requirements document was prepared on October 22,
2020.
 Preface

The document contains the Software Requirements Specification of ONLINE BUS

TICKET RESERVATION SYSTEM (OBTRS), which can be used for the all of the
internet users. The Ticket Reservation System is an Internet based application
that can be accessed throughout the Net and can be accessed by any one who
has a net connection. This application will automate the reservation of tickets
and Enquiries about availability of the tickets. This application includes email
information for the tickets.

The Goal of the Software Requirement Specification is to describe overall

functionality of the ONLINE BUS TICKET RESERVATION SYSTEM. This system is
prepared according to IEEE standard [2]. The Software Requirements
Specification is in content compliance with the IEEE standard 830-1998 in which
the contents of this standard are rearranged and a mapping is provided. That is,
the content compliant Software Requirements Specification is mapped into
various clauses and sub clauses of the IEEE standard 830-1998.

The requirements that are stated in this document will determine the final
product and its functionality. This document will also be used to evaluate the
success of the project.
 1. INTRODUCTION

1.1 PURPOSE

The purpose of the Software Requirements Specification document is to

maintain all the functions and the specifications of the Online Bus Ticket
Reservation System.
Besides, it contains the detailed descriptions of all the requirements specified
before.
1.2 SCOPE
The scope of the OBTRS is:
1. A person should be able to
• Login to the system through the first page of the application
• Change the password after logging into the system
• Should be able to create a new login for the accessing the reservation
facility.
• Query the buses for two weeks (Only two weeks advance reservation
is available).
• No reservation before two days can be done.
• See his/her current reservations on different buses along with the
details.
• Able to choose the seats which can are available for a certain class.
• Give details about the details about the credit card details.
2. A mail should be send to the concerned person about the confirmation of the
ticket to the specified email address.
3. The login Id and password should be sent to the mentioned email address if a
new account is created.
4. A calendar should be there which helps the person to select dates. It should
also show the public and nation holidays.
5. The system should automatically show the fare for the corresponding seat
and
amount of money needs to be pay for selected seats.
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
Acquirer: specifies requirements for and accepts delivery of a new or modified
software product and its documentation.
Administrator: The one who manages and maintains computer systems and
software.
Calendar: it is a tool which user enters monthly program
ONLINE BUS TICKET RESERVATION SYSTEM (OBTRS): The project
name.
FAQ: Frequently Asked Questions.
b: Institute of Electrics & Electronics Engineering
IS: Information Systems
IT: Information Technology
Marquee: A piece of text that scrolls across a browser document window.
SDD: Software Design Document
Server: The main computer on a network.
SPMP: Software Project Management Plan
SRS: Software Requirements Specification
Staff: The people who works for Red Bus Company.
Team: The name of the developer group.
User: People who open the OBTRS web site and the administrator of the OBTRS
web site.
Web: the network of computers that forms the Internet
FERSOFT: Fast Efficient Reliable Software Company

1.4 REFERENCES
[1] IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans
[2] IEEE STD 830-1998, IEEE Recommended Practice for Software Requirements
Specifications
[3] IEEE STD 1016-1998, Recommended Practice for Software Design
Descriptions
[4] Pressman, Roger S., Software Engineering “A Practitioner’s Approach”, Fifth
Edition, McGraw-Hill, 2000.
[5] http://httpd.apache.org/
[6] http://www.macromedia.com
[7] http://www.mysql.com/
[8] http://www.mozilla.org/
[9]http://libresoft.urjc.es/debiancounting/
sarge/index.php?menu=Package&package=sloccount we will use PHP in our
project.
[10] http://www.microsoft.com

1.5 OVERVIEW
After giving a brief introduction about the project, the body of the report is
divided into two parts. They are;
• The 2nd chapter contains a full description of the functions, their properties,
their aims, the constraints and the requirements of the project.
• The last chapter consists of the details of the functions and function
constraints.
2. OVERALL DESCRIPTION
This section describes the functions of the project and their aims. It also includes
the constraints and the requirements of the project.

2.1 PRODUCT PERSPECTIVE

Online Bus Ticket Reservation System provides a group of works with interface
environments. Also there will be a database which will keep all the records that
done by user while visiting the page.

2.1.1 SYSTEM INTERFACES

Online Bus Ticket Reservation System is connected with company server
database, thus no more connection with other systems is needed. No system
interface is needed during the development of this project.

2.1.2 USER INTERFACES

The OBTRS shall be designed as a web based that has a main user interface.
Format of main screen shall be standard and flexable. The system shall be user
friendly designed.
Pages shall be connected each other in a consistent way. Operations can be done
with the system shall be repeatable. The design of the pages should allow users
to do this.
2.1.3 HARDWARE INTERFACES
There is no need any hardware interface for Online Bus Ticket Reservation
System.
2.1.4 SOFTWARE INTERFACES
1. There are 2 product options for viewing:
A. Name: Microsoft Internet Explorer
Mnemonic: -
Specification number: -
Version number: 5.5
Source: Microsoft Corporation, the interface of the OBTRS is welldocumented
and can be found at [10].
Purpose: The web browser specified above is required as the container of the
client software at the client site in order to execute the client site of OBTRS.
Definition of the Interface: The Microsoft Internet Explorer is the software,
provides a flexible and reliable browsing experience with enhanced Web
privacy features for all users.
OR
B. Name: Mozilla Firefox
Mnemonic: -
Specification number: -
Version number: 2.0
Source: Mozilla Foundation, the interface of the OBTRS is well-documented
and can be found at [8].
Purpose: The web browser specified above is required as the container of the
client software at the client site in order to execute the client site of OBTRS.
Definition of the Interface: The Mozilla Firefox Browser is the software,
provides a flexible and reliable browsing experience with enhanced Web
privacy features for all users.
2. Name: Apache HTTP Server
Mnemonic: -
Specification number: -
Version number: 2.0.5.5
Source: The Apache Software Foundation, the interface of the OBTRS with
the application system is well-documented and can be found at [5].
Purpose: In order to execute the client site of OBTRS, the web server
specified above is required as the provider of the client software at the server
site.
Definition of the Interface: The Apache HTTP Server Project is an effort to
develop and maintain an open-source HTTP server for modern operating
systems including UNIX and Windows NT. The goal of this project is to
provide a secure, efficient and extensible server that provides HTTP services
in sync with the current HTTP standards.
3. Name: PHP
Mnemonic: -
Specification number: -
Version number: 4.0
Source: PHP Group, the interface of the OBTRS is well-documented and can
be found at [9].
Purpose: In order to build web pages which work with MySQL database and
Apache server?
Definition of the Interface: PHP is a widely-used general-purpose scripting
language that is especially suited for Web development and can be embedded
into HTML.
4. Name: Macromedia Dreamweaver
Mnemonic: -
Specification number: -
Version number: 8
Source: Macromedia Inc., the interface of the OBTRS is well-documented
and can be found at [6].
Purpose: The web development tool specified above is required for designing
and coding the project.
Definition of the Interface: Macromedia Dreamweaver is the industryleading
web development tool, enabling users to efficiently design, develop
and maintain standards-based websites and applications.
6. Name: MySQL
Mnemonic: -
Specification number: -
Version number: 5.0
Source: MySQL document defining the interface can be found at [7].
Purpose: Required as database server.
Definition of the Interface: MySQL is the world's most popular open source
database software, with over 100 million copies of its software downloaded or
distributed throughout its history. With superior speed, reliability, and ease of
use, MySQL has become the preferred choice of corporate IT Managers
because it eliminates the major problems associated with downtime,
maintenance, administration and support.
2.1.5 COMMUNICATION INTERFACES
The default communication protocol for data transmission between server and
the client is Transmission Control Protocol/ Internet Protocol (TCP/IP). At the
upper level
Hyper Text Transfer Protocol (HTTP, default port=80, default of apache
port=8080) will
be used for communication between the web server and client.
2.1.6 MEMORY CONSTRAINTS
There is not a specific memory constraint for OBTRS.
2.1.7 OPERATIONS
Company database backup and recovery operations should be done by Fersoft
support team. A full system backup will be done once a month. If any update or
modification required on system like interfaces, new specialties; Fersoft project
group
and the acquirer will make a new meeting. The detailed operations are defined
in User
Interfaces chapter.
2.1.8 SITE ADAPTATION
The Server has requirements to operate PHP scripts Apache Web server 2.0.5.5
with PHP 4.0.
2.2 PRODUCT FUNCTIONS
OBTRS is:
1. Login to the system through the first page of the application
2. Change the password after logging into the system
3. Should be able to create a new login for the accessing the reservation facility.
4. Query the buses for two weeks (Only two weeks advance reservation is
available).
5. No reservation before two days can be done.
6. See current reservations on different buses along with the details.
7. Able to choose the seats which can are available for a certain class.
8. Give details about the details about the credit card details.
9. A mail should be send to the concerned person about the confirmation of the
ticket to the specified email address.
10. The login Id and password should be sent to the mentioned email address if
a new account is created.
11. A calendar should be there which helps the person to select dates. It should
also show the public and nation holidays.
12. The system should automatically show the fare for the corresponding seat
and
amount of money needs to be pay for selected seats.
13. The administrator of the web site should used an admin tool for customize
the
web site.
14. The admin tool shall handle followings:
a) Shall change the logo
b) Shall add or remove links onto the main bar
c) Shall give options for search tools
d) Shall add, remove or update links on the menu
e) Shall add, remove or update events on the event calendar
f) Shall add or remove medias in the content menu
15. Logout from the system.
2.3 USER CHARACTERISTICS
The user types that would use the OBTRS are as follows:
Administrator: Administrators shall usually do anything on the site, in all
pages.
Administrator is responsible for updating and the maintenance of the web site
content such as adding/removing information about the company,
adding/removing links onto the main bar, adding/removing medias in the
content
menu, adding/removing/updating links on the event calendar and the menu,
changing the logo.
 Customer: Customers are people who shall use OBTRS. To use this service
people should have the basic computer using ability. They shall see the buses
information which is belong to current time. User can see all general
information, FAQ can use search.
External Users: External users are people who have not got any user account
for
the web site. They shall use the general information, FAQ.
2.4 CONSTRAINTS
a. Regulatory Policies: There are no regulatory policies.
b. Hardware Limitations: There are no hardware limitations.
c. Interfaces to other Applications: There shall be no interfaces.
d. Parallel Operations: There are no parallel operations.
e. Audit Functions: There shall be no audit functions.
f. Control Functions: There shall be no control functions
g. Higher-order Language Functions: The PHP shall be used for developing the
web pages with the help of Macromedia Dreamveawer. For the database
information, SQL shall be used.
h. Signal Handshake Protocols: This is no signal handshake protocols.
i. Reliability Requirements: Total number of bugs in the system shall not exceed
%1 of the total line number of code, except connection reliability which is out of
our range.
j. Criticality of the Application: The server applications shall be available 365
days.
k. Safety and Security Considerations: The password and a valid username are
the security issues. Data protection shall be satisfied by the back up process at
the server side.
2.5 ASSUMPTIONS AND DEPENDENCIES
The user must have the ability to use the internet.
The user must have connected to the internet to use the system.
The user’s computer must be Windows 95 or later version platforms and
Microsoft Internet Explorer version 5.5 or later
TCP/IP protocol must be installed to communicate through HTTP messages.
The accuracy of the information of users is the responsibility of all users.

2.6 APPORTIONING OF REQUIREMENTS

The requirements that may be delayed until future versions of the OBTRS are as
follows:
• Backup and recovery of the information will not be done in the first version of
the
OBTRS. In the future versions of the OBTRS, these issues will be handled.
When the OBTRS developed in the future handle these requirements, this
subsection of
the corresponding SRS document will be updated
3. SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACE REQUIREMENTS
Interfaces external to the OBTRS can be explained as “User Interfaces”. The
section 2.1.2 User Interfaces provide details of the user interfaces.
3.2 FUNCTIONAL REQUIREMENTS
3.2.1 FUNCTIONS
Use cases and the state transition diagram can be seen at Appendix section. In
order to see the overall view of the system.

3.3 PERFORMANCE REQUIREMENTS

The system performance is adequate. However, OBTRS is working with the user
internet connection, 60% of the performance is up to the client side.
3.4 DESIGN CONSTRAINTS
All documentation of the system shall be prepared related to IEEE standards.
Furthermore, the content shall be compliance with IEEE standards [1, 2 and 3].
3.5 SOFTWARE SYSTEM ATTRIBUTES
3.5.1 RELIABILITY
The system shall operate 95% of the time. The number of defect should not
exceed 10 per function. In addition, before the submission of the final release
the
calendar must be tested in case of the defects over 10 per function.
3.5.2 AVAILABILITY
The availability of the OBTRS is up to the internet connection of the client. Since
this is client-server related web-site, web-site shall be attainable all the time.
User should
have an account to enter the system, if user does not have an account; for the
availability
of the OBTRS user should sign up to the system by clicking the sign up link from
the home page.
3.5.3 SECURITY
The authorization mechanism of the system will block the unwanted attempts
to
the server and also let the system decide on which privileges may the user have.
The
system has different types of users so there are different levels of authorization.
There

will be also a firewall installed on the server so the incoming transactions can be
filtered.
Data integrity for critical variables will also be checked.
3.5.4 MAINTAINABILITY
The requirements, modules that are explained in this document are enough to
satisfy the customers’ needs and wants. In case of a change or addition demand
after
completing the system or in development processes of the system, a new
agreement shall
be done between the acquirer and FERSOFT Dev Group. The maintainability shall
be
easily done by integrating new modules and offering new software solutions for
the
system.
3.5.5 PORTABILITY
The OBTRS is an online service. So, anyone can use the service. One and only the
server of the system must have the required software including MySQL, Apache.
3.6 OTHER REQUIREMENTS
There are no other requirements in this phase. If some extra requirements are
wanted by the customer or acquirer, these are added in this part later