Proposal Description
The project proposal should lay out an initial blueprint for your final
project. The proposal can be as few as 2 pages or as many as you like. It
will not be graded separately; it is an intermediate step, meant to
encourage you to think critically about your project, and to help us give
you the right advice.
Send Eddie and Bryan the proposal by email by midnight Tuesday 11/15.
Sample outline
Not all sections are necessary! But think about these questions to guide
your work.
- Abstract
- A single paragraph describing the goal of your project. What research question will your project address? What is the best outcome you can imagine?
- Introduction
- Why is the project exciting for you?
- Design alternatives
- What do you plan to build?
- What alternative designs have you considered?
- What related work have you found? Do you need any pointers?
- Implementation challenges
- What special hardware or software access do you need, if any?
- What boring/tedious stuff will you need to do as a prerequisite?
- What are you worried about?
- Evaluation sketch
- What will be your performance hypothesis?
- What graphs will be in your eventual evaluation section? Describe them: what will be on the X and Y axes?
- If you don’t complete the whole project, what simpler questions could you evaluate?
- Schedule
- You have until 12/10 to do your research and write up the results. What will you do each week?
Final report
The final project should include a significant implementation component;
you will turn in code and a paper. The paper must contain at least some
evaluation component (graphs and/or tables), as well as a good description
of your design and relationship to prior work.