TP0 (Progress Update and Tech Demo)
Due Mon 18-Nov, 5pm

This is part of the Term Project Assignment. See that document for more details.
  1. TP0 Progress Update
  2. TP0 Tech Demo
  3. TP0 Submission
  1. TP0 Progress Update
    2.  Meet with your TP Mentor for 10 minutes to check on your progress, discuss project ideation and design decisions. This meeting will be around the tp0 deadline. It may occur just before that deadline at the discretion of your TP Mentor.

    In your TP0 meeting, you will finalize your TP idea with your TP Mentor. If you do not have a TP idea, you would be behind on your TP progress, and your mentor will help you decide on one at this point. The point is: as of TP0, you are committed to your project's basic vision and goals.

  2. TP0 Tech Demo
    3.  If you wish to use any tech outside of Python and what we have covered in the notes, then you must successfully complete a tech demo during your TP0 meeting. This includes if you wish to use any other libraries, modules, APIs, hardware, and so on. Tech demos are your responsibility -- you have to demonstrate sufficient mastery of the tech to your TP Mentor so that they believe you have a strong chance of using it effectively in your TP.

    While the specifics of your Tech Demo vary for each student, depending on how you intend to use your tech, in general you must show that you can deftly use the tech as required. For example, for opencv, you might demo that you can track a bright green object that the user is moving around. Then, your mentor may ask you to change the code to track a bright red object, and you would have to be able to do that, fairly easily, while your mentor watched to confirm.

    Your tech demo cannot just be example code you found online. Also, you must show your tech working inside of the cmu_graphics framework, obeying MVC.

    You have only passed a tech demo if you receive written confirmation from the lead TAs or faculty, via email (not verbally). If you do not pass the tech demo, then you will need to restructure your project to work without the tech, at least until you reach tp2 with adequate progress.

    We will not extend the tech demo deadline. You have one chance, so start early, and be prepared. But, remember that you do not have to use tech, nor do we recommend it, nor does it increase your chances of a good grade. It is easier to create a successful term project without additional tech.

  3. TP0 Submission
    4.  By the tp0 deadline, submit a single zip file to Autolab with the following:

    1. 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. Project Title and Description
        The name of the term project and a description of what it will be. Your description must be a paragraph or two, including as many specific details as you can in that space. That said, please keep this brief and to the point. Please include a couple of pictures if that helps.
      2. Similar Projects
        Identify at between 2 and 5 similar apps or projects, either in the TP Gallery or online or in the Apple or Google play stores. You need to study these apps and list a few features from them that you think may help inspire the design of some parts of your app.
      3. Version Control / Backup Plan
        Include a short description and image demonstrating that you are using version control or in some reasonable way backing up your code regularly (daily, at least). Note that your backups must not be on your computer (in case something happens to it). Ideally, store your backups in the cloud (Google Drive, a private git repository, etc).
      4. Tech List
        Include a list of all external modules/hardware/tech you are planning to use in your project. Note that any such modules must be approved by a Tech Demo. If you are not planning to use any additional modules, that's fine, just say so!

      Note:
      If your project plan changes considerably based on your Tech Demo and your TP0 Progress Update, you will be given a 2-day extension (explicitly, by email from your TP Mentor) to resubmit your updated TP0 submission.

    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. At this point, this may include short demos or exploratory code that may not be part of your tp3 deliverable.