TP1 (Progress Update)
Due Mon 25-Nov, 5pm

This is part of the Term Project Assignment. See that document for more details.
  1. TP1 Progress Update
  2. TP1 Submission
  1. TP1 Progress Update
    2.  Meet with your TP Mentor for 10 minutes to check on your progress, discuss your plan to reach tp2 with adequate progress. This meeting will be around the tp1 deadline. It may occur just before that deadline at the discretion of your TP Mentor.

  2. TP1 Submission
    3.  By the tp1 deadline, submit a single zip file to Autolab with the following:

    1. Updated Project Proposal (proposal.docx, proposal.pdf, or proposal.md)
      This file should be named proposal.docx, proposal.pdf, or proposal.md (that is, Word, PDF, or Markdown, and no other formats), and it should include these sections:
      1. Updated TP0 Deliverables
        These are the same deliverables as in tp0, only updated (if necessary) to reflect the current state of your project:
        • Project Title and Description
        • Similar Projects
        • Version Control / Backup Plan
        • Tech List

      2. Storyboard
        In addition to the updated tp0 items, your tp1 proposal must also include a storyboard that demonstrates how a user would interact with your finished project. A storyboard is just a series of sketches showing (roughly) what your project will look like. Your storyboard should have at least six panels, and at least three of those should demonstrate features within the project. You may scan or take a picture of your storyboard and include it in your project proposal file. Note you may not use screenshots or images from existing applications or projects. You should create these from scratch. However, you can take inspiration from existing applications when designing your own.

    2. Project Source Code
      In the top level of your submission zip file, include a folder named "src" that contains all the Python source code you have written so far. By tp1, this does not need to be a working demo, but it should at least be a real start towards solving the core problems of your project. For most students, 400-600 lines of decent code would indicate a good start, but we do not grade based on the number of lines you submit. In fact, some of the lowest scores typically are assigned to projects with a very large number of lines of poorly-designed code.