Home
We'll refer to the overall system being created as the "Ride Request MVP" or RRM. The data model for the RRM is our primary guide, as it reflects the entity relationships and the process of entering a ride request, allocating resources for the ride, and monitoring status while fulfilling the ride request. The communities of stakeholders and the intersecting user groups they belong to are defined in the communities diagram.
In order to have a common language framework about rides in general, we created the "diagram of a ride" below. It primarily assumes the perspective of the transportation provider and driver.
As you can see, the ride start (1) is at the transportation provider motor pool. The "pickup location" (2) is the origin of the rider. The "dropoff location" (3) is the destination of the rider. If for some reason this were a one-way trip, the ride would be completed and the driver would return to base (solid red line); however, the overwhelming majority of rides will be roundtrip, so at the return time "roundtrip return" begins (3a) at the dropoff location, and "roundtrip complete" happens (3b) at the pickup location. The ride then completes when the driver returns(4) to motor pool.
The diagram below shows the overall application flow at a high level; note that we have a case manager persona diagram as well as personas for the elderly rider and remote caregiver.
