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). Additionally, the current system lacks real-

time monitoring of trips and driver availability, as well as data analytics and reporting tools, limiting

operational visibility and decision-making.

To address these limitations, the proposed RURAL-RIDE system is introduced as a solution.

It adopts an Agile Software Development Methodology, promoting a flexible, iterative, and user-

focused development process. This approach enables continuous evaluation and refinement

throughout each phase of the project, from requirements analysis to testing and deployment. The

system is designed to incorporate essential features, including an online passenger booking

3|Page
module, automated driver assignment, route scheduling, fare computation, efficient Torno fare

collection, a rating and feedback system, and an analytics dashboard for monitoring trips and

revenue. These functionalities collectively support comprehensive data reporting and aim to

enhance overall operational efficiency and service delivery.

Statement of the Problem

The current rural transportation system operates using manual and unstructured processes
that result in several operational inefficiencies and service-related concerns. The reliance on the
“paunahan” or first-come, first-served system creates disorder in passenger allocation and leads to
unfair competition among drivers. In addition, the absence of a standardized fare matrix results in
inconsistent fare charges, reducing transparency and causing confusion among passengers.

Furthermore, the system depends heavily on manual record-keeping for driver registration,
membership fees, monthly dues, and terminal collections. This approach is time-consuming, prone
to human error, and makes it difficult to accurately track and retrieve records. The lack of a
centralized digital database also contributes to data inconsistencies and inefficient information
management.

Moreover, there is no real-time system for monitoring trips, tracking transactions, or providing
automated updates to users. Communication between passengers, drivers, and management
remains informal and unstructured, leading to delays and misunderstandings. The absence of
automated reporting tools further limits the ability of management to analyze operations and make
data-driven decisions.

In general, the current system lacks automation, organization, and digital support, resulting in
inefficient service delivery, reduced transparency, and poor data management. These challenges
highlight the need for a modern, integrated solution to improve the overall efficiency and reliability of
rural transportation services.

General Objective of the Project

4|Page
 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.

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.

5|Page
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

The capstone project titled “RURAL-RIDE: Rural Transport Reservation and Travel

Management System” is centered on the development of a web-based solution designed to

enhance and modernize the management of rural transportation services. It aims to improve

existing operations by digitizing key processes such as passenger booking, driver allocation, route

planning, and fare handling. In particular, the system introduces an organized booking platform, a

6|Page
fair driver assignment approach to replace the current “paunahan” practice, and a consistent fare

computation mechanism.

Moreover, the system supports the management of driver-related records and financial

transactions, including membership registration, fee collection, and digital documentation,

eliminating reliance on manual logbooks. It also integrates a feedback and rating feature to capture

passenger experiences, along with an analytics dashboard that provides insights into trips,

collections, and overall performance. An administrative interface is included to enable authorized

users to efficiently monitor operations, manage records, and generate reports.

In addition, the platform incorporates notification features to keep users updated on bookings

and transactions, supported by a centralized database for secure and efficient data handling.

However, the scope of this study is confined to the system’s design, functionality, and usability

within a single rural transportation setting, and does not extend to external system integration, GPS-

based tracking, or connections with third-party services.

Limitations of the Project

The RURAL-RIDE: Rural Transport Reservation and Travel Management System is

developed to improve the efficiency and management of rural transportation services; however,

certain limitations are recognized within the scope of this study. The system is designed to operate

within a single rural transportation setting only. It does not support integration with other transport

systems, terminals, or external platforms, which limits its applicability to a broader or multi-location

deployment. Additionally, the system does not include real-time GPS tracking or live location

7|Page
monitoring of vehicles, which may restrict its capability to provide precise trip tracking and

navigation features. Furthermore, the project focuses primarily on core functionalities such as

booking, driver assignment, fare calculation, and record management. Advanced features such as

mobile application support, online payment integration (e.g., e-wallets or banking systems), and

automated SMS notifications may be limited or not fully implemented, depending on system

constraints. The system also relies on stable internet connectivity for optimal performance. In rural

areas where internet access may be inconsistent or unreliable, system usability and accessibility

could be affected. Moreover, the study is limited to system development, usability, and functionality

testing, and does not cover long-term deployment, scalability testing, or real-world operational

evaluation.

Lastly, user adoption and system effectiveness depend on the willingness of drivers, passengers,

and management to transition from traditional manual processes to a digital platform, which may

pose challenges during implementation.

DOCUMENTATION OF THE EXISTENCE AND SERIOUSNESS

OF THE PROBLEM

The current rural transportation system continues to depend heavily on manual procedures

and informal practices, which lead to noticeable inefficiencies in daily operations. Passengers

typically wait at terminals without a structured booking system, relying on the “paunahan” approach

to secure a ride. This method often results in confusion, overcrowding, and unfair distribution of

8|Page
passengers among drivers. In addition, fare collection is handled verbally, without a standardized or

visible fare matrix, causing inconsistencies in pricing and a lack of transparency for commuters.

Operational tasks are also managed manually, particularly in the recording of driver

information, membership registration, and fee collections such as monthly dues and terminal

charges. These records are stored in logbooks, making the process time-consuming and prone to

inaccuracies. Staff are required to manually input, verify, and retrieve data, which increases

workload and reduces efficiency. As a result, tracking financial transactions and monitoring daily

operations becomes difficult and unreliable.

The seriousness of these issues becomes more evident when considering the risks

associated with manual systems. Records can easily be lost, misplaced, or incorrectly documented,

leading to discrepancies in data and delays in transactions. The absence of a centralized database

further complicates record management, making it challenging to access accurate and up-to-date

information when needed. This not only affects operational efficiency but also impacts accountability

and decision-making.

Moreover, the lack of real-time monitoring and communication systems creates uncertainty

for both passengers and drivers. Passengers have no means to reserve trips in advance or receive

updates, while drivers depend solely on physical presence at terminals to obtain passengers. This

limitation reduces convenience, wastes time, and contributes to an overall inefficient service

experience.

These challenges highlight the growing need for a more structured and technology-driven

approach. As demand for reliable and transparent transportation services increases, the limitations

9|Page
of the current system become more critical. Without proper automation, centralized data

management, and improved communication, the existing setup will continue to struggle in meeting

the needs of both operators and passengers, emphasizing the urgency for an improved digital

solution.

Photos/Images

Figure 1. Screenshots of the Current System

Figure 1 presents the current rural transportation setup, which operates through manual and

loosely organized practices. Passengers typically wait at terminals without a structured system,

relying on the “paunahan” method where drivers compete to pick up riders. This often creates

confusion, uneven distribution of passengers, and occasional conflict among drivers.

Fare handling is done informally, with prices communicated verbally instead of following a

fixed and visible rate. This results in inconsistent charges and limited transparency for passengers.

At the same time, records such as driver information, memberships, and fee collections are written

in logbooks, making data management slow and susceptible to errors.

10 | P a g e
 Daily operations follow a basic flow passengers wait, drivers compete, fares are agreed

upon, and transactions are recorded manually. Since there is no centralized or automated system,

monitoring trips, tracking collections, and retrieving information become inefficient. Communication

is also unstructured, with no system in place for updates or coordination.

Overall, the figure reflects a process that lacks structure, consistency, and system support,

highlighting the need for a more organized and digital approach to improve service delivery.

Problems Identified in the Current System

The current rural transportation system operates through manual and unstructured

processes, resulting in several operational inefficiencies that affect both service delivery and

management. These issues not only disrupt daily transportation activities but also significantly

impact passengers, drivers, and operators. The persistence of these concerns highlights the

limitations of the existing system and underscores the need for improvement.

One of the most critical problems is the unstructured dispatching system (“paunahan”),

where drivers compete to pick up passengers on a first-come, first-served basis. This creates

disorder at terminals, leading to confusion, unfair passenger distribution, and occasional conflicts

among drivers, particularly during peak hours when demand is high.

Another significant issue is the absence of a standardized fare system. Since fare rates

are communicated verbally without a fixed fare matrix, inconsistencies in pricing frequently occur.

11 | P a g e
This lack of transparency often results in misunderstandings between drivers and passengers and

reduces trust in the fairness of transportation services.

The system also suffers from manual record-keeping of transactions and collections,

including driver registration, membership fees, monthly dues, and terminal payments. These

records are stored in logbooks, making the process slow, inefficient, and highly prone to human

error, missing entries, and inconsistencies. Consequently, retrieving and verifying information

becomes difficult and unreliable.

In addition, there is a limited capacity for data utilization in decision-making. Because

records are not centralized or digitally organized, management faces challenges in analyzing

operational performance and identifying areas for improvement. This restricts the ability to make

informed and timely decisions that could enhance service efficiency.

Furthermore, there is an absence of automated reporting and analytics tools, which limits

the ability to monitor trips, collections, and operational performance. Since reporting is done

manually, it consumes time and increases the risk of inaccurate data interpretation, preventing

management from gaining clear and reliable insights.

Overall, these identified problems show that the current rural transportation system is outdated and

inefficient, particularly in terms of dispatching, fare standardization, record management, data

utilization, and reporting capabilities. The seriousness of these issues highlights the urgent need

for a digital and automated solution to improve fairness, transparency, and operational efficiency.

12 | P a g e
Seriousness of the Problem

The current rural transportation system operates using manual and unstructured processes

that result in several operational inefficiencies and service-related concerns. The reliance on the

“paunahan” or first-come, first-served system creates disorder in passenger allocation and leads to

unfair competition among drivers. In addition, the absence of a standardized fare matrix results in

inconsistent fare charges, reducing transparency and causing confusion among passengers.

Furthermore, the system depends heavily on manual record-keeping for driver registration,

membership fees, monthly dues, and terminal collections. This approach is time-consuming, prone

to human error, and makes it difficult to accurately track and retrieve records. The lack of a

centralized digital database also contributes to data inconsistencies and inefficient information

management.

Moreover, there is no real-time system for monitoring trips, tracking transactions, or providing

automated updates to users. Communication between passengers, drivers, and management

remains informal and unstructured, leading to delays and misunderstandings. The absence of

automated reporting tools further limits the ability of management to analyze operations and make

data-driven decisions.

In general, the current system lacks automation, organization, and digital support, resulting in

inefficient service delivery, reduced transparency, and poor data management. These challenges

highlight the need for a modern, integrated solution to improve the overall efficiency and reliability of

rural transportation services.

13 | P a g e
Need for a Digital Solution

The current rural transportation system is heavily dependent on manual processes and

unstructured practices, making it inefficient, inconsistent, and difficult to manage. These limitations

highlight the urgent need for a digital solution that can improve the overall operation of rural

transport services. A web-based system such as the proposed RURAL-RIDE platform is necessary

to automate key processes including passenger booking, driver assignment, fare computation, and

record management, thereby reducing reliance on manual transactions and improving operational

accuracy.

In addition, a digital system is needed to establish a centralized and organized database for

all transportation-related records, including driver information, fees, and trip transactions. This

ensures faster data retrieval, minimizes the risk of data loss or duplication, and improves the

accuracy of financial and operational records. It also helps streamline communication and

coordination between passengers, drivers, and management by providing a more structured flow of

information.

Furthermore, the implementation of a digital solution enhances transparency and efficiency

by enabling systematic processing of transactions and better monitoring of daily operations.

Features such as automated reporting and data tracking allow management to gain clearer insights

into system performance and make more informed decisions.

Overall, adopting a digital system is essential to improve efficiency, fairness, and service

quality in rural transportation, ensuring that operations become more organized, reliable, and

responsive to the needs of both passengers and drivers.

14 | P a g e
 TECHNICAL REQUIREMENTS

The following materials will be used in the development of the proposed system entitled

“RURAL-RIDE: Rural Transport Reservation and Travel Management System.” for Enhanced

Passengers and Drivers Services

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

15 | P a g e
 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
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
16 | P a g e
 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.

17 | P a g e
 PROJECT SCHEDULES OF THE PROJECT (GANTT CHART)

SPRINT 1 (Objectives 1 & 2)

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.

18 | P a g e
SPRINT 3 (Objective 5)

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.

19 | P a g e
 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
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.

20 | P a g e
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.

Entity-Relationship Diagram

Figure 2. Entity-Relationship Diagram of the System

21 | 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.
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.

22 | P a g e
 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.
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.

23 | P a g e
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
)
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

24 | P a g e
 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
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

25 | P a g e
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
settled.

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

Column Name Data Type Constraints Description

26 | P a g e
 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)

2. Admin Profile (Subtype) Admin

 admin_id (PK)
 user_id (FK)

3. Dispatcher Profile (Subtype) Dispatcher

 dispatcher_id (PK)
27 | P a g e
  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)
 assignment_id (FK)
 travel_date
 status (Pending / Confirmed / Cancelled)

9. Torno Collection TornoCollection

 torno_id (PK)
 driver_id (FK)
28 | P a g e
  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

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

Objective 1: Manage Credential Document Details

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

Objective 2: Students to Request Credentials

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

Objective 3: Students with Automated Status Updates via Email

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

Objective 5: Data Dashboard

33 | P a g e
Objective 6: Generated Reports

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

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

36 | P a g e