Professional Documents
Culture Documents
OnlineBusTicketReservationSystem SRS
OnlineBusTicketReservationSystem SRS
net/publication/363283919
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.
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]
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.
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.
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
2. Overall Description
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.
• 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.
Passenger
• View buses, routes, and scheduled times.
• Book tickets.
This system is built on Bootstrap, jQuery, and PHP.As 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.
• 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.
4. System Features
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
Actor Passenger
Use case Name Adding/updating/deleting Bus and route details to the system
• 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.
• 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.
• 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.
• 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.
• There are 2 main types of users in this system – Customer & Client
• Customer can book one or more bookings via this.
Topic assuming
Project Charter
Project Proposal
Analysis requirement
SRS Document
Design
Development
Project Progress
Final Evaluation
Start Date Duration
Appendix A: Glossary
• Flow of the Project – A diagram which use to plan the flow of the project into timestamps.