Bicycle Rental System

Software Requirements
Specification
for
RENTAL BICYCLE SYSTEM
Version 1.0 approved
INTAN NAZIEHA RASHIDAH BINTI RASHIDIN (2020987633)
NUR KHAIRUNNISA BINTI KAMAROLZAMAN (2020978369)
NUR AFIQAH BINTI ROSLI (2020965763)
RIDE PARADISE
21 OCTOBER 2021 – 6 FEBRUARY 2022
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii
Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
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 ................................................................................................................................... 3
2. Overall Description ..................................................................................................................3
2.1 Product Perspective ..................................................................................................................... 3
2.2 Product Functions ........................................................................................................................ 4
2.3 User Classes and Characteristics ................................................................................................. 5
2.4 Operating Environment ............................................................................................................... 5
2.5 Design and Implementation Constraints...................................................................................... 6
2.6 User Documentation .................................................................................................................... 6
2.7 Assumptions and Dependencies .................................................................................................. 7
3. External Interface Requirements ...........................................................................................8
3.1 User Interfaces ............................................................................................................................. 8
3.2 Hardware Interfaces................................................................................................................... 13
3.3 Software Interfaces .................................................................................................................... 14
3.4 Communications Interfaces ....................................................................................................... 14
4. System Features .....................................................................................................................15
4.1 Functional Requirements ........................................................................................................... 15
4.2 Other Nonfunctional Requirements ........................................................................................... 22
5. Other Requirements ..............................................................................................................22
Appendix A: Glossary..................................................................................................................23
Appendix B: Analysis Models .....................................................................................................23
Appendix C: To Be Determined List ..........................................................................................25
Revision History
Name Date Reason For Changes Version
Intan Nazieha 21/10/2021 This is just the basic bicycle rental system for 1.0
Rashidah binti Ride Paradise company
Rashidin
Software Requirements Specification for Ride Paradise Bicycle Rental System Page 1
1. Introduction
1.1 Purpose
The purpose of this document is to provide a detailed explanation of a system that has
been created so for our project group, we have created a bicycle rental system that is a system
that involves rental. here we use rental services because of the high demand for bicycle rental
services and have come up with the idea to open a bicycle rental business for visitors or travelers
to visit interesting places around there. therefore, the purpose of this system is to facilitate the
travel of tourists to the destination and provide new experiences for customers. This system is also
created to facilitate customers who want to rent without having to meet with superiors and even
just register and make payment through the staff assistant and customers can use the bicycle that
has been rented.
1.2 Document Conventions

All text contained in this document is 11pt Arial font. Section titles are 18pt Arial font.
Subsection titles is 14pt Arial font. The line paragraph spacing is 1.5. The main headings are
numbered with whole number like 1. introduction 2. overall description. The subheadings are
number with decimal like 1.1 purpose,1.2 document conventions etc.
1.3 Intended Audience and Reading Suggestions

Project managers, developers, testers, marketing staff, users, and documentation writers
should all read the report. The report is organized into 6 parts, 1. Introduction,2. Overall
Description,3. External Interface Requirements,4. System Features,5. Other Nonfunctional
Requirements and 6. Other Requirements. All the parts are independent however reading the
report sequentially helps the reader understand the Bicycle Rental System more neatly and
thoroughly.
1.4 Product Scope
Based on the problem statement given we found that they face some problems with using the bike
without a registration system. Therefore, ride paradise has submitted a registered system for
customers to be more organized during the bike rental. We decided to help them solve the problem.
the first problem that occurs is payment by bank. On this problem we can solve it by doing to our
company, for any rental that occurs we will use manual payment. There are many age groups who
are interested in trying to rent a bicycle but do not know how to pay. it will also waste time waiting
for the payment to be processed. Therefore, payment will be made to the staff in charge so
customers can continue to ride the bike after registration.
In addition, when a city sees more cyclists on the road, it starts a great cycle of progress. To
enable those bicycles, the infrastructure must alter, more bicycle lanes are needed, more cycle paths
are needed. This is because the system used by ride paradise is also a user-friendly system. Here any
problems that occur during or before registering will be resolved with the help of face to face.
therefore, this system is easier to navigate and used by all ages regardless of young or old.
Furthermore, they make the city safer for low-income citizens who rely on bicycles as their major
mode of mobility.
Furthermore, there is no doubt that other companies also use rental bikes, but they are not
effective because they only use token exchange and others. Therefore, ride paradise has provided an
innovation in the rental world that is customer tracking. by the customer will be able to know and
track in the event of loss or damage to personal data of a person's use will be evidence to our
company to trace the customer. we also use an alarm sound if the time has been sufficient in this
case to avoid the use of bicycles with more time limits. this created system has a new impact on
bicycle rental as it is more systematic and orderly.
1.5 References
Andrew Anten (2015), https://www.articlecube.com/benefits-bike-rental-system
Achieved by 9 September 2015
Will Rodger (2014), https://www.usatoday.com/story/life/2014/04/26/bike-share-green-

living/8044791/ Published 26 April 2014
Cosmin Popan (2019), Bicycle Utopias Imagining Fast and Slow Cycling Features, Published 30
June 2020
Paul Goodman (2022), https://skyaboveus.com/cycling/10-Disadvantages-of-Cycling

Achieved by 8 January 2022
2. Overall Description
2.1 Product Perspective

1. Manage account
In this system we provide system admin is the only person who can manage this system. If
customers want to add time, change the detail information such as name email and timing.
If bicycle have been lost or damage system will been update and get data that have been
registered.
2. Generate report, handle customer data, adjust time display, reminder time
Customer records creation and maintenance is the Administrator’s primary responsibility in
the organization of this bike rental system. This report contains the customer's personal
details such as date, name, ic number, telephone number, gender, and citizen. Admin
report records involve name, admin id, bicycle id, type, location, report, and status.
3. Login and logout

We provide to type of user which is admin and customer. Our system has been including
two box username and password to customer easy to login and logout the system. This
page purpose is to allow you to access the system or website.
4. Time starts and end

This is a timing for bicycle rental system. In this system, customer should be able to time
start and end time while rental the bicycle. By using this system can know their time limit
while using our bicycle rental system. 1 hour before and 30 minutes before time expires,
alarm the technology installed on the bike will sound as a reminder for customers to be
ready to return That bicycle.
5. Complete the data, register, make a payment, choose bicycle and location
This is customer website page which is they must register form by key in data and make a
payment after customer have been choose bicycle and location. This payment for the
bicycle rental system depends on timing from start to end but we still choose manual
payment because some of old people doesn’t know to use online banking, so this is easy to
be used by many ages categories
2.2 Product Functions

The main feature of the bike rental system is to keep records and important details of each
customer who has registered and made a payment. The system also allows admins to view all
record statistical data for customers. So basically, our system has two types of access modes:
1. Admin
2. Customers
2.3 User Classes and Characteristics

There are two types of users who can use this website:
1. Admin
Admin has all the privileges on the system to control everything in the system. Admin can
check the status and monitor the condition of the bike as well as the use of customers who
use the service of the bike rental system. For example, the admin can remove the data
report if the problem has been resolved, is data such as deleting records. For customer
privacy data the admin cannot delete and edit the data that has been entered.
2. Customers
Customers can fill in data to register data for new customers who want to use bicycle rental
services. After registering the customer will choose the place and time before making the
payment so the registered record will be accessed by the admin to check the time allocated
for the bicycle rental system to the customer.
2.4 Operating Environment
1. Hardware
• Any devices to access the system is required.
• Internet server.
2. Software
• Operating systems: Windows 10
• XAMPP control panel
• Visual Studio Code
• PHP MyAdmin
2.5 Design and Implementation Constraints

The challenge in developing a bicycle rental system is the loss and damage factor. This is
often the case with all rental companies. Besides that, the company that has made the rental must
be brave enough to take the risk. This system also only sounds an alarm if the usage time has
expired. Often such things happen to some irresponsible parties. Therefore, this is one of the major
challenges faced by bicycle rental system companies.
Next is the factor of loss of customer data if the staff has difficulty in terms of accessing
customer data. each customer who has registered their own account to access the system if they
want to rent. Then data loss can be caused by many things from computer viruses to hardware
failure. but failure to access data also occurs if the customer forgets their password. Therefore,
access failure is one of the biggest challenges in accessing a website.
Service can be considered of as the one of problem statement for bicycle rental system for
our industrial machines and equipment require. The system that we use 90 percent of the results
from the website, if there are problems in terms of maintenance, it will make it difficult for the staff
to do the work. For example, when a computer or hardware is used for too long without service, it
can infect a malware virus so maintenance should be done at least once a week to ensure the
system is not problematic and slow.
2.6 User Documentation

This rental system will provide a user manual by staff to explain the functions and provide
options available to users and step by step have been taught to facilitate customers.
2.7 Assumptions and Dependencies

Dependence has a direct impact on the development of bicycle rental system systems,
leading to the formation of cross-functional product teams. As a result, the ride paradise company
is very conscientious about ensuring that all dependencies are explicitly mapped and planned to
avoid any disruptions to the system's overall development. These assumptions and limits, once
determined, shape the project in certain ways, but in diverse ways. As a result, assumptions
represent possibilities, whereas constraints provide constraints for the bicycle rental system. For
ride paradise firms, we do things like availability of key project members, performance of key
project members, and skills of key project members, as well as budget restrictions. Finish-to-start,
Start-to-start, Finish-to-finish, and Start-to-finish are the four most common relationship models.
3. External Interface Requirements
3.1 User Interfaces
3.1.1 Main Page
3.1.2 Admin Login

3.1.3 Admin Homepage
3.1.4 Customer Data

3.1.5 Report Form
3.1.6 Admin Report

3.1.7 Customer Registration Form
3.1.8 Billing Payment

3.1.9 Start Rental
3.1.10 Timer
3.1.11 End Rental
3.2 Hardware Interfaces

Since the application must run over the internet, all the hardware shall require connecting
internet will be hardware interface for the system. This system can access by any devices such as
smartphone for customer and tablet for admin.
3.3 Software Interfaces
Software that involves for Ride Paradise Rental System development is:
1. Visual Studio Code (VSC).

Visual Studio Code combines the simplicity of a source code editor with powerful developer
tooling, like code completion and debugging. All the coding of interface, connection and
database linked is created in VSC.
2. XAMPP.
XAMPP is an acronym that stands for Cross-Platform, Apache, MySQL, PHP, and Perl,
with the Ps standing for PHP and Perl, respectively. It’s an open-source web-solutions kit
that provides Apache delivery for a variety of servers and command-line executables. Until
releasing a website or client to the main cloud, XAMPP allows a local host or server to
validate it on computers and laptops.
3. PHP MyAdmin.
It is a software tool written in PHP, intended to handle the administration of MySQL over the
Web. PHP MyAdmin supports a wide range of operations on MySQL. Frequently used
operations of managing databases, tables, columns, relations, indexes, users, permissions
and can be performed via the user interface, while still can directly execute any SQL
statement.
3.4 Communications Interfaces
The e-store system shall use the HTTP protocol for communication over the internet and for
the intranet communication will be through TCP/IP protocol suite.
4. System Features
4.1 Functional Requirements

Rental system of Ride Paradise has involved the following functions:
Customer
1. Register
This page allows customer to register into the system. customers need to fill in their
information in the system as a user. then if successful the system will continue to the
customer's homepage, otherwise an error message is displayed, and the user is transferred
back to the register page.
2. Payment
On this page, the system will allow the customer to make a payment after completing the
registration. On this page, customers need to refer to the staff because they need to enter the
admin id to enable the rental process to run. And the customer will press the proceed button
3. Choose Bicycle
On this page the system will allow customers to rent a bike by entering the id and the place
where they took the bike. Then they need to press the proceed button to start the rental
4. Time Display
This page will allow customers to start and stop their time if they rent a bike. On this page
will also be set the time they rent.
5. Returned Bicycle
This page will allow the customer to re -enter the bicycle id and the place where they return
the bicycle. And they will press the return button after returning the bike.
Admin
a. Login
This page allows an admin to login into the system. admin is prompted to enter his/her
username and password. When the admin activates the Login button, the system validates the
identifying information entered by the user, and if valid, he/she is transferred to the homepage,
otherwise an error message is displayed, and the user is transferred back to the Login Page.
b. Manage Customer Data

On this page the admin can access or track all data related to the customer. This customer
data will be stored in this system after the customer registers in this system.
c. Manage Report
This page will allow the admin to make a report related to the bike. Here the admin will fill
out the report form. At the same time the admin can also see the overall rental report of each
customer on the admin report page.
d. Logout
The interface allow user to logout from the system

4.1.1 Use Case Description
i. Register
Use Case Name register

Actors Customer
Description Allow user to register in application.
Pre-Condition The user goes to register form
Post-Condition User will be redirected to the register page
Normal Flow 1. The user must click button customer
2. user will be redirected to register page
3. users must fill in the register form
4. the data will record n the system.
Exception None
Frequency Of User When the user enters register page.
Special Requirement This function provides secure access to the system
Assumptions None
Notes And Issues None
ii. Payment
Use Case Name Payment

Actors Customer
Description Allow user to the payment page
Pre-Condition The user from register page
Post-Condition User will be redirected from register page to payment page
Normal Flow 1. the user will be redirected from register page
2. the user data will appear.
3. The user hace to enter staff id who incharge at that time.
4. The user must make payment
5. The payment option is cash only
6. The user will click button “proceed”.
Exception None
Frequency Of User When the user redirected in payment page
Assumptions Only customer can access this page.
iii. Choose Bicycle
Use Case Name Choose bicycle

Actors Customer
Description Allow user to the rental bike page
Pre-Condition The user must click button “proceed” in payment page
Post-Condition User will be redirected from payment page to rental bike page
Normal Flow 1. the user will be redirected from payment page
2. the user data must enter bicycle id
3. The user must choose the location
Exception None
Frequency Of User When the user redirected in rental bike page
iv. Time Reminder
Use Case Name Time reminder

Actors Customer
Description Allow user to the timing page
Pre-Condition The user must click button “proceed” in rental bike page
Post-Condition User will be redirected from rental bike to time reminder page
Normal Flow 1. the user will be redirected from rental bike page
2. the user will click button “start” to start the time.
3. The user will click button “end” to dtop the time
4. The page will direct to return bike page.
Exception None
Frequency Of User When the user redirected in time reminder page.
v. Return Bicycle
Use Case Name Return bicycle

Actors Customer
Description Allow user to the return bike page
Pre-Condition The user must click button “end” in time reminder page
Post-Condition User will be redirected from time reminder to return bike page
Normal Flow 1. the user will be redirected from time reminder page
2. the user data must enter bicycle id
3. The user must choose the location.
5. User will return the bike
6. The user will be redirected to mainpage.
Exception None
Frequency Of User When the user redirected in time reminder page.
vi. Manage customer Data
Use Case Name Manage customer data

Actors Admin
Description Allow user to customer data page.
Pre-Condition The user cannot track see or track customer data.
Post-Condition The user can track and record customer data.
Normal Flow 1. The user selects customer data page in mainpage
2. The page show customer data that have been record.
Exception None
Frequency Of User When the user enters customer data page.
Assumptions Only admin can access this page
vii. Login
Use Case Name Login

Actors Admin
Description Allow user to login in application.
Pre-Condition 1. The user is not logged in to the system
2. The user should land on the login page
Post-Condition 1. The user is logged in to the system
2. The system mainpage is display
Normal Flow 1. The user landed on the login page
2. The system displays a login form
3. The user enters the valid username and password
4. The user confirms his entry is valid
5. The system validates if user is identifying
6. The system logged in to the system
Exception At the step 3 of the normal flow, if the user enters invalid
username
and password:
1. The system will display an error message “Invalid
Username”
or “Invalid Password.
2. The user is transferred back to the Login page.
Frequency Of User When the application starts.
viii. Manage Report
Use Case Name Manage report

Actors Admin
Description Allow user to make a report in repor form and view admin report
Pre-Condition 1. The user has must click button “report form”.
2. The user must click button “admin report”.
Post-Condition 1. The user can fill in the report form.
2. The user can review customer data and report.
Normal Flow 1. The user must fill in the form if having a problems
2. After user fill in the data from report will be record
3. The user must click “admin report” button.
4. The user can access data about custmer and the report
record.
Exception None
Frequency Of User When user enter page “report form” and “admin report”
ix. Logout
Use Case Name logout

Actors admin
Description Allow user to logout from application.
Pre-Condition User must already login
Post-Condition User will be redirected to the mainpage.
Normal Flow 1. The user clicks “Log out” button
2. The application redirected to the mainpage.
Exception None
Frequency Of User User must click “Logout button”
Special Requirement None
Assumptions After logout, the user can choose wether they want to go anther
page.
4.2 Other Nonfunctional Requirements
4.2.1 Performance Requirements

1. Handling of Errors
In this system if there are any problems such as lost or damaged bikes, the system can be
affected because if that happens the admin will fill out a report form.
2. Security Requirements
The security requirements deal with the primary security. The software should be handled
only by the admin and authorized users. Only the admin has right to assign permission like
creating new accounts and generating password. Only authorized users can access the
system with username and password.
3. System Availability
The bicycle rental system is just available at 6 Am to 2 Am every day. In a case of
unavoidable circumstances that lead to system malfunctioning, it should be restored within
48 hours. System restore should be done as soon as possible to ensure that business
resumes as usual and business processes are not severely affected.
4. Easy to Use
With the level of knowledge of the target market users, the system interface should be
simple but quality to make it easy to comprehend and hence require less training and
learning efforts. Therefore, the system chooses to make payments in cash. This is for the
convenience of all users.
5. Other Requirements
All the data will be stored in a phpMyAdmin database.
Appendix A: Glossary
SRS – System Requirement Specification
RAM – Random Access Memory
VSC – Visual Studio Code
XAMPP – Cross-Platform, Apache, MySQL, PHP and Perl
MySQL – Structure Query Language
TCP/IP – Internet Protocol Suite
HTTP – Hypertext Transfer Protocol
Appendix B: Analysis Models
Figure 1 : Use Case Diagram

Figure 2 : Swimlane
Figure 3 : Class Diagram

Appendix C: To Be Determined List
Figure 4 : Admin Page Security and Authority
Figure 5 : Systematic Timer

Figure 6 : Record Data customer for Staff

Bicycle Rental System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bicycle Rental System

Uploaded by

Copyright:

Available Formats

Software Requirements

RENTAL BICYCLE SYSTEM

Version 1.0 approved

INTAN NAZIEHA RASHIDAH BINTI RASHIDIN (2020987633)

NUR KHAIRUNNISA BINTI KAMAROLZAMAN (2020978369)

NUR AFIQAH BINTI ROSLI (2020965763)

21 OCTOBER 2021 – 6 FEBRUARY 2022

1.2 Document Conventions

1.3 Intended Audience and Reading Suggestions

1.4 Product Scope

Will Rodger (2014), https://www.usatoday.com/story/life/2014/04/26/bike-share-green-

Paul Goodman (2022), https://skyaboveus.com/cycling/10-Disadvantages-of-Cycling

2.1 Product Perspective

3. Login and logout

4. Time starts and end

2.2 Product Functions

2.3 User Classes and Characteristics

2.4 Operating Environment

2.5 Design and Implementation Constraints

2.6 User Documentation

2.7 Assumptions and Dependencies

3. External Interface Requirements

3.1 User Interfaces

3.1.1 Main Page

3.1.2 Admin Login

3.1.3 Admin Homepage

3.1.4 Customer Data

3.1.5 Report Form

3.1.6 Admin Report

3.1.7 Customer Registration Form

3.1.8 Billing Payment

3.1.9 Start Rental

3.1.11 End Rental

3.2 Hardware Interfaces

3.3 Software Interfaces

1. Visual Studio Code (VSC).

3.4 Communications Interfaces

4.1 Functional Requirements

b. Manage Customer Data

The interface allow user to logout from the system

4.1.1 Use Case Description

Use Case Name register

Use Case Name Payment

iii. Choose Bicycle

Use Case Name Choose bicycle

iv. Time Reminder

Use Case Name Time reminder

Use Case Name Return bicycle

2. the user data must enter bicycle id

3. The user must choose the location.

4. The user will click button “proceed”.

5. User will return the bike

6. The user will be redirected to mainpage.

vi. Manage customer Data

Use Case Name Manage customer data

Use Case Name Login

viii. Manage Report

Use Case Name Manage report

Use Case Name logout

4.2 Other Nonfunctional Requirements

4.2.1 Performance Requirements

Appendix B: Analysis Models

Figure 1 : Use Case Diagram