You are on page 1of 12

Business Requirements Document (BRD)

Project Name :- Easy Car Rental (ECR)

VERSION AND APPROVALS


UTORS

VERSION HISTORY
Version # Prepared By Prepared Date Review By Review Date Change Log

This document has been approved as the official Business Requirements Document for Easy Car Rental
and accurately reflects the current understanding of business requirements. Following approval of this
document, requirement changes will be governed by the project’s change management process, including
impact analysis, appropriate reviews and approvals.
TABLE OF CONTENTS

Project Details........................................................................................................1

OVERVIEW...............................................................................................................1

PROJECT OVERVIEW................................................................................................1
3.1 Project Overview and Background.................................................................................................... 1
3.2 Project Dependencies....................................................................................................................... 2
3.3 Stakeholders..................................................................................................................................... 2

BUSINESS PROCESS.................................................................................................2
4.1 As Is Businesss Process Activity Diagram........................................................................................2
4.2 To Be Businesss Process Activity Diagram......................................................................................3

FUNCTIONAL REQUIRMENT........................................................................................1
5.1 Web Interface.................................................................................................................................... 1

NON FUNCTIONAL REQUIRMENT................................................................................1


6.1 Performance requirement................................................................................................................. 1
6.1 Security Requirements...................................................................................................................... 1
6.1 Quality Attributes............................................................................................................................... 1

KEY ASSUMPTIONS AND CONSTRAINTS.....................................................................2


7.1 Key Assumptions and Constraints.................................................................................................... 2
PROJECT DETAILS
Project Name Easy Car Rental
Project Type New Initiative
Project Start Date
Project End Date
Primary Driver Easy Car Rental
Secondary Driver
Division
Project Manager/Dept

PROBLEM STATEMENT
Easy Car Rental provides car rental service to their customers. To rent a car from Easy
Car Rental the customers has to walk in to their office, the receptionist then notes the
requirement of the customer in the form and completes the booking process.

In recent times Easy Car Rental has witnessed an increase in the number of customers
in the store and which has increased the workload for the receptionist and also difficult
to manage the customers details in a book. The customers also have to wait in long
queues to rent a car which gives a bad customer experience.

While the current system is not able to handle the pressure of increasing customers and
the emerging need of digitization of data. The purpose of this project is to create a portal
for Easy Car Rental using which their customer can rent their car online.
PROJECT OVERVIEW

3.1 Project Overview and Background


A new up and coming car rental service is wishing to have a user interface that will
allow their customers to view the models, descriptions and prices of different cars
available. The user has the ability to register and log in to the Web App from any
device, from tablets to mobile phones and desktop computers. The administrator will
also be able to login through the same form but have the ability to add/remove new
car rentals, change prices, and so on. Potential customers should be able to view all
the cars available to rent even without logging in as well as rent without having an
account, though the option is provided upon checkout.

3.2 Project Goals


This web Application will be used by the customers to rent cars. The customers can search
cars and filter them by price and model and the customer can fill the journey details like start
date, End date, Pick up location and destination location. They can also Pay online using
various online payment methods.

This Web Application will also allow the company to access their database securely and
safely in a user-friendly online environment. Allowing them to perform various task like add
new car, remove car, add driver with ease.

There should be a Web Application version for the software to connect with for those who
wish for a Quick car rental servicer. The Web App will be responsive to any device using it.
This allows for consumers to access the service from any sort of hardware device: tablet,
computer, mobile devices, and so on. The software itself will be available on all computer
platforms that are running any aspect of Linux, Windows 7, Windows 8,Windows 10 and
Mac operating systems.

3.3 Stakeholders
The following comprises the internal and external stakeholders whose requirements are represented
by this document:

Stakeholders Organization Role


BUSINESS PROCESS

4.1 Current Business Process (As - Is)


4.2 Proposed Business Process (To - Be)

Login and Registeration Process


Functional Requirement

5.2 Screen Mockup

Landing Page
The customer can view all the cars available for rent in this page and apply filters
like Price of car, Model Name, Seating Capacity.
Product Page
This page will show the car that the customer as selected on the product page.
The page will include Image of the car, Price and Name of the model, Seating
capacity of the car and description of the car.
5.2 Website Interface
User
 View available rental cars
o The customer can view all the cars available for rent.

 Enter Journey details


o The customer will enter his journey details (e.g Start date, End date, To
and From) in a  form.

 Select the desire car


o A button will appear below every car preview that will allow to book the car
model.

 Allow Registration
o Allow customers to register with the Registration form.

 Allow Log in
o Allow Login to register with the Login form.

 Give Feedback
o The customer can give their feedback in this form.

 Do Enquiry
o The customer can ask any question in this form.

Admin

 Add Car
o The admin can add cars.
 Remove Cars
o The admin can remove cars from the portal.
 Allow Login
o The admin can Login to his account
 Reply to feedback and enquiry
o The admin can reply to customer feedback and query.
 Add Driver
o The admin can add drivers.
 Edit Journey
o Admin can edit the customer's journey.

Super Admin
 Add admin
o The super admin can create an account and give admin access to the
staff.
 Super admin can also perform all the tasks of an admin.

Non Functional Requirement

6.1 Performance requirement:


 Ability to handle large customers traffic on the website at once without crashing.
 Fast loading of the web pages.
 Have a quick recovery time if anything were to go wrong.
 Display accurately and efficiently on all devices (responsive view).
 Send any emails immediately.
 Being logged in should allow for customers to quickly make payments
without reentering information, and allow for any potential registered
perks the company may have.

6.2 Security Requirements:


 Prevent any potential threats such as SQL injections through the forms or search
boxes.
 Sensitive data should be encrypted.
 Verify website security certificates.
 Prevent false information from being used in payment.
 Prevent false email inputs from being used when registering.

6.3 Quality Attributes:


 Maintain a user friendly environment that is visually appealing.
 Easy to see and use navigation.
 Searching cars should be accessible to people who are and are not logged in.
KEY ASSUMPTIONS AND CONSTRAINTS

7.1 Key Assumptions and Constraints

# Assumptions
Customers have a proper internet connection
The car works perfectly in the journey
The cost of the journey will be automatically calculated by calculating the journey
distance and rent of the car.

# Constraints
JavaScript should be enable in the browser

You might also like