CSE P 501 Project Report & Meeting

Project Code

In fairness to everyone, all projects are due by the cutoff given in the final part of the assignment. Your report should describe the project that you turned in by the deadline. However, there is always the "last" bug. If you want to make some additional changes to the code and discuss them in your report and at the meeting, we may be able to take small bug fixes into account in evaluating the project - even if these fixes have major effects. But large changes to the project after the deadline, while they may be very useful for your learning, cannot fairly be evaluated as if they were turned by the deadline, and the evaluation will be based on the code you turn in on time.

Report

Please write a brief (a couple of pages should be more than enough) summary of your project describing:

Your report should discuss the entire project, not just the code generation part, so we can use it to help evaluate the overall outcome. You should turn in your report using the online dropbox by 11 pm, Tuesday, June 10. Each group should turn in a single report. Please use pdf or plaintext.

Department of Pedantry Department: Please write the following at the top of the first page of your report:

CSE P 501 Project Report Spring 2014
<names>
<uwnetids>

Please expand the nonterminals <names>, <uwnetids>, etc. with your actual names, uw netids, and meeting information as appropriate. Don't include a separate cover page.

Meeting

We have no mandatory meetings this quarter. However, if you would like to talk about your project or any other aspect of the course, the course staff will be available to meet at the end of the quarter. This would be particularly useful if you have implemented extensions and wish to demo them.

We will be available to meet in the evening of June 11 (Jim at Microsoft, Nat at UW). Please email us to schedule a slot.