A WEB-APPLICATION

SOFTWARE REQUIREMENT
SPECIFICATION DOCUMENT

Cover|P a g e
The Scenario

Carsharing is the sharing of vehicle travels with the goal that more than one
individual goes in a vehicle, and anticipates the requirement for others to need to drive to
an area themselves.

By having more individuals utilizing one vehicle, carsharing diminishes every

individual's movement costs, for example, fuel costs, tolls, and the worry of driving.
Carsharing is additionally an all the more ecologically neighborly and economical
approach to go as sharing voyages decreases air contamination, carbon outflows, traffic
clog on the streets, and the requirement for parking spots. Specialists frequently
energize carsharing, particularly during times of high contamination or high fuel costs.
Vehicle sharing is a decent method to go through the full seating limit of a vehicle, which
would some way or another stay unused in the event that it were only the driver utilizing
the vehicle.

Thus, a web application related to carsharing is created to carpool with ease. Including
features such as details of the driver, type and model of the car , seat availability, cost
per seat, rating of the driver & rider.

Cover|P a g e
1 User Interface:

1.1 Pages
1.1.1 Home Page
1.1.1.1 Header will contain Search, Profile, Help, Contact Us, My
Trips and Logout.
1.1.1.2 User will see THANK YOU message after successful login
1.1.2 Search
1.1.2.1 This page contains Departure and Destination fields to
Search the rides available for a certain route.
1.1.2.2 The rides available would e displayed to the user.
1.1.3 Contact Us
1.1.3.1 Through Chat window
1.1.3.2 Through Email
1.1.3.3 Through Cell
1.1.3.4 Through Social Media
1.2 Ride Listing:
1.2.1 Car Brand & Model
1.2.2 Number of seats available
1.2.3 Price per seat
1.2.4 Driver's ratings
1.3 Booking:
1.3.1 Riders Name
1.3.2 Riders pickup Address
1.3.3 Riders Cell
1.3.4 Riders Rating
1.4 An online representation of the ride would be displayed using the Google maps.

2 SCOPE OF THE PROJECT

The objective of this project proposal is to define the project scope of carsharing Web
application and to provide the Estimation. The advantage would be simple user
interface that is easy to understand by all type of users.
2.1 SCOPE
The scope document is defined after discussing with the Client
2.1.1 Design Goals
The application consists of following main things:
Rider Features
View the routes availale
Browse the rides
View Drivers Details

Cover|P a g e
 View Prices and ratings
Become a Member through Registration process
Registered Member Panel
Login to site
Manage Account
My Profile
My Orders
Buy Product (Checkout)
Logout
Admin Panel
Login
Dashboard
Administrator User Management
Site Member(Customer) Management
Blind Type Management
Product Attribute Management
Product Management
Price Chart Management
Banner Manager
Order Manager
Booking Management

Cover|P a g e
 2.1.2 High level Requirements

System Block Diagram

for the riders

Cover|P a g e
for the driver

Cover|P a g e
for Booking system

Cover|P a g e
THE ER-DIAGRAM :

3 User Registration

3.1 User will register before any kind of transaction such as booking or sharing a
ride.

Cover|P a g e
 3.2 Though a visitor can view various rides available for a particular route.
3.3 Registration form will contain e-mail, user name, password, home address and
pickup point etc.
3.4 Security, in the form of protecting sensitive customer data while it is transferred
over the Internet, and preventing unauthorized access to the administration
console.
3.5 After enter user details then display terms and conditions for user in which user
need to confirm and read our conditions.
3.6 Display a welcome message to user after successful registrations.

4 Terms & Conditions

4.1 Privacy Policy. Our privacy policy, which sets out how we will use your
information, can be found at .By using this Website, you consent to the
processing described therein and warrant that all data provided by you is
accurate.

4.2 Prohibitions. You must not misuse this Website. You will not: commit or
encourage a criminal offense; transmit or distribute a virus, Trojan, worm, logic
bomb or any other material which is malicious, technologically harmful,
Breaching this provision would constitute a criminal offense.

4.3 Intellectual Property, Software and Content. The intellectual property rights in
all software and content (including photographic images) made available to you
on or through this Website remains the property of www.carsharing.com.

4.4 Terms of Sale. By placing a booking order you agree to take or share the ride.
All orders are subject to availability and confirmation of the ride booked.

4.4.1 Our Contract. When you place a booking for your ride, you will
receive an acknowledgement e-mail confirming Receipt of your
booking with the details of the ride.
4.4.2 Pricing and Availability. Whilst we try and ensure that all details,
descriptions, ratings and prices which appear on this Web application,
are accurate, errors may occur.
4.4.3 Payment Upon receiving your booking we carry out a standard
authorization check on your payment Card to ensure there are
sufficient funds to fulfill the transaction.

4.5 Complaints. We operate a complaints handling procedure which we will use to

try to resolve disputes when they first arise, please let us know if you have any
complaints or comments. A dedicated team of executives work round the clock
to ensure a safe ride for every carsharing.com user.

4.6 Entire Agreement. The above Terms of Service constitute the entire agreement
of the parties and supersede any and all preceding and contemporaneous

Cover|P a g e
 agreements between you and www.example.com. Any waiver of any provision of
the Terms of Service will be effective only if in writing and signed by a Director of
www.carsharing.com.

5 Commuting policy :

5.1 Commuting policy should easily accessible. Don’t require visitors to log in or
create accounts, before they can view the relevant rides available for them.
Visitors to our website will need to know the terms before they book or share a
ride.
5.2 Commuting policy must be accessible from all pages. Placing a link within
website’s header or sidebar will usually do the trick.
5.3 Rides must be booked beforehand. Atleast 30 minutes before the ride starts.

System Specification

We will use Agile method through whole project.

And we will use Nodejs,Angular 2+,MongoDB in this project.

Cover|P a g e
 System will be designed on The Basis of above user requirements.

1. User Interface:

1.1 Pages
1.1.1 Home Page
1.1.2 Header (logo, menu -> about, contact, [profile <- if logged in],
login/logout)
1.1.3 Display RIDE SAFE ALWAYS message after login successfully
1.1.4 Simple hero shot and marketing message
1.1.5 About Us
1.1.5.1 Couple of sentences about the website
1.1.6 Contact Us
1.1.6.1 Through Chat Box
1.1.6.2 Through Email
1.1.6.3 Through Cell
1.1.6.4 Through Social Media
1.1.6.5 Through Social Media
1.2 Ride Selection:
1.2.1 Car Brand & Model
1.2.2 Number of seats available
1.2.3 Price per seat
1.2.4 Driver's ratings
1.3 Booking
1.3.1 Riders Name
1.3.2 Riders pickup Address
1.3.3 Riders Cell
1.3.4 Riders Rating
1.4 An online representation of the ride would be displayed using the Google
maps.

2 User Registration Requirements:

2.1 Build value around registration.

Before users create an account you need to explain the reason for creating
an account.

Cover|P a g e
 2.2 Eliminate as many fields as possible.
Only get data from user which are most important and remove or make all
other fields as "Optional" which are not necessary about user.
2.3 Group fields logically
Some sites gather a lot of information in registration form like booking
address, billing address etc,
So many users want to deliver their personal information in certain order.
And we need an order for user registration.
2.4 Break up long registration processes into steps.
And finally bread down all the processes into a well steps.
2.5 Make your security and privacy policies clear as day.
Make sure that the user who is creating an account on our website is secure.
And include a clear link of our privacy policy.
2.6 Make password recovery easy.
If a user forgets his password or loses their password in some cases, so we
want a password recovery link in our both registration and login form.
2.7 Give the option to refresh captcha.
in order to secure website from robots usage. So we want a captcha code for
users to enter it while creating an account.
2.8 Give an epayment method.
Before users enter into their accounts while in registration they need to
confirm their account on any e-wallet or any other bank account.
2.9 User Login System:
It is necessary for every user to login into their accounts before they move to
book or share a ride from our web-application.
We want a user email and password in login form for the users.

2.10 Admin Panel:

We want an admin panel in which we can control all the information/data
about our website like we can insert a new data from admin panel and delete
that data about product which are not available in our shop/market. And our
admin panel must be secure in which only two admin can access to our
admin area and edit / delete the data.
And we have user’s information in our admin area So that we can easily
check the user’s detail.

3 Terms & Conditions

Cover|P a g e
 3.1 Privacy Policy. The privacy policy, which will set out how to use End user
information, place at [Privacy Policy Link].

3.2 Prohibitions.Display to user as“You must not misuse this Website. You will
not: commit or encourage a criminal offense; transmit or distribute a virus,
Trojan, worm, logic bomb or any other material which is malicious,
technologically harmful, Breaching this provision would constitute a criminal
offense.”

3.3 Intellectual Property, Software and Content. The intellectual property rights
in all s/w and content (including all graphics) made available to user on or
through this system remains the property of [site URL].

3.4 Terms of Sale. By placing an order, offering to purchase a product on and

subject to the following terms and conditions. All orders will subject to
availability and confirmation of the order price.

3.4.1 Contract. When user place an order, send an acknowledgement

through e-mail confirming Receipt of order to user.
3.4.2 Pricing and Availability. Whilst try and ensure that all details,
descriptions and prices which appear on the system, are accurate,
errors may occur.
3.4.3 Payment receiving user’s order carry out a standard authorization check
on user payment Card to ensure there are sufficient funds to fulfill the
transaction.

3.5 Complaints. Operate a complaints handling procedure which will use to try to
resolve disputes when they first arise, let userto complaints or any comments
anything about system.

3.6 Entire Agreement. The above Terms of Service constitute the entire
agreement of the parties and supersede any and all preceding and
contemporaneous agreements between user and [site URL]. Any waiver of
any provision of the Terms of Service will be effective only if in writing and
signed by a Director of [site URL].

Cover|P a g e
 4 Booking & Cancellation Policies:

4.1 Booking policy will easily accessible. Don’t require visitors to log in or
create accounts, before they can view rides available. Visitors to site will need
to know the booking terms before they book a ride.
4.2 Accessibility of booking policy from all pages. Place a link within
website’s header or sidebar to do the trick.
4.3 Provide all booking details at the checkout. Tell customers how much
each booking option will cost and how long it will take. Provide full details
on interstate and intercity booking, if applicable.
4.4 Refunds and compensations depend on who can’t travel as planned and when
they let us know.
4.5 if the passenger cancels more than 24 hours before departure time then
the booking amount will be refunded excluding service fees.
4.6 What if the passenger cancels in the last 24 hours before departure time If
the passenger books more than 24 hours in advance, we’ll refund them 50% of
the booking, excluding service fees. We’ll also compensate the driver 50%
because the passenger cancelled shortly before the ride. Also If they book in the
last 24 hours before the ride, but cancel within 30 minutes of booking, we’ll
refund their booking, excluding service fees.
4.7 What if the passenger doesn’t show up? We’ll compensate the driver the full
passenger contribution. It’s not fair for drivers to be kept waiting, so it’s best that
passengers cancel their booking beforehand.
4.8 What if the driver cancels? We’ll fully refund the passenger, including service
fees.

Cover|P a g e