CSE 401 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 (see next section for report details). 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. However, 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 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 2 pm, Sunday, March 14. Each group should turn in a single report. Please use some common document format - word and pdf are best since they're most widely portable. Plain ascii is barbaric, but tolerable.

Meeting

Plan on meeting with the instructor during finals week for 20 minutes to discuss your project. Meetings will be scheduled for Sunday and Monday afternoons, March 14 and 15. Watch for separate email with details on signups. If none of those times can be made to work, it may be possible to schedule other times; contact the instructor if this is a problem.

Please bring a copy of your report with you. This isn't a formal presentation (i.e., don't waste time preparing PowerPoint slides or anything like that). If at all possible, everyone in your group should be at the meeting.

That's it!  Have a great spring break!