1. CS 4360 Software Engineering

2. Overview
A free transportation service that is run primarily by volunteers.
The services will be handled directly through the Mobile and Web Applications.
There will be administrators to run and maintain the service.
Volunteer Drivers to enforce and supply the service.
Customers who request the service.

3. Admin Functional Requirements
Admins shall be able to:
View past and present requests.
Accept clients into database.
Make new requests for clients via telephone.
View driver availability and zones as well as edit driver information.
View and edit client information.
View thumbs up/down ratings on client and driver.

4. Driver Functional Requirements
Drivers shall be able to:
Set their zone and availability.
See zone/non-zone ride requests and accept/deny them.
Review clients via thumbs up/down system.
Change their information. (Personal, car specs, hours, etc.)
Track their total mileage.
Communicate with the clients via messaging system.
Go Online/Offline. (not get notifications while offline)

5. Client Functional Requirements
Clients shall be able to:
Request new rides via mobile app, website, or telephone.
Give information such as name, address, destination, estimated length of trip, accessibility, driver filters (such as gender and vehicle), and date/time of pickup.
Rate their driver based on a thumbs up/down system.
Communicate with the driver via messaging system.

6. Nonfunctional Requirements
There needs to be a high level of security. The app itself must be secure due to client/driver information being stored. Such information includes: driver information (such as background check, driver’s license, and phone number) and client disclaimer.
It needs to be very user friendly and easy to navigate.
Elders make up the most of Longville’s population and their experience will vary heavily.
Driver’s user interface must have a simple layout since they will be on the road.
Performance is a big issue. There can be problems such as loss of signal, communication issues, and drivers could get lost.
Clients are required to sign a disclaimer before each ride and drivers must be able to provide necessary information before they can drive clients.
Clients shall be able to request new rides at any time.

7. Driver Distance Preferences
Set a strict request range.
Drivers will have the option to allow further requests.

8. Admin - Basic Flow Admin Logs in. Incorrect - Displays an error.
Taken to Admin Dashboard.
Dashboard.
Create Ride Requests.
View/Edit Scheduled Rides, Up/Down Ratings.
Add/Edit/Delete Drivers and Clients.

9. Driver - Basic Flow Driver Logs in. Incorrect - Displays an error.
Driver Dashboard - Functionality
View/Accept/Decline Ride Requests.
Track Mileage.
Set Zones and Availability.
View Clients rating.
Accept a request.
Complete Pick-up/Drop-off.
Rate the Client.

10. Client - Basic Flow Client Logs in. Incorrect - Displays an error.
Client Dashboard.
Admin Accept .
Clients Functionality.
Create Ride Requests.
Rate Drivers.
Message Driver.

11. Database This is the center of our software implementation.
MySQL style database is being used to store the information.
Will connect all of the Web and Mobile apps together.
Will keep Admin/Driver/Client Information.
Database

12. Database Tables Showing the clients and drivers data model.
All of the data in the database will need to be managed and manipulated.

13. Server Requirements

14. Server Behavior

15. Up Next!
Web-Application Prototype Presentation.
Mobile-Application Prototype Presentation.