Software

Requirement &
Specification
Ride Buddy

By Harsh Kumar Manjhi

Introduction
1.1 Overview:
This document serves the purpose of collecting and analysing all the
assorted ideas that have come define this system, and its requirements
with respect to consumers. This SRS also serves the purpose of providing
a detailed overview of the software product, its parameters and goals.

1.2 Purpose:
Ride Buddy is a Web and Mobile Application based software
implementation of Car Rental Service. The need and utility of a car these
days are rising exponentially in this modern world of ours. Yet it isn’t
easy to get a car for your needs instantaneously, owning a car is a
expensive and a hectic thing. The tourists too face a lot of problem
travelling in a new city because of the lack of enough rental services. This
application strives to mitigate these problems by providing a simple, easy
and a really fast way to book your ride for as long as you need it.

1.3 Scope:
Being a Car Rental Service, this extends to provide the vehicular needs of
the user. It is an Utility application to help it users in their vehicular
functionalities. It covers the area of Car Rental Industry and Software
development industries.
Overall Description
2.1 Product Perspective:
A car rental is a vehicle that can be used temporarily for a period of time with a
fee. Renting a car assists people to get around even when they do not have
access to their own personal vehicle or don't own a vehicle at all. The individual
who want to rent a car must first contact the car rental company for the desire
vehicle. Which in most of the cases isn’t online. This product aims to bridge
that gap.
2.2 Product Function:
• Provide a simple interface and platform to facilitate easy renting of cars
for both the customer and the owner.
• Facilitate a Sort Functionality for the customer to choose a preferable
type or make of car.
• Adding a payment gateway and wallet in the application to provide an
easy method of payment.
• Implement a feedback system for resolving issues and as a preference
option for the user.

2.3 User Classes and Characteristics:

2.3.1 Admin:
• Admin can login to the system.
• Verify the car information database.
• Generate price strategy.
• Handle the payment system.
• Finalize the order.
• Cancel the order.

2.3.2 Employee:
• It updates the database.
• Give information to the customer about the car.
• Provides the alternatives.
• Maintain contacts.
2.3.3 Customer:
• Customer can login to the system.
• Visit the website/app.
• Place the order.
• Cancel the order.

2.3.4 Owner:
• It can add his/her car to the Car Database.
• Specify the time for the lease.
• Receive payment for its service
• Manage his orders
Functional Requirements
Customer’s View
1. Login & Sign Up
1.1 Description and Priority
Login is necessary to rent a ride. To provide the uniqueness of the user and
maintaining a user’s orders.

1.2. Stimulus/Response sequence

Stimulus :The unregistered user request to create an account
Response:The user is shown a signup page to continue with mobile no.
or gmail
Stimulus:The registered user log in with already existing account
Response: The user is shown a log in page to continue with gmail or
mobile no.
Stimulus :The user request to continue with gmail
Response :The user is redirected to gmail login
Stimulus :The user request to continue with mobile no.
Response :The user is redirected to enter the mobile no.
Stimulus :The user request to continue with facebook
Response :The user is redirected to enter the facebook

1.3. Functional Requirement

1.Continue with Gmail
2. Continue with mobile no.
3. Continue with facebook
2. Give User Details
2.1. Description and Priority
The user will be asked to enter the basic details like mobile no., name,
address and some document id like aadhar and pan.
2.2. Stimulus/Response sequence
Stimulus: User will be asked to enter the details.
 Response:After entering details user will be redirected to page
containing ride listing based on location availibility.
2.3. Functional Requirement
Enter Basic details: User must be allowed to enter the basic details.
3.Account Management
3.1. Description and Priority
Maintaining the account related info such as orders wallets ratings and
reviews.
3.2. Stimulus/Response sequence
Stimulus:When user clicks on order
Response: The user is shown the previous orders
Stimulus:When user clicks on wallets
Response: The user is can maintain his wallets and its balance
Stimulus:When user clicks on Ratings and Reviews
Response: The user is shown the Ratings and Reviews of the previous
orders
3.3. Functional Requirement
Add money to the wallet
Transfer money from bank to wallet and vice versa
Edit ratings and reviews of previous orders
Track the order status
4. Search, Filter and Sort By
4.1. Description and Priority
This allows the user to search and/or sort/filter the products as per his/her
needs.

4.2. Stimulus/Response sequence

Stimulus:User enters the product name on the search.
Response: The product matching the name is searched and shown
Stimulus:User specifies the filters and sort.
 Response: The product matching the filters is shown.

4.3. Functional Requirement

Filter by price, brands or category
5. Rent a ride
5.1. Description and Priority
The user rents the ride

5.2. Stimulus/Response sequence

Stimulus:User enters the duration for his ride.
Response:The ride with the availability duration less than the duration is
searched
Stimulus:User enters the pick up location.
Response:The ride availibity location is searched
5.3. Functional Requirement
The Ride List

6. Coupon and Offers

5.1. Description and Priority
The user is given the offers and coupon codes that he can apply on his cart

5.2. Stimulus/Response sequence

Stimulus:The user can click on the offers or choose a coupon.
Response :The offer or coupon is applied on the Cart
5.3. Functional Requirement
Check Eligibility of the offer or coupon

Owner’s View
1. Add ride and modify the ride details
 1.1. Description
Owner will able to add rides ,Modify the ride details such as car make and
model
1.2. Stimulus/Response sequence
Stimulus: Owner go to Add ride option.
Response: Owner will provide the ride details and add the product
Stimulus: Owner clicks on edit button of product
Response: Owner will provide the updated details
1.3 Functional Requirement:
Owner needs access to the car database for add funtionality

2. Manage offers and Coupons

2.1. Description
Owner will able to add coupons and offers
2.2. Stimulus/Response sequence
Stimulus: Owner can go to Add Coupon option.
Response: Owner provides the coupon details and add
2.3. Functional Requirement
Owner can set offer for category

Employee’s View
1. Manage offers and Coupons
1.1 Description
Employee will be able to add/remove coupons and offers in behalf of the
company.
1.2 Stimulus/Response Sequence
Stimulus: Employee can go to Coupons option.
Response: Employee provides the coupon details and add/removes them.
1.3 Functional Requirement:
Employee needs access to the coupon database.
2. Manage Feedback
1.1 Description
Employee will be able to resolve complaints and remove no pertinent
reviews.
1.2 Stimulus/Response Sequence
Stimulus: Employee can go to Feedbacks option.
Response: Employee marks the feedback as non-pertinent or resolved.
1.3 Functional Requirement:
Employee needs access to the Reviews database.
Non-Functional Requirements
1.1 Performance Requirements:
• The Client device must have an active internet connectivity.
• The server side must be capable enough to handle large number of users.
• The cellphone device should atleast have Android 5.1 or iOS 10.

1.2 Security Requirements:

• Secure transmission of data to and from the servers.
• Prevent false information from being used as payment.
• Verify Email and other credentials during registration.
Use Case Diagram
Actor and use case description shows the detail description of interaction
between the actors and their use cases. The description enables to have a proper
understanding of how actor interacts with the system through their use cases.
Class Diagram
Sequence Diagram
Sequence diagrams are used to demonstrate the behaviour of objects in a use
case by describing the objects and the messages they pass. It provides a
graphical representation of object interactions over time. Sequence diagrams
show an actor, the objects and components they interact with in the execution of
a use case. One sequence diagram represents a single Use Case 'scenario' or
events. Sequence diagrams show the flow of messages from one object to
another, and as such correspond to the methods and events supported by an
object.