Post on 21-Feb-2017
transcript
BRD
0
Business Requirements Document (BRD)
GOLA-Cab Booking Mobile Solutions
Version 1.4
Business Requirement Document for :
Filename : Gola App Cab services : Transactions
Last Modified Date: 05/12/2016
Author : Arpit Parkash
BRD
1
1.DOCUMENT REVISIONS:
2.APPROVALS: Role Name Title Signature Date
Product Owner Anshul Sponsorer Project Manager Arvind PM Business Analyst Arpit BA System Analyst Aditya SA Architect Dobb Tech lead Development Team Arun Developers Testing Team Tom Testers Scrum Master John Scrum Master
Date Version Number Document Changes
26/11/2016 1.0 Initial draft
28/11/2016 1.1 Project Scope
30/11/2016 1.2 Business overview
2/12/2016 1.3 Functional requirements & Non Functional requirements
05/12/2016 1.4 Final review and Glossary
BRD
2
RACI Chart RACI stands for Responsible, Accountable, Consulted, and Informed and is used to describe the roles played by team members and stakeholders involved
in the BRD and the ongoing process.
The following is the RACI chart for this BRD: Name Position * R A S C I
Anshul Product Owner
Arvind Project Manager
Arpit Business Analyst
John Scrum Master
Arun Development Lead
Tom Quality Lead
Uma Developer
BRD
3
Legend:
* Authorize has ultimate signing authority for any changes to the document.
R Responsible Responsible for creating this document.
A Accountable Accountable for accuracy of this document
S Supports Provides supporting services in the production of this document.
C Consulted Provides input (such as an interviewee)
I Informed Must be informed of any changes.
3. Introduction
3.1 Project Summary
3.1.1 Objectives
The client needed a cab booking solution for their fleet of cars equipped with tablets. The solution should simplify the cab reservation process to deliver cohesive customer service with operational efficiency. The solution should leverage the cutting-edge GPS technologies in enhancing control and gain business visibility for delivering premium services in public transport profession. The solution should also provide unified user experience for cab drivers and passengers, enabling them to access and streamline the booking process on the fly.
The objective of this specific document is to define the complete onboarding of the passenger to the cab services app.
3.1.2 Overview
A leading cab service provider in India, delivering on-time services through faster and cheaper rides to customers. The GPS cab management solution is developed to deliver better customer services and streamline operations right from booking the cab to invoicing and managing payments on the go.\
BRD
4
3.1.3 Purpose This document proposes the solution to onboard the passenger to the cab services app.
3.2 Project Scope
3.2.1 In Scope Functionality To onboard passengers and complete ride using an android app.
3.2.2 Out of Scope Functionality Customer Attraction
3.3 System Perspective
3.3.1 Assumptions
All passengers will have smart phones.
All drivers are provided with smartphones .
All Passengers should have a bank account/ credit or debit card.
3.3.2 Constraints
All passenger should use smart phones.
All drivers should use smart phones.
Passengers should use netbanking and online payments.
Safety of passengers
3.3.3 Business Dependencies
Android or iOS operating system to be used by users.
BRD
5
3.3.4 Business benefits/opportunities
Increased Revenue
Security compliance of the passenger.
Enriched mobile payment and invoicing practice for faster cab booking
Convenient third party wallet for offers
Increased productivity by monitoring and executing booking requests proactively
Better operational efficiency by push notifications for cab drivers and passengers
Improved Quality-of-Service (QoS) by streamlining booking process on the fly
BRD
6
4. Business Process Overview:
4.1 Current Business Process:
Current taxi services are manual and serviced through calls and messages and no mobile app.
BRD
7
4.2 Proposed Business Process
BRD
8
Proposed use case:
USE CASE 1 Input Porject Detail information
Goal Allow on boarding of passenger till
payment Preconditions
User login the system Success End Conditions
Menu page displays on the screen.
Primary, Secondary
Actors
Passenger, Driver, Admin system
Triggers User Click on the Input Project detail
information menu Activity Descriptions
Step
1 User Opens Gola App
2 User Register/sign-up by entering valid
Details 3
System Authenticate user with OTP
validation 4
User logins to account 5
User books a ride by entering valid pick up
location (or by GPS), destination, Type of
car. 6
User confirms info and requests a ride.
7 System updates the nearby driver’s
passenger list
BRD
9
8 Driver accepts or rejects the passenger
9 System makes driver status busy
10 System sends notification to passenger
11 Driver picks and drops the passenger
12 System sends an invoice to passenger
13 Passenger chooses the payment option
and makes payment. 14
Driver confirms payment.
15 Passenger gives feedback for ride and
recieves payment confirmation. 16
Driver status is set to open again
BRD
10
BRD
11
5. Business Metrics & Performance Measure: Rating and feedback form for the driver would be inbuilt in the app for ensuring the best rides are given to the prolonged customers.DashBoard is
provided for knowing the upcoming rides and also the cancelled rides.This is all equipped with the GPS which ensures to avoid errors and to have a legal
pricing.
KPI/ Business Metric Definition
Synchronous activation of
passenger
Verified Passenger should be on boarded instantly.
GPS management Ensure passenger gets onboarded instantly. Also avoiding errors
with location
Ratecard Avoid errors and hence legal issues in pricing and calculations
The requirements in this document are prioritized as follows:
Value Rating Description
1 Critical This requirement is critical to the success of the project. The project will not be possible without this
requirement.
2 High This requirement is high priority, but the project can be implemented at a bare minimum without this
requirement.
3 Medium This requirement is somewhat important, as it provides some value but the project can proceed without it.
4 Low This is a low priority requirement, or a “nice to have” feature, if time and cost allow it.
BRD
12
5.1 Functional Requirements
Req# Rating Description Use Case
Reference
FR- 001 1 Install the app UCD
FR- 002 2 Sign up UCD 2.1
FR- 003 2 Enter valid details UCD 2.2
FR-004 2 Validate data UCD 2.2
FR-005 2 Generate OTP UCD 2.3
FR-006 1 Validate OTP UCD 2.2
FR-007 1 Provide them an arrival alert once
passenger location is located
UCD 2.3.3
FR-008 1 Onboard the passenger UCD 2.1.0
FR-009 1
Make Payment:
1.Cash
2.Card/Net Banking
3.Wallet
UCD 2.2.7
FR -011 2 Generate the invoice with Booking ID UCD 2.7.2, UCD
2.7.3 , UCD 2.7.4
BRD
13
Req# Rating Description Use Case
Reference
FR -012 3 Feedback for rating driver and a text box
for comments
UCD 2.7.1
FR -013 2 Password recovery UCD 2.2.1
FR -014 1 Book a ride UCD 2.3.1
FR -015 2 Type of car UCD 2.3.2
FR -016 3 Request a Ride UCD 2.3.3
FR -017 2 Update Passenger list UCD 2.4
FR -018 2 Accept or reject UCD 2.5.1
FR -019 3 Reason for rejection UCD 2.5.2
FR -020 1 Pick up & Drop Location UCD 2.5.3
FR -021 2 End Ride UCD 2.6
BRD
14
5.2 Non-Functional Requirements
Page Banner-Background Color – White
Horizontal/Primary Navigation-Background Color – Black
Vertical/Secondary Navigation-Background Color – White
Central Display Area-Background Color – Grey
Portal-wide Font Type – Helvitica
Price – Free
Scalability- None
Reporting – Passenger vs location report, Common trends
MS Excel
Bulk search- yes - Because the records in system will be so many.
Export to pdf – yes - To communicated with Stakeholders
SMS Integration – yes – easy & fast communication
Payment through Mobile – yes – ease in transaction
Payment gateways – yes – 1.Paytm 2.Credit Card/Debit Card 3.Net banking
Accessibility – test cases for color
Context sensitive help – yes – help manual
Locations / Countries - India
Customer Hierarchy – Single
ITSM Customer ID – Salient Self
Legal and licensing issues or patent-infringement-avoidability – yes – terms and conditions should be provided
Core Metrics reports which would be provided are mentioned below
BRD
15
o Portal Usage report (Combination of Site over lay report and Content Category).
o Trend analysis report
The application is compatible and supported best on ios and android.All other operating systems are out of scope.
o The Login page would display the below information. This information would be in ENGLISH for the first release
o Help Page -This information would be in ENGLISH for the first release
Help > Overview Page (Default Login Landing Page)
BRD
16
Flow of events:
Basic Flow
Use Case ID
Use Case Name
Use Case Description
Use Case
Actors
Use Case Data Use Case
Comments
UCD 2.1 Sign up/Register Passenger should be able to register in the cab
services app.
Passenger
UCD 2.2 Enter Valid details Passenger should be able to enter valid details in the
registration screen.
Passenger
UCD 2.3 Validate details Cab services system should be able to validate the
email address and mobile number through verify
email and OTP functionalities respectively.
Admin system
UCD 2.1.0 Onboard Once the system validates the user successfully
using OTP , the system should onboard the
passenger successfully. And the passenger should
be able to access all the features.
Admin system
UCD 2.2 Login Passenger should be able to login to his account to
access services.
Passenger
UCD 2.2.1 Forgot password Passenger should be able to recover password if
passenger forgets the login details through email
Passenger
UCD 2.3.1 Book & Request a
Ride
Passenger should be able to enter valid Pick up
location or through GPS. Passenger should be able
to enter valid Destination location or through
GPS.
Passenger
BRD
17
UCD 2.3.2 Type of car Passenger should be able to Select the type of car
to ride through the list .
Passenger
UCD 2.4 Update Passenger
list
Admin should be able to update the passenger list
to nearby drivers
Admin system
UCD 2.5.1 Accept or reject Driver should be able to accept or reject a
passenger request
Driver
UCD 2.5.2 Reason Driver should be able to give reason for rejecting
the ride
Driver
UCD 2.5.3 Pick up & Drop
Location
Driver should be able to access accepted
passengers ride details for pick & drop.
Driver
UCD 2.6 End Ride Driver Should be able to end ride and send
invoice to passenger
Driver
UCD 2.7 Payment Passenger should be able to choose the payment
option
Passenger
UCD 2.7.1 Feed Back Passenger should be able to rate and give feed
back about the driver and ride
Passenger
UCD 2.7.2 Total amount
Passenger should be able to see the total amount
to be paid
Admin system
UCD 2.7.3 Total distance
Passenger should be able to see the total distance
traveled
Admin system
UCD 2.7.4 Total Time
Passenger should be able to see total time taken. Admin system
BRD
18
5.3 Screen Layout & Traceability Matrix
BRD
19
BRD
20
Control ID Control Type Control name Description Mandatory Unique? Default value
Additional information
A_Passenger_PID Text Autogenerated ID First name of the passenger
Yes Yes Auto-generated in the backend
A_Passenger_FirstName Text First name First name of the passenger
Yes No Entered by user
A_Passenger_LastName Text Last name Last name of the passenger
No No Entered by user
A_Passenger_EmailID Text Email ID Valid email ID
Yes Yes Verify email functionality should be invoked
A_Passenger_Mobile Number Mobile number Valid mobile number
Yes Yes Verify mobile number with OTP
A_Passenger_DOB Number DOB Valid DOB No No Entered by user
A_Passenger_Gender List Gender Gender of the passenger
Yes No Entered by user
A_Passenger_Terms and conditions
Check box I agree to the terms and
Terms and conditions
Yes No Selected by user
BRD
21
condition
A_Passenger_Invoice_ID Alpha Numerical Invoice ID(Auto generated)
Invoice of the passenger for that ride
Yes Yes Auto generated
A_Passenger_Feedback Alphabetical Feed back Feedback by the passenger
No No Entered by user
A_Admin_Total_amount Numeric Total amount Total amount to be paid by passenger
Yes No Auto generated based on rate card calculations
A_Admin_Total_distance Numeric Total distance Total distance travelled by passenger
Yes No Auto generated based on digital odometer
A_Admin_Total_time Numeric Total Time Total time taken by the passenger
Yes no Auto generated based on real time tracking
A_Passenger_Pick_up_location Alpha Numerical Pick up Location Pick up Location of passenger
Yes No Entered by User
A_Passenger_destination_location Alpha Numerical Destination Location
Destination Location of passenger
No No Entered by User
BRD
22
Appendices
Glossary of Terms
Passenger : The end user who requires cab service from the sponsor
Driver: The end user who drives cabs for the Cab service.
Gola : Name of the application the contracted company is developing for the sponsor
Related Documents 1. Stakeholder Analysis - Gola App Cab services.
2. Business Analysis Plan - Gola App Cab services
3. Artifact Folder :
o Gola App - Use Case Diagram (png file).
o Gola App - Use Case Diagram (Star UML Project File)
o Gola App - Passenger books cab (png file)
o Gola App - Passenger books cab (Bizagi project File)
o Gola - Existing Business Model (png File)
o Gola - Existing Business Model (Bizagi project File)
o Screen Layout (jpeg Files) .
-------------------------------------------------------END-------------------------------------------------------
BRD
23