Project 2 Check-in 2 (Proposal)

(Please see the corresponding project description for full notes about check-ins, including discussion with your TA and how to submit). Note that (despite the Canvas message here) submitting your check-ins on time is one factor we'll take into account when determining your grade.

Check-in 2 contents 

• Brief description of your planned program analysis (and visualisation, if applicable) ideas.
• Notes of any important changes/feedback from TA discussion.
• Any planned follow-up tasks or features still to design. 
• Planned division of main responsibilities between team members.
• Summary of progress so far.
• Roadmap for what should be done when, including specific goals for completion by future check-in (propose at least three such goals per future check-in, along with who will work on them; you can revise these later as needed).

Proposal contents

See attached PDF (Project_2_Proposal_Template.pdf) Download Project_2_Proposal_Template.pdf) or docx (Project_2_Proposal_Template.docx Download Project_2_Proposal_Template.docx) template for more details. The proposal must give the following information:

• A. Brief (1-3 sentence) Description of Proposed Program Analysis Tool:
• B. Intended User-Group:
• C. What language will you target? What features will you aim to support (or not support)?
• D.Which questions about program behaviour will users be able to answer with your tool?
• E. Which of the three criteria does your project satisfy? Justify why the criterion is satisfied.

• (only if meeting criteria 1+2 for E.) F. Which of the four impossible properties does your project *not* satisfy?

Submit your proposal as a pdf to GitHub by the check-in deadline. 

Check-in 2 requirement (individually)

Each team member must individually fill out a short survey about how things are going for them in their team; details in the accompanying assignment description.