Project Proposals (due in class on Wednesday, November
27):
Each student should submit a one-page written project proposal.
The proposals should include enough detail to convince a reader that you've
found a good problem, you understand how hard it is, you've mapped out
a plan for how to attack it, and you have an idea about which experiments
you might run to test the success of your implementation. Following is a brief
outline you might follow ...
Goal
What problem am I going to solve?
Who will benefit?
Challenge
Why is the problem hard?
What approaches have others tried?
Why don't those previous approaches work?
Approach
What approach am I going to try?
Why do I think it will work well?
Methodology
What steps (task list) are required?
Which of these steps is particularly hard?
What to do if the hard steps don't work out?
Metrics
How will I know when I am done?
How will I know whether I have succeeded?
Summary
What will I learn by doing this project?
Will this lead to
Project Proposal Presentations (during class
on Wednesday, December 4):
Each students will give a 10 minute talk to present his/her course
project proposal to the class (with slides, videos,
and/or other props). You should be sure to convince us that: 1) you
are addressing an important problem, 2) you understand various approaches
to the problem, 3) you have found an interesting approach to attack the
problem, 4) you have a specific, detailed plan, and 5) you will know when
you are done. We will run the proposals like a venture capital meeting, where
each student is given some amount of "money" to invest in projects,
and the project with the highest investment will get a prize.
Demo Day (at 2PM on Wednesday, January 15th in CS402):
Each student will give a short presentation of his/her
class project. Your goal should be to demonstrate and describe for
the class in 10-15 minutes what you have done and why it is interesting.
In addition to running a live demo on one of the computers, you should
describe the guts of your project (e.g., using a few slides and/or a movie).
The presentation should clearly present the goals, challenges,
approach, and results of your project.
Final Written Reports (due at 5PM on Friday, January 24,
2003):
Each team of students should submit a six- to ten-page written final report.
The written report should contain descriptions of the goals and execution
of your project. You should include a review of related work.
You should write detailed descriptions of the approach you've chosen, the
implementation hurdles you've encountered, the features you've implemented,
and any results you've generated. Please do not be vague in your
written descriptions. Following is a brief outline you might follow
...
Introduction
Goal
What did we try to do?
Who would benefit?
Previous Work
What related work have other people done?
When do previous approaches fail/succeed?
Approach
What approach did we try?
Under what circumstances do we think it should work well?
Why do we think it should work well under those circumstances?
Methodology
What pieces had to be implemented to execute my approach?
For each piece ...
Were there several possible implementations?
If there were several possibilities, what were the advantages/disadvantages
of each?
Which implementation(s) did we do? Why?
What did we implement? <== Include detailed descriptions
What didn't we implement? Why not?
Results
How did we measure success?
What experiments did we execute?
Provide quantitative results.
What do my results indicate?
Discussion
Overall, is the approach we took promising?
What different approach or variant of this approach is better?
