UNIVERSITY OF EDUCATION

Final Project Proposal

© University of Education
1
TABLE OF CONTENTS

FINAL PROJECT PROPOSAL GUIDE ...............................................................................3

1. INTRODUCTION ............................................................................................................ 3
1.1 PROJECT TITLE ............................................................................................................ 3
1.2 PROJECT OVERVIEW STATEMENT .............................................................................. 4
1.4 PROJECT GOALS & OBJECTIVES .................................................................................. 6
1.5 HIGH-LEVEL SYSTEM COMPONENTS .......................................................................... 6
1.6 LIST OF OPTIONAL FUNCTIONAL UNITS ..................................................................... 6
1.7 EXCLUSIONS ............................................................................................................... 7
1.8 APPLICATION ARCHITECTURE .................................................................................... 7
1.9 GANTT CHART ............................................................................................................ 7
1.10 HARDWARE AND SOFTWARE SPECIFICATION .......................................................... 8
1.11 TOOLS AND TECHNOLOGIES USED WITH REASONING............................................. 8

© University of Education
2
 Final Project Proposal

1. Introduction

The Smart Do Drive Application based on Android mobile is developed to people especially
adult to manage their riding efficiently. Existing drive methods to manage riding plan are
changed towards mobile application and by using smart phones. This application can help
user manage their basic drive condition and can be consider as a requirement in
environment recently. [1]The ADDIE (Analysis, Design, Development, Implementation,
Evaluation) method is divided into five main sections, namely the analysis phase, design
phase, development phase, implementation phase and evaluation phase. The use of the
ADDIE method ensures that the development of the system runs smoothly and according to
planning.[2]

1.1 Project Title

“Do Drive”

1.2 Project Overview Statement

We are going to create a Do-Drive application that helps the area of Vehari district
that the people will interact with this application and that helps them to their drives in a very
efficient way and in a short time. Before there is no application that was local for the people
of this region. Users can use this application anywhere in the world because it supports the
international language. Anselm's mobile application development services will deliver the
following results:
Developed your vision into an irresistible application:- You have the vision it's our job to
turn it into a reality. You'll get to watch as I transform your idea into a beautiful application,
asking questions and offering feedback along the way. Development isn't done until we test
to make sure your application.
Provided ongoing maintenance and support:- Given that after development phase we will
already be intimately familiar with your application, will stick around for three months to
help with maintenance, upgrades, and support.

© University of Education
3
 1.2 Project Overview Statement
Project Title:
Do Drive Application
Group Leader: Muhammad Shaban Tabassam
Project Members: 3 Group Members.
Name Registration # Email Address Signature
Muhammad Shaban
Bsf1904747 Bsf1904747@ue.edu.pk Shaban
Tabassam
Muhammad Waqas Bsf1905100 Bsf1905100@ue.edu.pk Waqas

Muhammad Shahid Bsf1904542 Bsf1904542@ue.edu.pk Shahid

Project Goal:

1.1.1 Preparing a best solution according to the need of the users.

1.1.2 Implementing solutions in their system.

1.1.3 Giving them a proposal of our new system which is correctly according to their problem.

1.1.4 To reduce risk of driving.

1.1.5 To increase customer satisfaction.

Objectives:
Sr.#
1 1. To study the mobile application in ride management
2 To develop a Smart Do Drive application that can help people to manage their riding.
3 To test the application functional and beneficial to us.
4 Control drive issues.
5 Manage time and Passengers according to drive.
6 Reduce Energy.
Project Success criteria:
1. User satisfaction and driver satisfaction.
2. Financial performance.
3. Market share, Regulatory compliance, Safety, and Innovation.
Assumptions, Risks and Obstacles:
1.Legal challenges and regulatory issues
2. Competition
3. Safety
4. Public perception
Organization Address (if any):

Type of project: Research

Target End users:

Development Technology: Oriented Structured

Platform: Android Based

Supervisor: Mr. Usman Ali

Approved By:
Date:
© University of Education
4
1.3 Project Goals & Objectives

Working in the competitive taxi market, the proposed taxi app can't afford to blend in with
thousands of others or strays from its vision. There is need for investment in this mobile
application project if we are to turn this idea into a remarkable end product that motivate
people to use it. Their main objective of the development of this app is to come up with a
product that will provide great value to its users and to the company.

1.3.0 What to expect

It takes time and patience to create something that works for you and is free of bugs and
other issues. Updates are required, but it's important to start with a sound foundation. We
believe in a thorough approach that provides our clients with as much engagement as they
request.

1.3.2 Framework

This involves: Functionality and content, Wireframes, the structural core of your app,
Branding and integrations, User Experience and User Interface, or UX and UI — essentially,
how you interact with the app, what makes it easy to use and desirable.

1.4 High-level system components

Table 1 FR_01 Sign-Up

ID NAME Description Input Output Basic Work Flow

User enter
In order to create
his/her User enters User will be
an account user,
FR_01 Sign-Up information email and set a created
enter a phone
for creating password. successfully.
number.
an account

Table 2 FR_02 Sign-In

ID NAME Description Input Output Basic Work Flow

User confirm
its information The user will The user will
Enter email
FR_02 Sign-in (i.e enter successfully Sign enter into the
and password.
password and In. food list category.
email).

© University of Education
5
 Table 3 FR_02 Update

ID NAME Description Input Output Basic Work Flow

Maintenance
Put new According to The user can see
on the
information. requirement all new updates
FR_03 Update application
Updates, show the all data and will enter the
and update a
delete. and credentials. all new details.
new version.

Table 4 FR_02 UI

ID NAME Description Basic Work Flow

This is the front-end of the
User application and includes the app The users interact with to request
FR_04
interface or website that users interact rides, pay for rides, and rate drivers.
with Do-Drive.

Table 5 FR_02 Ride Dispatch

ID NAME Description Basic Work Flow

This is the system that matches
Ride riders with nearby drivers based The users select type of ride and
FR_05
dispatch on their locations and vehicle according to their need.
availability.

Table 6 FR_02 Payments

ID NAME Description Input Output Basic Work Flow

Collecting payment
Passengers Passengers information from
This is the system
Payment select a ride successfully users and
FR_06 that handles
processing plan and pay achieve their processing
payment for rides
payments. goals. payments to
drivers.

© University of Education
6
 Table 7 FR_02 Map and Location

ID NAME Description Input Output Basic Work Flow

Do-Drive uses
Passengers Passengers
Map and maps and location Route drivers to
enter their reach
FR_07 location tracking to show pick up and drop
destination successfully on
tracking users the location off riders.
location. destination.
of nearby drivers.

Table 8 FR_02 Driver

ID NAME Description Input Output Basic Work Flow

Ratings are used to
Driver Do-Drive allows Passengers
Show rating help ensure a high-
FR_08 and rider riders and drivers enter their
points. quality experience
ratings to rate each other. feedbacks.
for both parties.

Table 9 FR_02 Customer

ID NAME Description Input Output Basic Work Flow

Do-Drive has a
team of customer Passengers
Solve all Make better
support ask their
Customer problems and relations between
FR_09 representatives questions
support gives response passengers and the
who handle and
quickly. Do-Drive team.
questions and problems.
issues from users.

1.5.0 App Features for Drivers

1. Driver Profile & Status - verification process of a driver should be done from the
administrator side of things (license, vehicle insurance etc). Status will inform as to
the availability of a driver.
2. Trip Alert - ability to receive trip orders to accept or deny, including information
regarding passenger's location, route, travel history.
3. Push Notifications - used for alerts, taxi app booking information (location, route,
payment.), trip changes, and completion.
4. Navigation & Route Optimization - offer the best trip route using Google Maps.
5. Driver Delivery Reports - provides statistical information regarding trips and earnings
on a daily/ monthly basis.6.Messaging - texting or calling to a passenger from the
app.

© University of Education
7
1.5.1 Do Drive App Features for Passengers

1. Registration - possible via email, Facebook, phone number with verification. The
most wide spread implementation of this feature is via social media.
2. Taxi Booking - refers to the feature represented on the screen for entering the
address, selection of car type, and set pickup location.
3. Fare Calculator - the customer can check the price for a ride beforehand. This feature
is a complex one to implement on the backend side of the system.
4. Driver Tracking - feature to observe the driver's movement to make updates during
or after the journey.
5. Payment - multiple payment variants may be implemented; cashless - in-app
payment via credit cards, services like PayPal, or simply in cash.
6. Push Notifications - vital element for informing; keeps passenger up-to-date with trip
request status, driver arrival time, driver and car details, etc.
7. Messaging - ability to contact the driver from the app.8.Driver Rating & Review -
corresponds to the service evaluation (driver, vehicle, trip, etc.).
8. Travel History - shows details from previous rides and transactions.
9. Customer Support
10. Pickup Location - this aallows passengers to find a driver based on their current
location automatically.
11. Ride Cancellation - offer ride cancellation within a predetermined period of time.

12. Interactive Map - feature provides possibility to observe all the taxi cabs on the map
in real time.

1.5.2 Admin Dashboard Features

1. Locations & Fares Management

2. Driver & User Management
3. Booking Management
4. Vehicle Management
5. Review Driver's Orders & Payoffs
6. Check Ratings & Reviews
7. Notifications Management
8. System Content Management & FAQ
9. Promotions & Discounts Management
10. Driver & User Support
11. Integration with Google Analytics
12. Key Performance Indicators
13. CRM (e.g sales force)

© University of Education
8
1.6 List of optional functional units

These are the optional functional units:

 Refund
 Feedback and reviews

1.7 Exclusions

We are also beginner in this field. As we work at the application we will find what should be
include and exclude. Exclusion would depend upon our experience with the development of
application.

1.8 Application Architecture

1.8.1 ER Diagram

© University of Education
9
1.8.1.1 Description of ER Diagram
An entity relationship diagram (ERD), also known as an entity relationship model, is a
graphical representation that depicts relationships among people, objects, places, concepts
or events within an information technology (IT) system.

1.8.2 Use Case Diagram

© University of Education
1
0
1.8.2.1 Actors:

 Admin
(Registration control, delete unauthorized profile, manage payment records,
confirm book ride)

 Passenger
(Sign-up, update profile, search ride, request for ride, book ride, share trip
detail, rate ride, make payments, leave tip, can logout from system)

 Diver
(Register, create ride bill, confirm book ride, receive tip, rate ride)

1.8.2.2 Description of use-case Diagram

Use-case diagram model the behavior of a system and helps to capture the
requirements of the system. These diagrams also identify the interactions between the
system and its actors. Passenger, admin, driver are the actors here. Actors would be able
to login and logout from the system. Admin can delete profile of any other actor and
manage payments and records. Passenger would be able to register, update profile, time
of ride, search ride, book ride, share trip detail, rate ride, update payments and cancel ride
and driver able to register, create reserve ride bill and payments. Admin manages the
overall task and able to login, delete profile, manage payments records and control the
whole system activities.. It is simple design architecture of expected application. These
actors performs individual task and represent well system for any user.

© University of Education
1
1
1.8.3 Class Diagram

© University of Education
1
2
1.8.3.1 Entities:

 Admin

 Driver

 Passenger

 Payment

 Vehicle

1.8.3.2 Description of class Diagram

A Class is a blueprint for an object. The entire point of Object-Oriented Design is not
about objects, it's about classes, because we use classes to create objects. Classes describe
the type of objects, while objects are usable instances of classes. The Driver class represents
Do-Driver app driver. The driver class has attributes driver's name, phone, Email, his id used
in the system, gender, and current location. The Driver class has methods like drive, pickup
and drop off which represents the action of the driver driving their car to pick up and pickoff
a passenger. The Vehicle class has attributes like type, id, model, and year. The Driver use
vehicles to deliver the passenger to destination. The Do-Driver passenger class in system
would represent a single passenger using the ride sharing service. It would contain
information about the passenger, such as their name, phone number, and payment method,
as well as methods for booking rides and canceling rides. The system uses a user profile class
to store and manage information about its users. This class diagram shows the various
attributes and methods associated with a user profile in the system. This class store users
data and after that this data will represent their profile in different way. They would be able
to edit their personal information that stored in the system. The Admin would be able to
manage overall system including managing user accounts, processing payments, and
monitoring ride requests and driver activity. This class diagram shows the various attributes
and methods associated with an admin in the system. Admin can remove illegal user and
coordinate whole system work.

© University of Education
1
3
1.8.4 DFD Level-1 Diagram

© University of Education
1
4
1.8.4.1 Description

A data flow diagram (DFD) maps out the flow of information for any process or system. It
uses defines symbols like rectangles, circles, and arrows. Passenger would be able to register
and login after authentication in the system. Driver will also need to login and
authentication. Passenger can check status of driver. Driver and passenger record will store
in the system database. If passenger done any type of driver booking for trip. Driver will
check passenger information and then check real time location and confirm trip booking this
will be store in the trip record database. After passenger verification of destination driver
will write amount and send to passenger for their desire destination. Driver will also send bill
detail to passenger will chose payment method. Admin can remove unauthorized passenger
and driver also can manage payments. Admin can see feedbacks, rating and complaints of
passenger for application and driver. Driver can see feedbacks, rating and complaints of
passenger. Driver can also send feedbacks, rating and complaints for application issues.

1.9 Gantt chart

1.1

© University of Education
1
5
1.10 Hardware and Software Specification

Software Specification
Operating System Microsoft Window 10 pro
Programming Tool Android Studio (version 2022(3.1))
Language JAVA 17, XML (version 1.0)
Database Firebase

Hardware Specification
Laptop Dell
Processor Intel(R) Pentium(R) CPU N3540 @ 2.16 GHz
RAM 4.00GB
Hard Disk SSD 128GB
Others Keyboard ,mouse

1.11 Tools and technologies

Android Studio:

Android Studio is the official [8] integrated development environment (IDE) for Google's Android
operating system, built on Jet Brains' IntelliJ IDEA software and designed specifically for Android
development.[5]

 Layout editors
 Resource editors and managers
 Android SDK Managers
 Virtual devices

Java:
Java is a programming language and computing platform first released by Sun Microsystems

in 1995. It has evolved from humble beginnings to power a large share of today’s digital world, by

providing the reliable platform upon which many services and applications are built.

Designing Tools:
 Draw.io[4]
 MS Excel

© University of Education
1
6
Firebase:

The Firebase Real-time Database is a cloud-hosted database in which data is stored as JSON.

The data is synchronized in real-time to every connected client. All of our clients share one Real-time

Database instances and automatically receive updates with the newest data, when we build cross-

platform applications with our iOS, and JavaScript SDKs.

Development Tools:

 Android studio:2022
 Android studio (3.1)
 Language: Java and XML
 Firebase

1.12 Expected Outcomes

Expected Out Comes

© University of Education
1
7
References:
[1] https://www.diva-portal.org

[2] http://staff.ustc.edu.cn/~cheneh/paper_pdf/2014/Hengshu-Zhu-KDD

[3] https://www.bidsketch.com/

[4] https://app.diagrams.net/

[5]https://developer.android.com/studio?gclid=Cj0KCQiA5NSdBhDfARIsALzs2ECYYD-
euWyDl-mOWcogGZMfIhYSlxI7UPcxVIKyCe1OqkCk_RZkfSgaAhjrEALw_wcB&gclsrc=aw.ds

© University of Education
1
8