CSE 262 Class project report requirements

The final report is due by 9PM on Saturday March 16th. Turn in a hard copy in my mailbox on the 2nd floor or slip under my door in an envelope. Also email me an electronic copy (instructions below), which includes up-to-date Self Evaluation form.

Your report should be a polished piece of work. Read over these Tips for authoring a writeup. To get an idea of what I expect, look at project reports from courses I’ve taught previously.

Your writeup should describe the application at a level appropriate for a technical, but non-expert, audience. Thus you will likely need to provide some background knowledge to allow the audience to understand the application.

The structure of your writeup should generally follow that of the presentation. In addition, discuss any revised milestones and completion dates that you established previously, including an explanation.

As with the progress report, include a team-evaluation that discusses the division of labor and other aspects of how you worked together as a team team. (If working as a group of 1, modify as appropriate.) A copy of the form is available in html.

The grade for your project report will be based primarily on it thoroughness but also on the presentation. If you have negative results, report them. Such results will be rewarded just as positive results are rewarded, so long as they are discussed thoroughly and are well presented.

The electronic submission should be a compressed archive. e.g. .tgz .zip. If you like, send me a URL where I may download the file, rather than mailing it to me.

When extracted, the compressed archive should produce a directory of the form <LASTNAME>_<INITIALS>, i.e. Baden_SB.tgz. Be sure to remove .o files and executables before creating the tar ball. At the top level of your directory there should be a navigation file listing all the parts of your electronic submission. It could be an HTML file with clickable links, but an ordinary ASCII file README.txt will do. Include, at the top level, a copy of your report in PDF format, of the form <LASTNAME>_<INITIALS>_Report.pdf, e.g. Baden_SB_Report.tgz.

Include the following 3 directories.

• src: Contains all source code along with a Makefile, so that your results can be reproduced. Subdirectories may also be included if needed.
• data: Raw experimental output, ASCII files, spreadsheets, etc. If you want to include the tabular form of plotted data, be sure to document this in your navigation file. Similarly, if you use a spreadsheet to plot your data, you should keep the plots together with the data.
• plots: If you have separate plot files, for plots used in your report, png, jpeg, etc, put them here.

If you need other directories be sure to explain them in the navigation file.

Maintained by [Thu May 19 21:57:38 PDT 2011]