This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
trucks-for-you-revised [2018/07/19 06:44] hari |
trucks-for-you-revised [2018/07/31 10:58] (current) hari [See the list of trucks that fit a suggestion] |
||
---|---|---|---|
Line 92: | Line 92: | ||
===== Driver use cases ===== | ===== Driver use cases ===== | ||
+ | |||
+ | ==== Login ==== | ||
+ | - During induction, a driver's phone number and name are already created by the admin. | ||
+ | - The driver enters phone number. | ||
+ | - The system checks if a driver with that phone number has been inducted. | ||
+ | - If not so, then the driver is not allowed to log in. | ||
+ | - An OTP is sent to the driver's phone number, while a provisional token is generated for the driver and sent back in the response. | ||
+ | - The driver's app enters the OTP into the OTP field. | ||
+ | - If the OTP generated by the system does not match the one entered by the driver, then the authentication is unsuccessful. | ||
+ | - The following things are fetched: | ||
+ | - The driver's profile: name, phone number, photo, driving license number. | ||
+ | - The truck's profile: registration number, type, capacity, photo | ||
+ | - A list of trip suggestions that are applicable for the that driver. | ||
==== Get a list of applicable trips ==== | ==== Get a list of applicable trips ==== | ||
- | - Driver gets a list of requested trips for which he/she is eligible. Each trip has the following details. | + | - Driver gets a list of requested trip suggestions for which he/she is eligible. Each trip has the following details. |
- Start city | - Start city | ||
- End city | - End city | ||
Line 133: | Line 146: | ||
===== Admin use cases ===== | ===== Admin use cases ===== | ||
+ | |||
+ | ==== Login ==== | ||
+ | |||
+ | - Admin can log in using either phone number of email. | ||
+ | - A verification is sent based on the entry of identity. In both cases, an access token is generated. | ||
+ | - An OTP is sent if the identity is phone number. | ||
+ | - An email with verification link is sent if the identity is email. | ||
+ | - The OTP and verification token in the request are checked against the ones generated by the system. | ||
+ | - For a mismatch, authentication is denied. | ||
+ | - The admin is taken to the home page. | ||
==== Add a truck ==== | ==== Add a truck ==== | ||
Line 151: | Line 174: | ||
- The admin can add a new truck type by its name. | - The admin can add a new truck type by its name. | ||
+ | ==== Add a driver ==== | ||
+ | |||
+ | The admin adds new drivers to the system when they are hired. The following details are added. | ||
+ | - Name | ||
+ | - License number | ||
+ | - License expiry date | ||
+ | - Photo | ||
+ | - License photo | ||
==== Hide truck ==== | ==== Hide truck ==== | ||
The admin can hide a particular truck if it is currently not available for a trip online. | The admin can hide a particular truck if it is currently not available for a trip online. | ||
Line 159: | Line 190: | ||
==== Hide city ==== | ==== Hide city ==== | ||
The admin can hide a city if it is currently not serviced | The admin can hide a city if it is currently not serviced | ||
+ | |||
+ | |||
+ | ==== Hide driver ==== | ||
+ | The admin can hide a driver if that driver is not going to take a trip for a long time. | ||
==== Create and assign trip ==== | ==== Create and assign trip ==== | ||
Line 164: | Line 199: | ||
If the admin comes to know about a booking that was taken over phone, they'll need to add a new trip manually and assign it to a truck. The fields are the same as the corresponding ones in hirer truck booking. | If the admin comes to know about a booking that was taken over phone, they'll need to add a new trip manually and assign it to a truck. The fields are the same as the corresponding ones in hirer truck booking. | ||
+ | ==== View a list of truck suggestions for a trip request ==== | ||
+ | Similar to hirer | ||
+ | ==== Manually select a suggestion for a trip request ==== | ||
+ | Similar to hirer | ||
+ | |||
+ | ==== See the list of trucks that fit a suggestion ==== | ||
+ | The admin can see the list of trucks that fit the conditions of a suggestion. Here are the fields the admin can see at a glance | ||
+ | - Truck registration number | ||
+ | - Driver name | ||
+ | - Driver phone number | ||
+ | - Date leaving loading city | ||
+ | - Date reaching delivery city | ||
+ | ==== Manually create a hirer ==== | ||
+ | The admin enters the following fields to create a hirer | ||
+ | - Name | ||
+ | - Phone number | ||
+ | |||
+ | ==== Assign a truck to a trip ==== | ||
+ | - The admin assigns a truck to a trip | ||
+ | - The hirer receives an SMS for the assignment of the trip. | ||
+ | |||
+ | ==== Confirm a trip ==== | ||
+ | - If a hirer agrees to the truck specifications assigned to him/her, then the admin confirms the trip. | ||
+ | - Both the driver and the hirer get a confirmation with the following data: | ||
+ | - Start city | ||
+ | - End city | ||
+ | - Trip start date | ||