For each project you develop for this course, you must submit your program electronically, using the directions available here by the end of the day (i.e., 11:59:59pm) on the due date given. You are responsible for ensuring that all files are turned in on time. You may submit an assignment electronically as many times as necessary, but only the files included in the last submission will be graded. Thus, you should always submit all your project's source files --- even if they have not changed since a previous submission.
Projects that you submit should follow this set of Design Conventions. Updates may occur during the semester.
Non-code Projects
These projects are intended to help you reflect on your own computing experience.
- Introductions, due Wednesday, September 3
- Life-Long Learning, due November 1
These books were presented on this schedule.
Recitation Projects
These are solo projects, on which you must work by yourself. For each solo project, you must hand in an automated means of testing every line in your program.
- Bins, due Monday, September 1
- Roulette, due Monday, September 8
revised again, due Sunday, September 14 - Jotto, due Wednesday, September 17
extended, due Saturday, September 20 - NanoGoogle, due Sunday, September 28
- TagCloud, due Friday, October 24
Team Projects
These are assigned to groups of two to five students. For each team project, submit only one version of the program and project artifact electronically.
- NanoGoogle, due Friday, October 10
To see which team you are on, check online here. - FennecBrowser, due Sunday, November 9
To see which team you are on, check online here. - VOOGA, due Sunday, December 11
To see which team you are on, check online here.
