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, unless otherwise noted. 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 to these conventions will be announced during the semester.
Non-code Projects
These projects are intended to help you reflect on your own computing experience.
- Introductions, due Monday, August 31, by the end of the day
- Life-Long Learning
- email me your top two choices of a book from this list (first come first serve) by the end of the day, September 4
- you will be present during class according to this schedule
Individual Projects
These projects are to be competed by yourself. For each individual project, in addition to your project code, you must submit an automated means of testing every line in your program.
- Bins, due Thursday, August 27, by 6pm
- Arithmetica, due Thursday, September 3, by 10pm
Final revisions due by the end of the day, Sunday, September 6 - Jotto, due Sunday, September 13, by 10pm
Team Projects
These projects are to be completed in groups of two to four (depending on the project). For each team project, submit only one version of the program and project artifact electronically.
- Picasso, due Wednesday, September 30
Individual Analysis, due Friday, October 2
To see which team you are on, check online here - DataViz, due Friday, October 23
Individual Analysis, due Monday, October 26
To see which team you are on, check online here - VOOGA, due Friday, December 11
Individual Analysis, due Sunday, December 13
To see which team you are on, check online here
