Project Detail

Description

Hello,

I am in need of a robust air-tight application that will work in conjunction with a front-end website. This application is for an upstart vanpool company that has the following specifications.

1. There are a number of vans that travel throughout town going to various worksites.
2. Passengers pay for the service by giving a check or cash to a van coordinator.
3. There is one van coordinator per van.
4. People looking to join a vanpool can view a vanpool listing on the website in which the information is entered manually.
5. The vanpool's monthly fee charged to the passenger varies for each vanpool and is calculated by the administrator, and it may differ for each month as it is determined by many factors such as gas prices, but these factors will not be incorporated into this
application for now, perhaps in a phase 2 upgrade.


The company wants to automate many of these functions online. These are the following requirements for this application.

1. There are 3 roles identified for this application: administrators, coordinators, and passengers.

2. Passengers can create an account on this system. During this application process they can designate which van they belong to, as

noted by a Van ID, perhaps chosen from a dropdown box. There will also be other information for them to enter into their profile,

i.e., address, phone numbers, etc.

3. The administrator can enter what the monthly rate is for each van. Coordinator is for their respective van and then make their

own calculations accordingly as to what each passenger will have to pay for that month. Therefor the coordinator can enter in the

fee and then the passenger can login to their account and pay this fee online.

4.Once the transaction is confirmed through the merchant account, a confirmation email is sent to the passenger, his/her respective

coordinator, and the administrator(s) of this payment. The payment is also noted in the database column "method of payment" as

credit card/debit card. With that being said, coordinators can still receive payment from passengers in the form of cash or check,

and within this application they will be able to specify this method of payment as well.

5. A monthly email notification is sent out to passengers notifying them of what their payment amount is for the upcoming month. I

should mention that coordinators are considered passengers as well so they would be reciving this notification as well.


There are some various forms that are needed to add information to the application/database:

I am uncertain as to how the process is for a user to create an account. I've received emails before telling me to create an

account at the website and there have been times where I would receive a user ID and I use that to update a profile that was

already created for me by an administrator. I am open to suggestion for this method of creating an account.

With that being said there will be a form where the passenger can create a profile. The heirarchy of the roles under consideration,

administrators can create/edit/delete other administrators and coordinators and passengers. Coordinators can only create/edit

passengers, and passengers and create/edit themselves. Coordinators can be changed to passengers as he/she may not want to perform

in this position, with that being said, the coordinator will lose those rights associated with that position.

Each van for the company will have a profile in which the administrator can enter in the information for that as well as the

coordinator associated with this van. So a form will be needed to add a van into the system.

A form will be needed for the administrators to enter in the monthly amount required for each van.

A form will be needed for the coordinators to enter in the monthly amount required for each passenger. The coordinator can only

enter the information for the van that he/she is associated with.

VIEWS
All of the roles have a need to see views/grids of information.

passengers
Passengers can see all the historical data of their payments made to the company. They can also see their profile information.

coordinators
Coordinators can see their own payment history as well as the payment history of all the passengers belonging to his/her van. They

can also look at their profiles. They will be able to look at the views on a year by year basis. There will be a button or link

which will allow them to edit a particular field if need be, only for the current year. For past years will not be editable. They

can also look at the van profile for which they belong to but cannot edit this information, except to designate whether there is a

vacancy or not..

administrators
Administrators can see everything described above and more. They will be able to see a master listing of all passenger profiles

belonging to all vans and a master list of all van profiles. They can also see a master list of payment history. There will be a

link/button where they can edit any field,particular field if need be, only for the current year. For past years will not be

editable. Only administrators can edit van profiles.

everyone
This is the only part of the application to be seen by the public, that being prospective passengers looking to join a vanpool.

This will be a van vacancy view. When the administrator or coordinator tells the system that a van has a vacancy, the van's profile

(only contact info, destination, arrival times, etc) will populate this view on the webpage.


There needs to be a way to save all historical data to be accessed by administrators. For passengers who have left the van and have

been deleted from the application, Administrators who have been deleted from the application, Coordinators who have been deleted

from the application; this information still needs to be stored in the database and accessed on the fly. Additionally all payment

information from prior years

REPORTS
There is also a need to generate reports from this application, perhaps in pdf and xls formats.

I have enclosed some sketches of how the application is envisioned to work and look. We would like to see a portfolio of similar work. Thanks for taking a look.







Additional files submitted:
admin-coordinator panel.PDF
passenger add-edit form.PDF
passenger dues listing by year.PDF
passenger master listing for admin.PDF
single van dues listing.PDF
single van monthly dues form.PDF
van dues monthly entry form.PDF
vanpool availability listing.PDF
vans master listing.PDF