§01Purpose / Problem
Coordinating transportation requests between riders and drivers takes more than a simple interface. It requires modelling users, rides, drivers, and requests, and how they relate to and depend on each other in a real-world process.
§02What I Built
CoolRides translates the ride-sharing process into a software system, covering users, drivers, ride requests, and the relationships between them, so the underlying business rules and user flows reflect how the process actually works, not just how it looks on screen.
§03Outcome / Impact
The project provided practical experience designing software around real-world users, processes, business rules, and interactions rather than just building an interface.
§04What I Learned
CoolRides reinforced that software development isn't only about the interface. The underlying processes, relationships, business rules, and user flows have to make sense for the system to actually solve the problem. It also gave me practical experience applying design patterns to structure that system cleanly.