System Name: RideGuide

System Type: Web Application

Architecture Style: 3-Tier Architecture

1. System Selection & Problem Definition

1.1 System Type Selected

Web Application - A responsive web-based platform designed for commuters to access

local transport information including tricycle and jeepney routes, fares, and terminal
locations.

1.2 Real-World Problem Identification

Filipino commuters, especially in provincial areas and smaller municipalities,
navigate local transportation in a state of information blindness, they travel daily
without knowing the correct routes, proper fare rates, or terminal locations.

This leads to:

 Overcharging by drivers who take advantage of uninformed passengers.
 Confusion for new commuters (students, workers, tourists) unfamiliar with
local routes.
 Inefficient travel planning due to lack of centralized route information.
 Wasted time and money from taking wrong routes or unnecessary transfers.
 No accountability for drivers who deviate from standard fares.

1.3 Proposed Software Solution

RideGuide is a FREE, web-based local transport information platform that provides
commuters with simple yet comprehensive tools to:
 Find routes between any two locations
 Calculate accurate fares based on official fare matrix
 Locate terminals with operating hours and available routes
 Access driver/operator information for verified routes
 Submit feedback and report fare violations
The platform transforms the confusing local transport system into an organized,
searchable database that any commuter can access from their phone or computer.

Solution Approach

Problem RideGuide Solution

No route visibility Searchable route database with step-by-

step directions
Fare overcharging Official fare calculator based on LGU-
approved rates
Unknown terminal locations Complete terminal directory with maps
and details
No driver accountability Driver/operator registration with feedback
system
Scattered information Centralized platform accessible 24/7 via
web browser
Technology barriers Simple interface, works on any device
with a browser

1.4 Core Purpose

"To empower Filipino commuters with a reliable, free, and accessible platform
that provides accurate local transport information, enabling them to travel confidently
with knowledge of proper routes and fair prices."

In simple terms: "Tulungan ang mga komyuter na malaman ang tamang ruta at presyo
ng pamasahe." (Help commuters know the correct routes and fare prices.)
1.5 Primary Functionalities
Functionality Description Priority
User Registration & Email/password login, Must Have
Authentication commuter and operator
account types
Route Finder Search routes by Must Have
origin/destination, view step-
by-step directions,
landmarks, and transfer
points
Fare Calculator Calculate fares based on Must Have
distance, vehicle type, and
official fare matrix
Terminal Directory Browse terminals with Must Have
location, operating hours,
contact info, and available
routes
Driver/Operator Registration Operators can register their Must Have
routes, vehicles, and
schedules for verification
Feedback System Rate routes, report issues, Must Have
submit fare violation
complaints
Admin Dashboard Manage users, routes, Must Have
fares, terminals, and
moderate feedback
Route Maps Visual display of routes Should Have
using interactive maps
(Leaflet + OpenStreetMap)
Low Fare Alerts Notify users of fare updates Should Have
or special rates
Search History Save frequently searched Should Have
routes for quick access
Multi-language Support Filipino/Taglish and English Could Have
interface options
Offline Route Cache Save route information for Could Have
offline viewing
2. Define Objectives, Scope & Users
2.1 SMART Objectives
1. Fast Route Search
 Specific: Display complete route information (directions, fare, terminals) within 3
seconds of search.
 Measurable: Search response time is less than 3 seconds.
 Achievable: This can be done with optimized database queries and proper
indexing.
 Relevant: Helps commuters quickly find routes without waiting, especially when
in a hurry.
 Time-bound: Ready within 4 weeks from the start of development.
2. Accurate Fare Information
 Specific: Provide fare calculations that match 100% with LGU-approved fare
matrix for all registered routes.
 Measurable: One hundred percent accuracy based on official fare rates.
 Achievable: This can be done by inputting the official fare matrix and using
distance-based calculations.
 Relevant: Prevents overcharging and gives commuters confidence in fare
information.
 Time-bound: Fare calculator functional within 3 weeks of development.
3. Comprehensive Route Database
 Specific: Register at least 50 verified local transport routes within the target
municipality.
 Measurable: 50 verified routes in the database.
 Achievable: This can be done through partnerships with local transport offices
and operator registration.
 Relevant: Shows the platform has useful and comprehensive coverage of local
routes.
 Time-bound: Achieve this within 2 months after public launch.
4. User Adoption in Target Area
 Specific: Reach 200 registered commuter users and 30 registered operators in
the target municipality.
 Measurable: 200 commuter accounts and 30 operator accounts.
 Achievable: This can be done through local promotion, social media, and
transport office partnerships.
 Relevant: Demonstrates that the platform serves a real need in the community.
 Time-bound: Achieve this within 3 months after public launch.
5. Reliable Feedback System
 Specific: Implement a feedback system that allows commuters to rate routes
and report fare violations with photo evidence.
 Measurable: System can receive and store at least 100 feedback submissions
without errors.
 Achievable: This can be done with a simple form submission and database
storage.
 Relevant: Creates accountability for drivers and helps improve service quality.
 Time-bound: Ready within 4 weeks from the start of development.
2.2 Project Scope
RideGuide's scope is planned so the project stays focused on the main needs of
commuters in the target municipality while remaining realistic with the time, budget, and
technical limits. This scope is divided into Included Features and Excluded Features.
Included Features
1. Platform and Technology
o A responsive web application accessible on desktop and mobile browsers.
o Uses CodeIgniter 4 (PHP framework) for backend development.
o Uses MySQL database for data storage.
o Uses Bootstrap 5 for responsive frontend design.
o Hosted locally using XAMPP or deployed on free hosting (InfinityFree,
000webhost).

2. User Accounts and Security (User Management)

o Register using email and password.
o Two account types: Commuter and Operator.
o Create and edit user profile (name, contact details, location).
o Admin accounts for system management.
o Security options:
 Password hashing (CI4 built-in)
 Session management
 Password recovery via email
3. Route Management (Routes)
o Users can search and view routes, including:
 Route name and code
 Origin and destination points
 List of stops/landmarks along the route
 Vehicle type (tricycle, jeepney, multicab)
  Estimated travel time
 Operating hours
o Admin/Operators can:
 Add new routes with complete details
 Edit existing route information
 Deactivate discontinued routes
o Route search features:
 Search by origin and destination
 Filter by vehicle type
 View route on map ([Link] + OpenStreetMap)
4. Fare Management (Fares)
o Official fare matrix based on LGU rates
o Fare calculator features:
 Calculate fare based on distance
 Different rates per vehicle type
 Special fare categories (student, senior, PWD)
o Admin can:
 Update fare matrix when rates change
 Set minimum fare and per-kilometer rate
 View fare history/changes
5. Terminal Directory (Terminals)
o Complete list of transport terminals, including:
 Terminal name and location
 Operating hours
 Contact information
 Available routes from terminal
 Facilities (waiting area, restroom, etc.)
o Search and filter terminals by:
  Location/barangay
 Vehicle type served
 Routes available
o Map view showing terminal locations
6. Operator Registration (Operators)
o Transport operators can register their:
 Business/operator name
 Contact information
 Routes operated
 Number of vehicles
 Franchise/permit details (optional)
o Admin verification process before public listing
o Operator dashboard showing:
 Their registered routes
 Feedback received
 Profile management
7. Feedback and Rating System (Feedback)
o Commuters can:
 Rate routes (1-5 stars)
 Write reviews about their experience
 Report fare violations with details
 Upload photo evidence (stored in server)
o View feedback features:
 Average ratings per route
 Recent reviews
 Filter by rating or date
o Admin moderation:
 Review and approve/reject feedback
  Respond to complaints
 Generate feedback reports
8. Admin Dashboard (Admin)
o System statistics:
 Total users, routes, terminals
 Recent activity
 Feedback summary
o User management:
 View all users
 Activate/deactivate accounts
 Assign roles
o Content management:
 Manage routes, fares, terminals
 Approve operator registrations
 Moderate feedback
o Reports:
 Route usage statistics
 Most searched routes
 Feedback analysis
9. Language Options
o Users can choose Filipino (Taglish) or English interface.
Excluded Features
1. Mobile Native Application
o No Android or iOS native app for now.
o Web application only, accessible via mobile browser.
2. Real-Time GPS Tracking
o No live tracking of vehicles or drivers.
o No real-time arrival predictions.
 o Requires paid APIs and complex integration.
3. Online Payment Integration
o No fare payment through the app.
o No GCash, Maya, or card payment processing.
o Information platform only, not a booking system.
4. Booking and Reservation System
o No seat booking or ride reservation.
o No scheduling of rides in advance.
5. Driver Verification (KYC)
o No government ID verification for drivers.
o No background check integration.
o Basic registration only with admin approval.
6. SMS Notifications
o No SMS alerts for fare updates or route changes.
o Requires paid SMS gateway.
o Email notifications only (using free SMTP).
7. Advanced Analytics and AI
o No route optimization algorithms.
o No demand prediction.
o No machine learning features.
8. Multi-City/Provincial Coverage
o Initial deployment for single municipality only.
o No automatic expansion to other areas.
2.3 User Personas
User Persona 1 – Maria (Student Commuter)
1. Background
o Maria is 19 years old.
o She is a college student studying in a university in the city.
o She commutes daily from her barangay to the school.
o She mostly speaks Filipino/Taglish and is comfortable with basic English.
2. Phone and Technology Use
o She uses an Android smartphone.
o She regularly uses:
 Facebook and Messenger (for communication)
 Google Maps (for directions in the city)
 GCash (for allowance and payments)
o She has mobile data but tries to save it for important use.
o She is comfortable using websites and apps.
3. Commuting Situation
o She takes a tricycle from her home to the terminal.
o Then she rides a jeepney to the city.
o Sometimes she needs to transfer to another jeepney near her school.
o Her daily transport budget is around ₱100-150.
o She commutes 5-6 days a week.
4. Goals Maria wants RideGuide to help her:
o Find the cheapest route to school.
o Know the correct fare so she won't be overcharged.
o Discover alternative routes when her usual route is full or not available.
o Find terminals near unfamiliar locations when visiting friends.
o Know operating hours so she won't wait for rides that have stopped.
o Report drivers who overcharge students.
 5. Problems and Frustrations
o She was overcharged ₱20 by a tricycle driver on her first week of school
because she didn't know the correct fare.
o She got lost trying to find the right jeepney terminal in a new area.
o Some drivers don't give student discounts even when she shows her ID.
o She doesn't know which routes are faster during rush hour.
o Asking strangers for directions is sometimes awkward and unreliable.
o She tried Google Maps but it doesn't show local tricycle routes.
6. Daily Routine
o She leaves home around 6:30 AM to avoid traffic.
o Morning commute takes about 45 minutes to 1 hour.
o Classes end between 4:00 PM and 6:00 PM.
o Evening commute is more difficult because some routes stop operating
early.
o On weekends, she sometimes goes to the mall or visits friends in other
barangays.

User Persona 2 – Mang Tonyo (Tricycle Driver/Operator)

1. Background
o Mang Tonyo is 48 years old.
o He has been driving a tricycle for 20 years.
o He owns 3 tricycles (1 he drives, 2 operated by other drivers).
o He finished high school.
o He is married with four children.
o He mostly speaks Filipino/Bisaya.
2. Phone and Technology Use
o He uses a basic Android smartphone.
o He can use:
 Facebook (for news and groups)
  Messenger (for family communication)
 GCash (to receive payments)
o He is not very confident with new apps but can learn if shown how.
o He prefers apps with simple interfaces and big buttons.
3. Business Situation
o He operates on a fixed route from the barangay to the public market.
o His daily earnings are around ₱500-800 per day (gross).
o He follows the fare approved by the local transport office.
o He is a member of the local tricycle operators association (TODA).
o His tricycles are registered and have franchises.
4. Goals Mang Tonyo wants RideGuide to help him:
o Make his route visible to more passengers, especially new residents.
o Show that he charges the correct, legal fare.
o Get positive reviews from satisfied passengers.
o Attract more passengers by being listed as a verified operator.
o Respond to complaints professionally if there are misunderstandings.
o Connect with other operators for route information sharing.
5. Problems and Frustrations
o Passengers sometimes accuse him of overcharging even when he follows
the correct fare.
o New residents don't know his route exists and take longer, more
expensive alternatives.
o Some illegal (colorum) operators undercut fares and steal passengers.
o When fare rates increase, passengers don't believe him because there's
no public announcement they can check.
o He has no way to promote his service except word-of-mouth.
o The TODA doesn't have a website or online presence.
6. Daily Routine
o He starts driving at 5:00 AM.
 o Peak hours are 6:00 AM to 8:00 AM and 5:00 PM to 7:00 PM.
o He takes a break during midday when there are fewer passengers.
o He stops operating around 8:00 PM.
o On Sundays, he rests or only drives half-day.

User Persona 3 – Ms. Ana (Tourist/Visitor)

1. Background
o Ms. Ana is 32 years old.
o She works in Manila but is visiting her province for a family reunion.
o She hasn't been home in 3 years.
o She speaks Filipino and English fluently.
2. Phone and Technology Use
o She uses an iPhone but also comfortable with any smartphone.
o She regularly uses:
 Grab (in Manila)
 Google Maps
 Waze
 Various travel apps
o She has mobile data and is comfortable with technology.
3. Commuting Situation
o She needs to travel from the airport/bus terminal to her relative's house.
o She also needs to visit different relatives in various barangays.
o She is unfamiliar with current routes and fares (things changed since she
left).
o She doesn't want to bother relatives by asking for rides all the time.
4. Goals Ms. Ana wants RideGuide to help her:
o Find routes from the airport/terminal to her destination.
o Know the correct fare so she won't be taken advantage of as a visitor.
 o Locate terminals when she's in an unfamiliar area.
o Plan trips to visit multiple relatives efficiently.
o Feel confident commuting on her own.
5. Problems and Frustrations
o Grab and other ride-hailing apps don't operate in her province.
o Google Maps shows driving directions but not local tricycle/jeepney
routes.
o She was charged ₱150 for a trip that should have been ₱50 because the
driver knew she was from Manila.
o She doesn't know which terminals are near her relatives' houses.
o Asking for directions makes her feel like an outsider in her own hometown.
o Local transport seems confusing compared to Metro Manila.
6. Situation During Visit
o She's staying for 2 weeks.
o She needs to attend events in at least 5 different barangays.
o She wants to explore local spots (beach, market, restaurants).
o She might rent a motorcycle but prefers public transport for short trips.
2.4 Key Stakeholders
Primary Stakeholders
1. Commuters (Main Users)
o Examples: students, workers, residents, senior citizens, and tourists.
o They use the platform to find routes and fares.
o They are the most important because the platform will only succeed if it
serves their needs.
o They should be involved through user surveys, testing, and feedback after
launch.
2. Transport Operators and Drivers
o Examples: tricycle drivers, jeepney operators, TODA/JODA members.
o They register their routes and respond to feedback.
o They benefit from increased visibility and credibility.
o The platform must be easy for them to use for registration and updates.
3. Passengers Who Use the Feedback System
o They actively contribute reviews and ratings.
o Their feedback improves the quality of information.
o The platform must protect their identity if they report violations.
Secondary Stakeholders
1. Local Government Unit (LGU) - Transport Office
o They set official fare rates and approve franchises.
o They can use the platform to disseminate fare updates.
o They may endorse the platform for public use.
o Partnership with them adds credibility and accuracy.
2. Transport Associations (TODA/JODA)
o Tricycle Operators and Drivers Association.
o Jeepney Operators and Drivers Association.
o They can encourage members to register on the platform.
 o They benefit from organized route information.
3. Local Community
o Barangay officials who may promote the platform.
o Local businesses near terminals.
o Schools and companies whose students/employees commute daily.
Internal Stakeholders (People Who Build and Manage the Platform)
1. Development Team
o PHP/CI4 developers, frontend developers, and testers.
o They need clear requirements and regular feedback to build the platform
well.
2. Project Adviser/Manager
o This person decides feature priorities and manages the timeline.
o They guide the project to meet user needs within constraints.
3. System Administrator
o Manages the deployed platform.
o Handles user support and data backup.
o Moderates content and manages security.