https://github.com/quenty/raik383team3
Team 3's Project Repository for RAIK383H Software Engineering
https://github.com/quenty/raik383team3
Last synced: about 1 year ago
JSON representation
Team 3's Project Repository for RAIK383H Software Engineering
- Host: GitHub
- URL: https://github.com/quenty/raik383team3
- Owner: Quenty
- Created: 2017-01-29T22:42:28.000Z (over 9 years ago)
- Default Branch: integration
- Last Pushed: 2017-04-27T15:51:20.000Z (about 9 years ago)
- Last Synced: 2025-02-16T17:56:37.671Z (over 1 year ago)
- Language: C#
- Homepage: https://practicalwerewolf.azurewebsites.net/
- Size: 21.2 MB
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README


# Team 3
* Abbie Jarratt
* James Onnen
* Jessee Zhang
* Matt Dottavio
* TA: Jacob Sanchez
# Client problem statement
A transportation company is seeking to improve its operations. Their current practices are outdated as they are not integrated, and rely on manual operation, which is error prone and costly. The company uses contractors that are truck drivers and can haul loads as needed across the nation. When a shipment order comes in, currently by email, a human dispatcher reviews it, and cross-references it with an Excel spreadsheet where they maintain the list of available contractors and their profiles, together with their status: whether idle or on assignment, at their home base, or at a destination where they had finished an assignment. The dispatcher tries to find the best matching contractor that can haul the given shipment, and assign them the request and send them the work order. The company wants you to automate this process for them, integrated into a web application. Their ultimate objective is ensuring optimal assignments of shipments to contractors to keep costs low.
## Grading
* Requirements - 10 points
* Design - 10 points
* Implementation - 30 points
* Final Demo - 10 points
## Timeline
* Requirements will be turned in by the end of January,
* Design by last week of February, and
* the rest until the final demo is left for Implementation.