For drivers
Uncertainty about where capacity is available.
Smart parking, designed for smarter campuses.
PARADA is a mobile and web-based smart parking management system designed to help drivers and parking administrators understand, manage, and monitor parking availability through a unified platform.
Instead of attempting to individually monitor every parking space, PARADA uses zone-based occupancy as its primary operational metric — the zone, not the individual slot, is the authoritative unit of availability.
Uncertainty about where capacity is available.
Difficulty monitoring occupancy and parking activity manually.
Disconnected parking operations and limited visibility into utilization.
PARADA brings these activities together through one connected system.
To develop a smart parking management system that combines computer vision, license-plate recognition, zone-based occupancy monitoring, parking operations, mobile navigation, and web-based administration into a unified platform.
The vehicle reaches a zone gate or entry point.
The gate camera observes the vehicle and captures the license plate.
Image processing reads the plate text.
The API determines the vehicle, user, zone, reservation, and admission policy.
The plate resolves to a registered vehicle and user, or a guest candidate under policy.
Zone occupancy and the parking session update in the same transaction.
Both clients read the same backend-authoritative state — drivers on mobile, administrators on the web dashboard.
The exit camera/OCR event enters the API.
The backend closes the session and calculates the fee where configured.
PARADA treats the parking zone as the authoritative unit of availability. Physical parking spaces can still exist as inventory or layout information, but operational occupancy is represented at the zone level — this keeps the system accurate with standard gate cameras instead of a sensor on every slot.
A modular breakdown of platform capabilities — from driver experience to intelligent infrastructure and operational control.
Guest admission is controlled by establishment-defined policies rather than treating every unidentified vehicle as automatically authorized.
Live availability across every zone. See open spots before you even leave.
Compare rates, limits, and restrictions. Filter by EV, accessible, or covered.
Lock your bay in 2 taps. Guaranteed spot, instant confirmation.
Turn-by-turn to your exact space. No more circling the block.
Live timer, one-tap extension, and automatic checkout. All from your pocket.
Administrators work in the web application; drivers use the mobile app. The dashboard is the operational surface for zones, cameras, sessions and anomalies.
This allows PARADA to adapt to different establishment layouts without changing the application's source code for every parking facility.
Section 04 showed what happens to a vehicle. This is how the system makes it happen: a camera event travels through vision/OCR into the API, which resolves identity, occupancy and sessions, persists them, and propagates the new state to both clients.
PARADA is developed as a capstone project for the Bachelor of Science in Information Technology program.
Identifies vehicles from camera observations.
Makes availability understandable at the zone level.
Drivers and administrators use connected interfaces.
Parking facilities can configure zones, capacities, cameras, and policies.
Critical parking state is managed centrally instead of being independently calculated by each client.
Walk through finding, reserving, and navigating to a zone.
See how operators monitor zones, sessions, and cameras.
Watch a vehicle move through capture, OCR, resolution, and exit.
PARADA demonstrates the integration of mobile development, web administration, backend services, database management, computer vision, OCR, GPS navigation, and configurable parking operations within a single system architecture.
The system is developed as a capstone prototype and evaluated based on functionality, integration, correctness, and system behavior. Formal accuracy evaluation and production deployment are treated separately from the functional implementation.