final project checkpoint 4

This checkpoint is due April 13, 2020, 23:59 CDT.

This checkpoint is mostly a “continue doing what you’re doing, and update me on your progress” checkpoint. Because of the semester reorganization, our new deadlines for the rest of the semester are:

  1. Monday March 30th: Deployment checkpoint (aka checkpoint 3)
  2. Monday April 13th: Checkpoint 4 deliverables due. If you ran into any snags (feature X was way harder than you expected at the beginning), you can make your case for changing final deliverables.
  3. Monday April 27th: Final deliverable due.
  4. Weeks 10-15: SPOOKY SECURITY ASSIGNMENT. There will be no explicit security assignment; as stated earlier, the entire project is a security assignment if you go for the extra credit by finding and fixing security issues with each others’ projects.

Deliverable 1: progress report

Provide a short writeup of your overall plan of attack for this project. Basically:

  • What were the different functionalities you aimed to finish for each deadline (checkpoints 2, 3, 4)?
    • A quick English description of “what is currently working in the app”
    • Who accomplished what
    • What didn’t get done in time
  • What is the plan of attack for finishing Checkpoint 5?
    • What functionality remains to be finished
    • Who will be in charge of finishing what
  • What changes, if any, do you want to make from your original plan?
    • What is your reason for making those changes (i.e. what you did try, what you learned, what you realized is way harder than it needed to be, and how you realized that)?

This writeup will be worth 15% of your checkpoint grade, and will be graded on its completeness.

Deliverable 2: Final test list

Write out specific deliverables for checkpoint 5. They should both be described in your README.md file, as well as via English descriptions of tests that your app will be passing. In your readme, please list which tests in which files within your repository are the checkpoint 5 tests.

These will be worth 15% of your checkpoint grade.

Deliverable 3: pass your tests

The meat of this assignment is getting your functionality up and running as per your tests for Checkpoint 4 that you described in Checkpoint 3.

This is worth 60% of your checkpoint grade.

Deliverable 4: keep the deployability working

The application and tests should be runnable by an instructor with little to no additional configuration. This is basically a rehash of the checkpoint 3 “deployability” check.

This is worth 10% of your checkpoint grade.

Submitting your code

Your final commit to master before the deadline will be graded. 10 bonus points will be given if you create a “checkpoint 4” tag pointed at that commit to make our lives easier.