See discussions, stats, and author profiles for this publication at: [Link]
net/publication/363283919
Online Bus Ticket Reservation System - Software Requirements Specification
Document
Technical Report · April 2021
CITATIONS READS
0 376
1 author:
Isuru Adhikari
MAS Holdings
6 PUBLICATIONS 1 CITATION
SEE PROFILE
All content following this page was uploaded by Isuru Adhikari on 05 September 2022.
The user has requested enhancement of the downloaded file.
Software Requirements Specification Document for
Online Bus Ticket
Reservation System
Prepared by PEP_014
Name Registration No.
Adhikari A M I Y IT20209698
Dasanayaka U D P M IT19006376
Ranathunga R M S S IT20218676
Wijekumara N W D H IT20181956
Submitted to
Sri Lanka Institute of Information Technology
Table of Contents
1. Introduction ..............................................................................................................................1
1.1 Purpose ........................................................................................................................................ 1
1.2 Document Conventions ............................................................................................................... 1
1.3 Intended Audience and Reading Suggestions.............................................................................. 1
1.4 Product Scope .............................................................................................................................. 2
1.5 References ................................................................................................................................... 2
2. Overall Description ..................................................................................................................3
2.1 Product Perspective ..................................................................................................................... 3
2.2 Product Functions ........................................................................................................................ 3
2.3 User Classes and Characteristics ................................................................................................. 3
2.4 Operating Environment ............................................................................................................... 3
2.5 Design and Implementation Constraints...................................................................................... 4
2.6 Assumptions and Dependencies .................................................................................................. 4
3. External Interface Requirements ...........................................................................................5
3.1 User Interfaces ............................................................................................................................. 5
3.2 Software Interfaces ...................................................................................................................... 6
3.3 Communications Interfaces ......................................................................................................... 6
4. System Features .......................................................................................................................7
4.1 System Feature 1: Functional requirements ................................................................................ 7
4.1.1 Passenger side Requirements .................................................................................................. 7
4.1.2 Booking a Seat ........................................................................................................................ 8
4.1.3 Owner Side requirements ........................................................................................................ 9
4.2 System Feature 2: Use Case Diagrams, Use Case Scenarios ...................................................... 9
4.3 Activity Diagram ....................................................................................................................... 11
4.3.1 Client sided activity diagram................................................................................................. 11
4.3.2 Passenger sided activity diagram .......................................................................................... 12
5. Other Nonfunctional Requirements .....................................................................................13
5.1 Performance Requirements........................................................................................................ 13
5.2 Safety Requirements .................................................................................................................. 13
5.3 Security Requirements............................................................................................................... 13
5.4 Software Quality Attributes ....................................................................................................... 14
5.5 Business Rules ........................................................................................................................... 14
5.6 Rough Schedule for the project development ............................................................................ 14
Appendix A: Glossary..................................................................................................................14
Appendix B: Analysis Models .....................................................................................................16
PEPIM_014 – Online Bus Reservation System
1. Introduction
1.1 Purpose
The purpose of the document is to collect and analyze all assorted ideas that have come up to define
the system, its requirements with respect to consumers. Also, we shall predict and sort out how we
hope this product will be used to gain a better understanding of the project, outline concepts that
may be developed later, and document ideas that are being considered, but may be discarded as the
product develops.
In short, the purpose of this SRS document is to provide a detailed overview of our software
product, its parameters, and goals. This document describes the project's target audience and its user
interface, hardware, and software requirements. It defines how our client, team and audience see the
product and its functionality. Nonetheless, it helps any designer and developer to assist in software
delivery lifecycle (SDLC) processes. [5]
1.2 Document Conventions
When creating the SRS document, the type of font used for the headers is Times New Roman (bold)
and the font size is 14. The type of font for the content is Times New Roman and the font size is 12.
This SRS report is created according to the IEEE standards.
1.3 Intended Audience and Reading Suggestions
This document is intended for programmers, developers, marketing stuff, and users involved in the
website modification of the Online Bus Ticket Reservation system. This report consists of the
various steps and procedures for the website development initiated with an open discussion
with the client. Following section describes the rest of the project and its purposes.
Software Requirement Specification 1
PEPIM_014 – Online Bus Reservation System
1.4 Product Scope
Online ticket reservation system will be the best solution for the bus owners with the Covid-19
travel restrictions. This is a website which enables passengers to view a bus and book the ticket by
their own. A passenger has given the chance to book his desired seat by the remaining seats.
1.5 References
[1] w3school, "HTML Tutorial," [Online]. Available: [Link]
[2] w3school, "CSS Tutorial," [Online]. Available: [Link]
[3] w3school, "PHP Tutorial," [Online]. Available:
[Link]
[4] Bikin, "Bootstrapmade," [Online]. Available: [Link]
[5] L. A. F. Werneckei, D. A. Rezende and T. A. Guimarães, "ScienceDirect," 02 Jun 2021.
[Online]. Available: [Link]
Software Requirement Specification 2
PEPIM_014 – Online Bus Reservation System
2. Overall Description
2.1 Product Perspective
In this Covid-19 situation, bus owners and passengers have faced the problem where only limited
number of passengers are allowed to travel on a single bus. It would be more convenient if
passengers can book their seat tickets from home. This project will solve these needs. Online ticket
reservation system will be the best solution for the bus owners with the Covid-19 travel restrictions.
This is a website which enables passengers to view a bus and book the ticket by their own. A
passenger has given the chance to book his desired seat by the remaining.
2.2 Product Functions
• Bus management- It can manage the buses and their routes, timetables.
• Customer management- Customers can be added or removed with admin privileges.
• Employee management- Manage employees who can access the website.
• Booking / Payment management- Booking is fully online and payments either online or at
the tour.
2.3 User Classes and Characteristics
Client
• Add, remove, update, and modify Buses, Routes and Bookings.
• Add, remove, update, and modify Users.
• View booking records.
Passenger
• View buses, routes, and scheduled times.
• Book tickets.
2.4 Operating Environment
A Windows 7 or above operating system is required to operate a web browser like Chrome or
Firefox, to access the website through the internet. Hardware requirements such as minimum of
4GB of RAM with an Intel Core i5 processor and hard disk space of 10GB.
Software Requirement Specification 3
PEPIM_014 – Online Bus Reservation System
2.5 Design and Implementation Constraints
This system is built on Bootstrap, jQuery, and [Link] this project developed by undergraduates,
the resources and time are limited. Therefore, use of third-party resources are limited only to the
free and open-source resources.
2.6 Assumptions and Dependencies
• This is developed assuming its users do not have high computer literacy as well as
English language literacy. But they must be able to communicate up to certain level in
English language, and basic knowledge of using internet is required.
• If there will be any hardware issue or external influences the system will depend on it. It
may be not work properly.
• Users’ devices must have an internet plan to access the internet.
• Client must have a 24/7 network connection.
Software Requirement Specification 4
PEPIM_014 – Online Bus Reservation System
3. External Interface Requirements
3.1 User Interfaces
A complete website achieving all client requests will be developed and launched as expected. This
website is developed with a user-friendly clean interface where passengers can select the bus, view
the drivers, view destinations, and book a seat/s. Users do not require to have an intensive level
knowledge on computer literacy as well as language literacy to use this application. [1] [2]
Sketch of the website is as follows:
Software Requirement Specification 5
PEPIM_014 – Online Bus Reservation System
3.2 Software Interfaces
• Bootstrap is a free and open-source CSS framework directed at responsive, mobile-first
front-end web development. It contains CSS- and JavaScript-based design templates for
typography, forms, buttons, navigation, and other interface components. [4]
• jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML
document traversal and manipulation, event handling, animations much simpler with an
easy-to-use API that works across a multitude of browsers.
• PHP (Hypertext Preprocessor) is known as a general-purpose scripting language that can be
used to develop dynamic and interactive websites. It was among the first server-side
languages that could be embedded into HTML, making it easier to add functionality to web
pages without needing to call external files for data. [3]
• MySQL is an open-source relational database management system. "SQL", the abbreviation
for Structured Query Language
3.3 Communications Interfaces
• A web browser is used to access the website
• HTTPS is used as the communication protocol.
• Contact form is used which will redirect to personal email through domain email.
Software Requirement Specification 6
PEPIM_014 – Online Bus Reservation System
4. System Features
4.1 System Feature 1: Functional requirements
4.1.1 Passenger side Requirements
Description and Priority
In the homepage contains a brief description about the Online bus ticket reservation system such as
bus details contact numbers and driver details.
Priority level: High
REQ-1 Enter the Website through browser
Input Click the URL
Process Loading system main page
Output Accessing the homepage
Definition Display the Details of Webpage
REQ-2 View Bus Details
Input Click the Bus details button
Process Loading the bus detail page
Output Showing Bus Details
Definition Display the Details of Available busses
REQ-3 View Driver’s Details
Input Click the Our Driver details button
Process Loading the Driver details page
Output Showing Driver’s Details
Definition Display the Details of Drivers
Software Requirement Specification 7
PEPIM_014 – Online Bus Reservation System
REQ-4 View Contact Details
Input Click the Contact details button
Process Loading the Contact details page
Output Showing Contact Details
Definition Display the Contact Details
4.1.2 Booking a Seat
Description and priority
After selecting the bus passenger can book a seat
Priority level: high
REQ-1 Book a seat
Input Click the Book your seat button
Process Load the booking page
Output Display the fields to enter details
Definition Taking passenger details to book a seat
REQ-2 Save passenger booking details
Input the necessary details and click submit
Input button
Process Save all details in database
Output -
Definition Storing booking details
Software Requirement Specification 8
PEPIM_014 – Online Bus Reservation System
4.1.3 Owner Side requirements
Description and priority
Priority level: high
REQ-1 Manage all booking and bus details
Input Click the Admin button
Process Load the admin page
Output Display fields to enter username and password
Definition Display all details about busses and bookings
4.2 System Feature 2: Use Case Diagrams, Use Case Scenarios
Software Requirement Specification 9
PEPIM_014 – Online Bus Reservation System
Use Case Number 01
Use case Name Booking a seat
Pre-Condition User should have a NIC and Phone number
Actor Passenger
Main Scenario Step Action
1 Entering Book, a seat page
2 Filling relevant details
3 Submitting the booking details
Extension 2.1 System shows no busses according to the given details
Use Case Number 02
Use case Name Adding/updating/deleting Bus and route details to the system
Pre-Condition User should have a username and Password
Actor Client (Bus Owner)
Main Scenario Step Action
1 Entering the login details
2 Choosing the relevant filed to change
3 Submitting the new details or removing current details
Extension 2.1 System indicates error message
Software Requirement Specification 10
PEPIM_014 – Online Bus Reservation System
4.3 Activity Diagram
4.3.1 Client sided activity diagram
Software Requirement Specification 11
PEPIM_014 – Online Bus Reservation System
4.3.2 Passenger sided activity diagram
Software Requirement Specification 12
PEPIM_014 – Online Bus Reservation System
5. Other Nonfunctional Requirements
5.1 Performance Requirements
• Efficient
I. This newly created webpage is fast and efficient for the betterment of usage
among customers and bus holders.
II. The website always available when the user visits the webpage.
III. It already quickly response to the user.
IV. User can easily enter their details using any type of device.
V. Our system is covered all national wide routes.
• Large scale data handling
I. All submitted data will be stored in a pre-defined database in the system. It has
ability to reduce data redundancy. All entered data will be stored in organized
database pattern.
5.2 Safety Requirements
• Users must enter their personal details to the system for book a ticket. So, the provided
details are secured within a database. Especially these entered details can only access by the
admin of the system. It will guarantee the user’s privacy.
5.3 Security Requirements
• Database created to store all details which are related for users and it will be maintained
privately.
• User has a special login process to access the system and perform their tasks. Only particular
use can access it.
• All other sensitive data shouldn’t be exposed to the common interface of the system.
Software Requirement Specification 13
PEPIM_014 – Online Bus Reservation System
5.4 Software Quality Attributes
• Reliability – User identification is a must for this system. Because user’s details need to be
accurate.
• Adaptability - Due to this pandemic situation transportation has to more secure service for
customers. They aren’t needed to physically interfere for the transportation methods, but
they can easily do it with their own devices.
• Cost effective – This system is designed with a reasonable budget in order to reduce
• Maintainability – The admin of the system is responsible for maintain new busses and routes
according to the customer’s feedback.
5.5 Business Rules
• There are 2 main types of users in this system – Customer & Client
• Customer can book one or more bookings via this.
5.6 Rough Schedule for the project development
12-Jul 1-Aug 21-Aug 10-Sep 30-Sep
Topic assuming
Project Charter
Project Proposal
Analysis requirement
SRS Document
Design
Development
Project Progress
Final Evaluation
Start Date Duration
Software Requirement Specification 14
PEPIM_014 – Online Bus Reservation System
Appendix A: Glossary
• Flow of the Project – A diagram which use to plan the flow of the project into timestamps.
Software Requirement Specification 15
PEPIM_014 – Online Bus Reservation System
Appendix B: Analysis Models
Flow of the project
Software Requirement Specification 16
View publication stats
