CS577 PROJECT GUIDELINES


DATES

January 28	Initial proposals due
Feb 4		Final proposal approval required
Feb 25		Progress report due
Mar 10/17	Project oral presentations (optional)	
Mar 19		Project writeups due


INITIAL PROPOSAL CONTENTS

Your initial proposal should be one page.  It should describe the following:

o Project topic.  This should be described by saying what question your project is going to answer.
	(Examples: Which commercially available Java JIT produces the fastest-running code? 
		   Does garbage collection algorithm XYZ make the Jikes optimizing JVM run faster than existing GC's?
		   How can optimizers inline functions even in the presence of dynamically loaded code?)

o Approach.  Are you doing experimental comparison, implementation, or a research paper survey? 
	     What methodology will you use?  

o Deliverables.  What do you plan to hand in?  Just a paper?  Experimental results? Code?

o Materials.  If you're doing an experimental comparison or implementation, what existing software and
		tools will you work with?  If you're doing a research comparison, list three key papers
		you plan to include in your literature survey.


Proposals should be submitted in hard copy in class on the due date.  I will give feedback on them as
quickly as possible.   I may encourage you to narrow your topic, use a different approach, or use
different tools.  In rare cases, I may require you to change your topic.  It is a very good idea to 
discuss topics with me in advance.

PROGRESS REPORT

A 1-2 page intermediate progress report will be required about one month into the project.
This is intended to help keep projects on track.

CLASS PRESENTATION

This is not required, but is a good thing to do.  It can only help your grade.  
(But note that presentations need to be made well in advance of the final project due date.)

PROJECT WRITEUP

All projects, even those whose primary product is code, must include a written summary of methods
and results.