Computer Science 1050
The table below lists the programming projects and associated due dates.
|Project||Topic||Due||Collaboration Policy||Art Show|
|project1||Draw Something||11:59pm Wednesday, January 27, 2016||individual||art show|
|project2||Landscape Perspective||11:59pm Wednesday, February 24, 2016||individual||art show|
|project3||Missile Command||11:59pm Wednesday, March 23, 2016||pair|
|project4||Data Visualization||11:59pm Monday, April 11, 2016||pair|
|project5||Final Project -- "alpha" version||11:59pm Sunday, April 24, 2016||pair|
|project6||Final Project||11:59pm Tuesday, May 3, 2016||pair|
For each project, you must submit all source code files that you have created or modified. Note that the Processing Development Environment creates a folder for every project. Although you could zip the entire folder and submit, all that I really need are the file(s) with the ".pde" suffix. The content of that file is precisely the text that makes up the source code for the program. For most of our projects, there will likely be a single .pde file to submit (although, on more advanced projects, we may begin to see multiple such files in a single project).
You are required to submit a text file titled "readme" with every program you submit. It will be read at the time your program is graded, so it allows you to give helpful information.
The content of the readme file should generally include
A brief (i.e. one or two paragraph) overview of your program and any interesting design decisions that you made.
A clear citation of any help you received on this program from other (approved!) sources, as detailed in the policy on Academic Integrity.
Many of our program projects explicitly require the inclusion of additional, specific information in this file. Please read the individual program projects carefully.
Finally, you may include any other discussion that you feel will be helpful when grading your project. For example, if there are known bugs or problems with your program, you might briefly discuss them here.