Enjoy the great videos, songs, poems and comics for assignment 9 here.
Note that a small portion of your assignment grade is based on the readability of your program. This readability grade includes style, comments, and the naming of variables and methods. You must include a comment at the top of each source file you modify that includes your name and your netid. Then include a comment for every function and every major block of your code. Function names, variable names, etc should be meaningful. The variable name totalCost is more meaningful than the variable name x.
If you have concerns about an item that was graded (lab, apt or assignment), you have one week after the grade is posted to fill out the regrade form here.
Every Assignment submitted must include filling out the README form in the box below. .
| Assignment | Howto | README | Due Date |
|---|---|---|---|
| Assignment 1: Programming with Blockly | none | README | January 19 |
| Assignment 2: Totem Poles | Howto | README | January 31 |
| Assignment 3: TurtleQuakes | Howto | README |
February 7 Extended to Feb. 8 |
| Assignment 4: Transform | Howto | README |
February 14
Extended to Feb. 21. |
| Assignment 5: Hangman Games | Howto | README |
March 9
|
| Assignment 6: Billionaires | Howto | README |
March 30
|
| Assignment 7: Snarky Hangman | Howto | README |
April 6
|
| Assignment 8: Recommender |
Howto Details |
README |
April 20 Extended April 21 |
| Assignment 9: Song, Dance | None | README |
April 26 April 28 with no late penalty |
All assignments must be turned in on the due date given. You are responsible for ensuring that all files are turned in on time, if a program is turned in late there is a penalty detailed online here.
All assignments should be turned in using websubmit or Ambient. We have added instructions at the bottom of Assignment 1 to explain how to submit using Ambient
Ambient. When you are done with your project and are confident it is satisfactory, you should submit it electronically using the directions available here. You may submit an assignment 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 files -- even if they have not changed since a previous submission. Note, the official time of submission for your project will be the time of your last submission. An assignment will be considered late if the last submission is late, even if your first submission was on time. You may lose points on your assignment if your final submission is incomplete or late.
Important: After submitting, ALWAYS then do submit history to verify all the necessary files were submitted.
Many assignments will include code to get you started. This may consist of completed modules that you will utilize but not modify or modules in which some functions have been completed and others are left for you to fill in. In either case, comments will clearly indicate which sections of the code you may edit and which must not be modified (you can go to these sections directly by using the Tasks view within Eclipse). All starter code may be obtained with the Ambient download tool by following the directions here. The download site for the course is
http://www.cs.duke.edu/courses/compsci101/spring17/snarf/