RURAL-RIDE: Rural Transport Reservation and Travel Management System

MICHAEL JAMES G. SERA

SUMMER P. PARIAN
CLARK ERNEST A. BACNES

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE SUBJECT IT221

– ADVANCED DATABASE SYSTEMS

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

2nd Semester | A.Y. 2025-2026

June 2026

1|Page
 TABLE OF CONTENTS

TITLE PAGE
Title Page 1
Background of the Project 0
Problem Statement 0
Objectives of the Project 0
Significance of the Project 0
Scope and Limitations 0
Documentation of the Existence and Seriousness of the Problem 0
Documentation of the Current System 0
Problems Identified in the Current System 0
Seriousness of the Problem 0
Need for a Digital Solution 0
Methodology 0
Agile Methodology 0
System Architecture 0
Technical Requirements 0
Hardware Requirements 0
Software Requirements 0
Budgetary Requirements 0
Project Schedules (Gantt Chart) 0
System Design and Development 0
Entity Identification, Cardinality, and Relationships 0
Entity Relationship Diagram 0
Data Dictionary 0
Normalization Process 0
System Screenshots 0
Appendix A: Approved Letter Permission to Conduct Data/Information Gathering 0

Appendix B: Pictorials 0

2|Page
 INTRODUCTION

Background of the Project

This project, "RURAL-RIDE: Rural Transport Reservation and Travel Management System," is
submitted by Michael G. Sera, Summer P. Parian, and Clark Ernest A. Bacnes as a partial
fulfillment of the requirements for IT221 – Advanced Database Systems. Developed for the
Bachelor of Science in Information Technology program during the 2nd Semester, A.Y. 2025-2026,
this system aims to revolutionize rural transportation management by introducing a digital platform
that addresses current operational challenges.

The current system, largely reliant on manual processes and traditional methods, faces significant
inefficiencies. These include an unfair "Paunahan" (first-come, first-served) dispatching system that
leads to disorganization and driver disputes, the absence of a standardized fare matrix resulting in
inconsistent verbal fare charges, and the inconvenient manual logging of all records, from driver
applications and membership fees (Php 250 for new, Php 200 for returning drivers) to monthly dues
(Php 30) and terminal fees (Php 10.00).

To overcome these limitations, the RURAL-RIDE system is being developed. It will leverage an
Agile Software Development Methodology, ensuring a flexible, iterative, and user-centric approach
to development. This methodology allows for continuous feedback and adaptation throughout the
project lifecycle, from requirement gathering to testing and implementation. The system's
architecture will be designed to support key features such as a passenger booking system, driver
assignment, route scheduling, automated fare calculation, streamlined Torno Fare Collections, a
service ratings and feedback mechanism, and an analytics dashboard for trip and collection
insights, culminating in comprehensive data reporting.

Statement of the Problem

The existing rural transportation system is plagued by several issues that hinder efficiency
and fairness:

 Unfair Dispatching System ("Paunahan"): The current practice of drivers competing for
passengers on a "first-come, first-served" basis leads to disorganization, unfairness, and
potential conflicts among drivers.

3|Page
  Absence of a Standardized Fare Matrix: The lack of a visible and consistent fare structure,
with fares communicated verbally, results in varied charges for passengers and a general
lack of transparency.
 Manual Record-Keeping and Collections: All records, including driver applications,
membership fees (Php 250 for new, Php 200 for returning), monthly dues (Php 30), and
terminal fees (Php 10.00), are managed manually through logbooks. This process is
inefficient, prone to errors, and lacks robust data management capabilities.

General Objective of the Project

To develop and implement a comprehensive digital system, "RURAL-RIDE: Rural Transport

Reservation and Travel Management System," that enhances the efficiency, transparency, and

overall management of rural transportation services by automating key processes such as

passenger booking, driver assignment, route scheduling, fare collection, and data reporting.

Specific Objectives of the Project

Specifically, this project aims to:

1. Develop a Passenger Booking System for efficient trip reservations.

2. Implement a fair Driver Assignment mechanism.

3. Establish effective Route Scheduling for optimized travel.

4. Automate accurate Fare Calculation.

5. Streamline Torno Fare Collections, including membership fees, monthly dues,

and terminal fees.

6. Incorporate Service Ratings and Feedback from passengers to enhance service

quality.

7. Provide a Trip and Collections Analytics Dashboard for management insights.

8. Facilitate comprehensive Data Reporting for operational analysis.

4|Page
Significance of the Project

The RURAL-RIDE system will be a big help to everyone involved in rural transportation. It's a major
step forward in making things work better, giving people a better experience, and making everything
run more smoothly.

To the Passengers: This system will provide a transparent and convenient booking experience,
clear fare information, and a platform for feedback, leading to increased satisfaction and trust in
rural transport services.
To the Drivers: The RURAL-RIDE system will introduce a fairer dispatching and assignment
process, reducing competition-related conflicts and ensuring equitable opportunities. It will also
simplify the management of their financial contributions (fees and dues), allowing them to
concentrate on providing reliable service.
To the Management/Operators: The system offers advanced capabilities for operational oversight
through an analytics dashboard and data reporting. This will enable efficient management of
resources, better financial tracking, and informed decision-making to improve overall service
delivery.
To Future Researchers: This project will serve as a valuable reference for future studies focusing
on the development and implementation of digital management systems within the transportation
sector, particularly in rural contexts. It demonstrates the application of advanced database concepts
and agile methodologies.

Scope of the Project

Discussion starts here.

Limitations of the Project

Discussion starts here.

5|Page
 DOCUMENTATION OF THE EXISTENCE AND SERIOUSNESS
OF THE PROBLEM

Documentation of the Current System

Discussion starts here.

Photos/Images

Figure 1. Screenshots of the Current System

Problems Identified in the Current System

The current rural transportation system suffers from several significant issues:

Problem Identified 1: Unfair Dispatching System ("Paunahan").

Problem Identified 2: Absence of a Standardized Fare Matrix

Problem Identified 3: Manual Record-Keeping and Collections

Problem Identified 4: Discussion starts here.

Problem Identified 5: Discussion starts here.

6|Page
Seriousness of the Problem

Discussion starts here.

Need for a Digital Solution

Discussion starts here.

TECHNICAL REQUIREMENTS

Discussion starts here.

Table 1. Hardware Requirements

ITEM SPECIFICATION
Processor Intel Core i5 or AMD Ryzen 3 (Minimum)
Memory 8GB DDR4 RAM
Hard Disk 256GB SSD (Solid State Drive)
Power Supply 500W - 650W PSU
Monitor 13.3" FHD Anti-Glare Display
Internet / WiFi PLDT Home Fibr (High-speed Fiber
Input Devices Built-in Backlit Keyboard and Touchpad

Table 1 shows the hardware requirements needed for the system; this includes the minimum

hardware parts of computer to support the development process of the system.

Table 2. Software Requirements

ITEM SPECIFICATION
Programming Language (front-end) HTML5, CSS, JavaScript
Web Scripting Languages PHP (Server-side)
Cross-platform web server XAMPP (Apache, MySQL)
Web Designing Tools CSS3

7|Page
 Project Management Tool Ms project
Diagramming and vector graphics [Link] (Database Relationship Mapping)
Database Application (back-end) MySQL
Operating System Windows 11

Table 2 shows the software requirements needed to develop the system. This includes the

minimum operating system, front end and backend software as well as the domain name needed to

deploy the system online.

Table 3. Budgetary Requirements

NO. QTY ITEM DESCRIPTION UNIT COST TOTAL COST

(PHP) (PHP)
A. Hardware
Laptop dell latitude 5320 (1) 20,000 20,000
Processor, RAM, SSD, Power
Supply, Monitor
Internet Connection ISP (1) 1,600.00 1, 600.00
(Monthly Subscription)
Printer 3,500.00 3,500.00
B. Software
2 1 package XAMPP
Installation Visual Studio Code
Operating System
MS Project 2013
[Link]
Localhost Server

C. Supplies and Materials

3 1 Reams A4 couponed bond 235.00 235
(substance 20)
Subtotal 25,335
Contingency (10% of the Subtotal) 25,533
Grand Total 27,533

8|Page
 Table 3 shows an itemized summary of expenditures for a given period along with the

financing during a period of the study.

METHODS TO BE USED IN DEVELOPING THE SYSTEM

Figure 3. Agile Software Development Methodology

Agile Software Development Methodology was designed to ensure that system requirements

are met efficiently in existing computerized systems. It provides a structured approach to

requirement gathering, planning, development, implementation, and testing, ensuring a logical and

systematic process. This methodology emphasizes flexibility, continuous feedback, and iterative

development, allowing for adaptability to changes while maintaining technical accuracy and user

satisfaction.

PROJECT SCHEDULES OF THE PROJECT (GANTT CHART)

SPRINT 1 (Objectives 1 & 2)

9|Page
Figure 4. SPRINT 1 Project Schedules

Figure 4 shows the timeline, tasks and duration of the project and the expected completion

date of SPRINT 1.

SPRINT 2 (Objectives 3 & 4)

Figure 5. SPRINT 1 Project Schedules

Figure 5 shows the timeline, tasks and duration of the project and the expected completion

date of SPRINT 2.

SPRINT 3 (Objective 5)

10 | P a g e
Figure 6. SPRINT 3 Project Schedules

Figure 6 shows the timeline, tasks and duration of the project and the expected completion

date of the SPRINT 3.

SPRINT 4 (Objective 6)

Figure 7. SPRINT 5 Project Schedules

Figure 7 shows the timeline, tasks and duration of the project and the expected completion

date of the SPRINT 4.

DATABASE IMPLEMENTATION

Entities and Attributes

Entity Name Primary Attributes
Key
Admin admin_id name, email, username, contact_no, password, role
Dispatcher dispatcher_id name, email, username, contact_no, password, role
Driver driver_id name, email, username, contact_no, password, role,
license_number, status
Passenger passenger_id name, email, username, contact_no, password, role
Route route_id origin, destination, scheduled_time, regular_fare
DriverAssignment assignment_id driver_id (FK), route_id (FK), dispatcher_id (FK), date,
status
Booking booking_id passenger_id (FK), assignment_id (FK), travel_date, status
TornoCollection torno_id driver_id (FK), dispatcher_id (FK), amount_paid,
collection_date
AssociationFee fee_id driver_id (FK), admin_id (FK), fee_type, amount,
payment_date
11 | P a g e
Feedback feedback_id booking_id (FK), passenger_id (FK), rating_score,
comments, date

Cardinality and Relationships

Entities Involved Cardinality Relationship
Dispatcher → DriverAssignment 1:M One dispatcher manages multiple driver
assignments.
Driver → DriverAssignment 1:M One driver is assigned to multiple trips.
Route → DriverAssignment 1:M One route is applied to multiple trip
schedules.
Dispatcher → TornoCollection 1:M One dispatcher records multiple daily torno
payments.
Admin → AssociationFee 1:M One admin manages membership and
monthly fee records.
Passenger → Booking 1:M One passenger can book multiple trips.
Assignment → Booking 1:M One scheduled trip can have many passenger
bookings.
Booking → Feedback 1:1 One booking corresponds to one service
feedback.

12 | P a g e
Entity-Relationship Diagram

Figure 2. Entity-Relationship Diagram of the System

13 | P a g e
Data Dictionary

tbl_admin (Profile for Association President

Column Data Type Constraints Description
Name
Admin_id INT PK, Auto- Unique identifier for all users.
Increment
Name VARCHAR(100) Not Null Complete name of the President.
Email VARCHAR(100) Unique, Not Null Email address for notifications.
username VARCHAR(50) Unique, Not Null Used for system login.
Contac_no VARCHAR(15) Not Null Active mobile number.

14 | P a g e
 Password VARCHAR(255) Not Null Encrypted login password.
role VARCHAR(20) Not Null Admin, Dispatcher, Driver, or
Passenger.

Table 8. Dispatcher Table (tbl_dispatcher) Profile for managing daily dispatches

Column Data Type Constraints Description

Name
dispatcher_i INT PK, Auto- Unique identifier for all users.
d Increment
Name VARCHAR(100) Not Null Complete name of the dispatcher.
Email VARCHAR(100) Unique, Not Null Email address for notifications.
username VARCHAR(50) Unique, Not Null Used for system login.
Contac_no VARCHAR(15) Not Null Active mobile number.
Password VARCHAR(255) Not Null Encrypted login password.
role VARCHAR(20) Not Null Admin, Dispatcher, Driver, or
Passenger.

Table 9. Driver Table (tbl_driver) Profile for registered vehicle operators.

Column Name Data Type Constraints Description
Driver_id INT PK, Auto- Unique identifier for all users.
Increment
Name VARCHAR(100 Not Null Complete name of the driver.
)
Email VARCHAR(100 Unique, Not Null Email address for notifications.
)
username VARCHAR(50) Unique, Not Null Used for system login.
15 | P a g e
Contac_no VARCHAR(15) Not Null Active mobile number.
Password VARCHAR(255 Not Null Encrypted login password.
)
license_number VARCHAR(50) Unique, Not Null Professional Driver's License.
status VARCHAR(20) Not Null Active or Inactive status.
role VARCHAR(20) Not Null Admin, Dispatcher, Driver, or
Passenger.

Table 10. Passenger Table (tbl_passenger) Profile for commuters using the booking system

Column Data Type Constraints Description

Name
passenger_i INT PK, Auto- Unique identifier for all users.
d Increment
Name VARCHAR(100) Not Null Complete name of the passenger.
Email VARCHAR(100) Unique, Not Null Email address for notifications.
username VARCHAR(50) Unique, Not Null Used for system login.
Contac_no VARCHAR(15) Not Null Active mobile number.
Password VARCHAR(255) Not Null Encrypted login password.
role VARCHAR(20) Not Null Admin, Dispatcher, Driver, or
Passenger.

Table 11. Route Table (tbl_route) Stores the standard routes and fare rates

Column Name Data Type Constraints Description

route_id INT PK, Auto- Unique Route ID..
Increment
origin VARCHAR(100 Not Null Dispatch starting point
16 | P a g e
 )
destination VARCHAR(100 Unique, Not Null Final drop-off point..
)
scheduled_tim VARCHAR(50) Unique, Not Null Standard time of departure..
e
regular_fare VARCHAR(15) Not Null Computed standard fare rate.

Table 12. Driver Assignment Table (tbl_driver_assignment) The dispatch record linking
driver, route, and dispatcher.

Column Name Data Type Constraints Description

assignment_id INT PK, Auto- Unique Dispatch/Assignment ID
Increment
driver_id INT Not Null The assigned driver
route_id INT Unique, Not Null The assigned route.
assignment_dat DATE Not Null Date of the scheduled trip.
e
dispatcher_id INT Not Null Dispatcher who authorized the
trip.
status VARCHAR(20) Scheduled, On-Trip, or
Completed.

Table 13. Booking Table (tbl_booking) Stores passenger trip reservations.

Column Name Data Type Constraints Description

booking_id INT PK, Auto- Unique Booking ID.
Increment
passenger_id INT FK, Not Null The passenger who booked the
trip.
assignment_id INT FK, Not Null Reference to specific

17 | P a g e
 tbl_driver_assignment.
travel_date DATE Not Null Intended date of travel.
status VARCHAR(20) Not Null Pending, Confirmed, or
Cancelled.

Table 14. Torno Collection Table (tbl_torno_collection) Tracks daily terminal fees paid by
drivers.

Column Name Data Type Constraints Description

torno_id INT PK, Auto- Unique Torno payment ID
Increment
driver_id INT FK, Not Null The driver who paid the fee.
dispatcher_id INT FK, Not Null Dispatcher who received the
payment.
amount_paid DECIMAL(10,2) Not Null Daily terminal fee amount.
collection_date DATETIME Not Null Exact date and time of
payment.

Table 15. Association Fees Table (tbl_association_fees) Tracks membership and monthly
dues for the association.

Column Name Data Type Constraints Description

fee_id INT PK, Auto- Unique Fee record ID.
Increment
driver_id INT FK, Not Null The driver who paid the dues.
admin_id INT FK, Not Null Admin/Secretary who
recorded the fee.
fee_type VARCHAR(50) Not Null Membership or Monthly Due..
amount DECIMAL(10,2) Not Null Amount paid for the fee.
payment_date DATE Not Null Date when the fee was

18 | P a g e
 settled.

Table 16. Feedback Table (tbl_feedback) Stores passenger ratings for the trip.

Column Name Data Type Constraints Description

feedback_id INT PK, Auto- Unique Feedback ID.
Increment
booking_id INT FK, Not Null Reference to the specific
booking
passenger_id INT FK, Not Null The passenger giving the
rating.
rating_score INT Not Null Rating value (1 to 5 stars).
comments TEXT Nullable Optional text review from the
passenger.
DATETIME Not Null Date and time the feedback
date_submitte was sent.
d

Data Normalization Process

1. User (Supertype Entity for Admin, Dispatcher, Driver, Passenger) To avoid redundancy
among Admin, Dispatcher, Driver, and Passenger, a single user table is recommended to store
common personal information and login credentials. User

 user_id (PK)
 name
 email
 username
 contact_no
 password
 role (Admin / Dispatcher / Driver / Passenger)
19 | P a g e
2. Admin Profile (Subtype) Admin

 admin_id (PK)
 user_id (FK)

3. Dispatcher Profile (Subtype) Dispatcher

 dispatcher_id (PK)
 user_id (FK)
 terminal_assigned

4. Driver Profile (Subtype) Driver

 driver_id (PK)
 user_id (FK)
 license_number
 plate_number
 status (Active / Inactive)

5. Passenger Profile (Subtype) Passenger

 passenger_id (PK)
 user_id (FK)
 address

6. Route Route

 route_id (PK)
 origin
 destination
 scheduled_time
 regular_fare

7. Driver Assignment DriverAssignment

 assignment_id (PK)
 driver_id (FK)
 route_id (FK)
 dispatcher_id (FK)
 assignment_date
 status (Scheduled / On-Trip / Completed)

8. Booking Booking

 booking_id (PK)
 passenger_id (FK)
20 | P a g e
  assignment_id (FK)
 travel_date
 status (Pending / Confirmed / Cancelled)

9. Torno Collection TornoCollection

 torno_id (PK)
 driver_id (FK)
 dispatcher_id (FK)
 amount_paid
 collection_date

10. Association Fee AssociationFee

 fee_id (PK)
 driver_id (FK)
 admin_id (FK)
 fee_type (Membership / Monthly Due)
 amount
 payment_date
 remarks

11. Feedback Feedback

 feedback_id (PK)
 booking_id (FK)
 passenger_id (FK)
 rating_score (1-5 Stars)
 comments
 date_submitted

SYSTEM SCREENSHOTS

Objective 1: Manage Administrative Staff Accounts

21 | P a g e
Objective 1: Manage Academic Tracks

Objective 1: Manage Credential Document Details

22 | P a g e
Objective 1: Manage Credential Requests

Objective 2: Students to Request Credentials

23 | P a g e
Objective 2: Generate Requests Slip with QR code

Objective 3: Students with Automated Status Updates via Email

24 | P a g e
Objective 4: Scan and Verify Request Slip with QR code

Objective 5: Data Dashboard

25 | P a g e
Objective 6: Generated Reports

26 | P a g e
APPENDIX A: Approved Letter Permission to Data and Information Gathering

27 | P a g e
APPENDIX B: Pictorials during the Conduct of Data and Information Gathering

28 | P a g e