BUSINESS REQUIREMENTS DOCUMENT

ONLINE TRANSPORTATION
APPLICATION
VERSION: 0.1

DATE : 2024-09-05
 PROJECT CASE STUDY
A Business person named Aishwarya is currently Providing
Transportation services (Auto,Car).The current system Works through
Manual Local Transport Orders. She wanted to expand her Business
targeting to larger public including Working Professional,College
students,Old-agepeople
Currently She was facing issues like
 Operational inefficiency route Distance planning,Scheduling and
tracking.
 Scalability As it is more in-demand services handling increased
demand manually is difficult
 Each customer individual data management like keeping records of
their bookings,payment details

In order to improve her business she wanted an “Online Transport

service Application” that connects passengers with drivers for seamless
and efficient ride-hailing services. from where public shall Track their rides
[Real-time tracking GPS],User-friendly interface,Shall use Multiple secure
payment options digital wallets(Gpay,Phonepe),Emergency convenience
Booking at your Doorstep 24/7. and share their experience all in one
Application The app will allow users to book rides, track drivers in real-
time, and make secure payments through the platform.
 ONLINE TRANSPORTATION APPLICATION
VERSION AND APPROVALS
UTORS

VERSION HISTORY
Version # Date Description Author
0.1 05/09/2024 Initial Draft Aishwarya

I admit that This document named <Online Transportation Application>, 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.

DOCUMENT APPROVALS
Approver Name Project Role Signature/Electronic Approval Date
Aishwarya Business Team
 TABLE OF CONTENTS

1. INTRODUCTION

1.1 PROJECT DETAILS

1.2 PROJECT OVERVIEW
1.3 DOCUMENT RESOURCES

2. BUSINESS OBJECTIVES

2.1 BUSINESS GOALS

2.2 PROJECT OBJECTIVES
2.3 SUCCESS CRITERIA (ROI)

3. CURRENT BUSINESS OVERVIEW

3.1 CURRENT BUSINESS SITUATION
3.2 CHALLENGES AND ISSUES
3.3 PROPOSED SOLUTION
3.4 STAKEHOLDERS

4. BUSINESS REQUIREMENTS

4.1 FUNCTIONAL REQUIREMENTS

4.2 NON-FUNCTIONAL REQUIREMENTS
4.3 SYSTEM REQUIREMENTS
4.4 REPORTING TABLES

5. ASSUMPTIONS AND RISK

5.1 ASSUMPTIONS
5.2 RISK AND ITS MITIGATON
 INTRODUCTION
PROJECT DETAILS
Project Name Online Transportation Application
Project Type New Initiative
Project Start Date 05/09/2024
Project End Date (Estimated)
Project Sponsor Stakeholders
Primary Driver Mandatory
Secondary Driver Efficent
Division Software Development

OVERVIEW

This document defines the high level requirements [Online Transportation Application]. Document will
be used as the basis for the following activities:

 Creating solution designs

 Developing test plans, test scripts, and test cases
 Determining project completion
 Assessing project success

DOCUMENT RESOURCES

Documents Business Unit Resources

Design UI/UX Developer Detailed designs, including visual elements and user interaction flows. Basic
layouts of the app's user interface

Technical Software Developer Details the technical architecture, technologies, and systems used
Development

Legal Legal Advisor Compliance Documents: Ensures the app adheres to regulations such as data
protection (GDPR, CCPA) and transport-specific laws.
Terms of Service & Privacy Policy: Legal agreements for users.

Marketing Marketing Manager Strategies for promoting the app, including target audience and key messaging.
Launch Plan: Detailed timeline and activities for the app launch.

Quality Assurance Quality Assurance Strategies and scope for testing the app.
Tester(QA) Test Cases: Detailed scenarios to validate app functionality and
performance.
BUSINESS OBJECTIVES:

BUSINESS GOALS:
1. To connects passengers with drivers for seamless and
efficient ride-hailing services.
2. By expanding Aishwarya’s customer Base through online
services,shall increase Revenue and Market share.
3. The Efficient Online Booking Transport Facility Shall
Enhance Customer satisfaction and loyalty.

PROJECT OBJECTIVES:

 Develop a User-friendly Online Booking Transportation Application

via web and Mobile Platforms
 Get connected with a wide range of users and customers.
 Connects passengers with drivers for convenient, on-demand
transportation.

SUCCESS CRITERIA : (ROI)

 Unit Economics: Positive contribution margins per ride or delivery—

ensuring that each transaction generates a net positive return.

 Revenue Growth: A strong indication of ROI is continuous revenue

growth, driven by increasing ride volume, geographic expansion, or
new service offerings.

 Customer Lifetime Value (CLV): Maximizing the long-term revenue

generated from a user, while minimizing customer acquisition costs
(CAC).
CURRENT BUSINESS OVERVIEW

Current Business Situation: Manual Local Transport Services

CHALLENGES AND ISSUES

 Operational inefficiency route Distance planning,Scheduling and tracking.
 Scalability As it is more in-demand services handling increased demand
manually is difficult
 Each customer individual data management like keeping records of their
bookings,payment details

PROPOSED SOLUTION

Online Transport service Application” that connects passengers with drivers for seamless
and efficient ride-hailing services.

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

Stakeholders

Aishwarya (Owner)
1.
Customers
2.

Drivers
3.

Application Developers
4.
BUSINESS REQUIREMENTS:

The following sections document the various business requirements of

this project.

FUNCTIONAL REQUIREMENTS:

 User Registration and Profiles

o User Registration: Support registration for riders and drivers

using email, phone numbers, or social media accounts.
o Profile Management: Riders and drivers can manage their
profiles (e.g., name, photo, contact details, and payment
information).
o Driver Verification: Drivers must undergo a verification process,
including background checks, vehicle registration, license
upload, and insurance documentation.

 Ride Booking and Management

o Ride Request: Riders should be able to request rides by

entering pickup and drop-off locations.
o Ride Matching: The system should match the rider's request
with the nearest available driver.
o Ride Scheduling: Riders can schedule a ride for a future date
and time.
o Real-time Tracking: Both riders and drivers can view the real-
time location of the vehicle during the trip.
o ETA Updates: Provide riders with estimated time of arrival
(ETA) for pickup and destination.
 Payment Processing

 Multiple Payment Options: Riders can pay via credit/debit

cards, digital wallets (e.g., PayPal, Apple Pay, Google Pay), or
cash.
 In-app Payment: Integrated payment gateway for seamless
payment processing after the ride.
 Receipts: Automatic generation of ride receipts, sent via email
or available in the app.
 Promo Codes and Discounts: Riders can apply promo codes or
discounts to reduce the fare.
Navigation and Route Management

o In-app Navigation: Integration with GPS services (e.g., Google

Maps, Apple Maps) for drivers to navigate efficiently.
o Route Optimization: Suggest optimized routes based on traffic
conditions and road closures.
o Multiple Stops: Riders can add multiple stops or waypoints to
their trip.
NON-FUNCTIONAL REQUIREMENTS:

Notifications and Alerts:

o Push Notifications: Send notifications for ride confirmation,

driver arrival, trip completion, payment, and promotional offers.
o SMS/Email Notifications: Notifications via email or SMS for
booking confirmations, invoices, and promotional messages.
o Driver Alerts: Notify drivers about new ride requests,
cancellations, and scheduled rides.

Rating and Feedback System:

o Ride Ratings: Riders and drivers can rate each other at the end
of the trip.
o Feedback: Option to provide written feedback about the ride
experience.
o Driver Performance Monitoring: Track driver ratings and provide
performance reports for quality control.

Scalability: The system must be able to handle increasing numbers of

users, vehicles, and routes efficiently, especially during peak hours. It
should support scaling both horizontally and vertically to accommodate
future growth.

Performance: The app should respond to user requests within a certain

time frame (e.g., under 2 seconds for booking a ride). Latency should be
minimized, and the app should handle a high volume of transactions per
second without performance degradation.
SYSTEM REQUIREMENTS

HARDWARE REQUIREMENTS:

Client Devices :
o Smartphones: Android or iOS-based devices with minimum system
configurations.Example: Android version 7.0
o PCs/Laptops (for Admin/Dashboard Use): Processor: Intel i3 or AMD
equivalent and above

Business Server Infrastructure :

o Application Servers: Processor: Intel Xeon or AMD EPYC series
o Database Servers: Processor: Intel Xeon or AMD EPYC series (similar to
Application Servers)
o Load Balancers: Dedicated hardware load balancers to manage traffic and
ensure availability during peak loads.
o Firewall Devices: For security, high-performance hardware-based firewalls
should be implemented

Software Requirements:

Client-Side (User and Driver Apps):

- Operating System: Android Mobile Development Framework Native

Development: Android Studio (Java/Kotlin) and Xcode (Swift/Objective C)
- APIs: Integration with third-party services like Google Maps API, Payment
Gateways (e.g., Stripe, PayPal), and notification services (e.g., Firebase)

Server-Side (Backend):

- Operating System: Linux-based distributions (e.g., Ubuntu, CentOS,

Debian)
- Programming Languages:
- Backend frameworks: Node.js, Ruby on Rails, Python (Django/Flask), or
Java (Spring)
- API Development: RESTful APIs or GraphQL
Database Management System (DBMS):

- Relational Databases: MySQL, PostgreSQL, or MariaDBNoSQL

Databases (if required): MongoDB, Cassandra,
- NGINX or Apache for web server management
- Docker or Kubernetes for containerization and orchestration
- Cloud Services:
- AWS, Google Cloud, or Microsoft Azure for hosting, storage, and managed
services
- S3 Buckets for storing media files (e.g., driver images, ride data, etc.)
- DevOps Tools:
- CI/CD Pipelines: Jenkins, CircleCI, or GitLab CI
- Version Control: Git (GitHub, GitLab, or Bitbucket)

Security Software:

- SSL certificates for secure data transmission (HTTPS) Antivirus, Intrusio

Detection Systems (IDS), and Security Information and Event Management (SIEM)
Admin Panel (Dashboard): Web-Based Framework: Frontend: Angular, React,
or Vue.js
- Backend: Same as the application server (Node.js, Python, etc.)
- Database: Same as the main database server
- Reporting Tools: Integrate with tools like Google Analytics, Tableau, or
custom reporting dashboards for real-time analytics.

Network Requirements:
Client-Side (User/Driver Devices): Internet Connection: Mobile Data
(3G/4G/5G support) Wi-Fi (supporting at least 802.11n)

Server-Side (Backend Infrastructure):

- Internet Bandwidth: Scalable bandwidth depending on the size of the user
base (minimum 100Mbps scalable to 1Gbps for large-scale operations)
- Network Architecture.

Security and Access Control:

- Firewalls: Configurable to allow access to specific services (e.g., port-based
restrictions)
- SSL/TLS Protocols: For encrypting data between servers and client devices
- Virtual Private Cloud (VPC): For isolating backend components in cloud
environments.
 REPORTING TABLES

General / Base
REQ# PRIORITY DESCRIPTION RATIONALE
<ID> <value> <The system shall allow up to 100 concurrent users> <data suggests high of 45 concurrent users,
need room to expand>

Security

REQ# PRIORITY DESCRIPTION RATIONALE

KEY ASSUMPTIONS :
 User Accessibility: Users have access to smartphones and stable
internet connections to use the application efficiently.

 Demand for Convenience: There is a significant demand for

convenient, on-demand transportation services in urban and
suburban areas.

 Availability of Drivers: A sufficient number of qualified drivers are

willing to register on the platform and provide transportation services.

 Secure Payment Systems: Users prefer secure and convenient digital

payment methods, such as credit cards, mobile wallets, or bank
transfers, over cash payments.

 User Trust and Safety: Both passengers and drivers require safety
features, including driver/passenger verification, real-time tracking,

RISKS AND ITS MITIGATION:

1. Technical Failure (Server Downtime, Bugs)

Risk:
The app may experience technical failures such as server downtime,
slow response times, or bugs that hinder functionality.

Mitigation:
- Invest in scalable, cloud-based infrastructure with redundancy.
- Perform regular testing (QA, automated, and manual testing) and have
a dedicated development team to address bugs.
- Set up real-time monitoring and alerts for performance issues.

2. Security Breaches and Data Privacy

Risk:
Personal and payment data of users could be compromised due to
cyberattacks or inadequate security measures.

Mitigation:
- Implement encryption protocols for sensitive data (SSL/TLS, end-to-
end encryption).
- Follow industry-standard compliance regulations (GDPR, PCI-DSS).
- Regularly update security measures and perform vulnerability
assessments.
- Educate users on secure account management and offer features like
two-factor authentication (2FA).
3. Regulatory and Legal Compliance

Risk:
Failure to comply with transportation, data protection, or labor laws
could result in fines or business disruption.

Mitigation:
- Hire legal counsel to ensure the app complies with all relevant
regulations in the regions where it operates.
- Implement a flexible compliance strategy that adapts to evolving laws.
- Maintain records and audit trails for compliance reviews.

4. Driver and Vehicle Availability

- Risk: Insufficient availability of drivers and vehicles during peak times
could result in long wait times or service disruptions.
- Mitigation:
- Develop dynamic pricing models (surge pricing) to incentivize driver
availability during peak hours.
- Build a solid recruitment and retention strategy for drivers.
- Implement predictive analytics to forecast demand and allocate
resources efficiently.

5. Customer Dissatisfaction (UX/UI or Service Issues)

Risk:
Poor user experience (complex UI, slow navigation) or service-related
issues (unreliable drivers, delays) could lead to low customer retention.

Mitigation:
- Conduct user experience testing and incorporate user feedback to
improve the app's design and functionality.
- Provide reliable customer service (in-app chat, call centers) and quick
resolution of issues.
- Establish a rating and feedback system for both drivers and customers
to enhance quality control.