CSE 262 Class Projects (Spring 2009)

One of the goals of CSE 262 is to teach you how to conduct research. A research project is a formal requirement of the course and counts for 60% of your grade. A project may be done individually, but some projects are better suited to a team of 2. You should allow 6 weeks to complete the project. Your project grade will be based on your successful completion of the following 3 parts:

1. Project proposal: due Friday, April 17, 2009 (electronic, 1/10 of the project grade)
2. Progress report: Wednesday, May 6, 2009, in-class (electronic, 2/10 of the project grade, an in-class presentation)
3. In class presentation: Last week of classes (TBA) Bring hard copies of your slides to class. (2/10 of your project grade)
4. Final Report: due Friday, June 5, 2009, 5PM, in EBU3B 3244 (Hard copy and electronic)

A list of projects appears below. If you have your own project in mind, discuss it with me first.

Your project proposal should identify the investigator(s) and the title of the project. You should present a preliminary list of milestones—with completion dates—and possible options depending on your progress. Your milestones are not binding, so be realistic. You may need to fine-tune your goals as the project is underway. This is fine so long as you document your decisions. If you are working in a team, describe the division of labor in your proposal. If you are proposing your own project, include a description of the project that is roughly one double spaced page long. I will give you feedback once I've read over you proposal.

Your project proposal should address the following issues.

1. What are the goals of your project? Are they realistic?
2. What are your hypotheses?
3. What is your experimental method?
4. What result(s) do you want to demonstrate?
5. What are the significance of the results?
6. What code will you implement? Briefly describe any software packages or previously written software that you will be relying on.

The progress report will help keep you on a steady pace and enable you to make mid-course corrections. The report should

1. discuss your progress to date. If you are working in a team, include a self-evaluation discussing the division of labor and other aspects of how you worked together as a team team (A copy of the form is available in html)
2. revise any milestones and completion dates that you established previously, including an explanation.

In evaluating your proposal and progress report I will check to see if your goals are realistic. A realistic project that is completed successfully will likely receive a higher grade than one that is too ambitious and doesn't get finished. Results alone are not adequate. You need to interpret them. If you have any questions about this, be sure and see me. If you do have an ambitious design, we can work together to set realistic goals.

Your report should be a polished piece of work. To get an idea of what I expect, look at project reports from courses I’ve previously offered.

Submit hard copy as well as an electronic version, e.g., html with ASCII and other attachments. Here is a discussion about what is expected in the report, along with instructions for submitting an electronic copy.

Projects

Maintained by

baden

@

ucsd.

edu

[Fri Mar 20 15:01:45 PDT 2009]