Q: Creating a User-Case requirements model & domain-model.

Here are the specs:

There is a driver and a rider (actors)

Rider can update data, request rides, rate drivers (scale 1-5).

Drivers can update data, accept or decline request, complete request, and rate riders (scale 1-5).

Driver data & rider data includes name, average rating, an account with balance.

Driver data also contains specifications of the car(make, model, year, color, license #).

Rider data also contains a picture.

Request holds pick-up place, drop-off place, passenger info, completed flag, and driver who accepted request (if any).

When a ride is requested, Taxi server sends to a driver who can either accept or refuse. If refused, it is sent to another driver until no driver exists, sending error message. Otherwise, ETA and driver data provided to rider.

Once accepting request, driver picks up passenger. Upon arrival at destination, a request-complete notification sent to Taxi server.

Taxi server then takes payment from rider and adds it to driver's balance. Driver rates rider and rider rates driver. Then both ratings are updated.