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 Coding 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 Monday, January 12
- Life-Long Learning
- email me your choice of a book from this list (first come first serve) by the end of the day, January 25
- these books will be presented approximately 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.
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 Monday, February 9
To see which team you are on, check online here. - Flocks, due Saturday, March 28
To see which team you are on, check online here. - Springs, due Sunday, April 5
To see which team's code you are working with, check online here. - VOOGA, due Saturday, May 2
To see which team's code you are working with, check online here.
