Team CargoFlow Inc.

(This webpage was last edited on 12-13-2024)

  1. This file CargoFlow.pdf contains evidence of our efforts to plan our elicitation of requirements from Mr. Keogh, and any notes taken during the elicitation.
  2. This file CargoFlowProjectPitchORIGINAL.pdf contains our original pitch to Mr. Keogh, which was delivered on October 13th, 2024, at 9:00 AM.
  3. This file CargoFlowProjectPitchCORRECTED.pdf contains a new version of the pitch, with all the corrections, amendments and deletions suggested by Mr. Keogh (and/or Dr. Keogh)
  4. This file CargoFlowDesign.pdf shows evidence of our efforts to design our software.
  5. This file CargoFlowTesting.pdf which shows evidence of our efforts to test our software.
  6. This URL github.com/pondohoo/cs-179-cargoflow points to a GitHub repository of our code.
  7. This YouTube video, that shows our software solving one balance, and one transfer test case (our choices, of the test cases Mr. Keogh gave us).
  8. This text file, is the KeoghsPort2024.txt log that was created by our software, during the making of the YouTube video in the previous bullet point.
  9. We would like to point out the following limitations:
    • The website's storage capacity is limited, and running a complex A* search for a certain amount of time tends to exceed it, causing the function to pause and stop running. To address this, we reduced the time limit from 15 minutes to 13 minutes. While this change prevents the website from pausing, it also results in a potential less optimal solution. This limitation also stops the use of the buffer in the case of time limit exceeded because A* is in charge of using the buffer to find the optimal steps.
    • For load/unloading buffer use has not been implemented.
  10. (EK says, this is optional) Here is some additional items you may find useful in grading the project.
    • Upon reviewing the submission video, we realized that the log file name was incorrect. This was corrected, but not reflected in the video.
  11. (EK says, this is optional) We would like to acknowledge the following resources that were helpful in completing this project. As not all members were experts on Javascript and Next.js, we had to research and learn the language and framework. The sources we consulted were: the JavaScript documentation, React documentation, Google, Stack Overflow, and GeeksforGeeks.