Programming Assignments

ICS-33: Intermediate Programming


Programming assignments are typically due about two weeks after they are assigned, at 11:30pm, typically on a Tuesday night (but look for exceptions). To turn in programs, and verify the submission, use the Checkmate Homework Dropoff system: it is also available on the standard frame index on the course website: it uses UCInetID Secure Web Login.

Ensure that you submit the code you wrote, not empty files, nor the original files that you downloaded. Ensure that your code runs the batch self-checks correctly. This is your responsibility. Be very careful and double-check what you submit to avoid any mistakes: if you are not sure that you submitted the correct code, resubmit it.

No Late Submissions

You receive NO POINTS for late submissions, unless you have discussed the matter with me and gotten my official permission (typically, granted well-prior to the due date -not at the last minute- always via email, not just orally; contact me as soon as possible).

IN ALL CASES, you must submit (on time) whatever part of the program you have written, if you are to receive any partial credit for a submission (either on time or late with permission); if you submit no files, I must assume that you have done no work on the assignment (which will result in a grade of 0 for it). If you are still programming the day that an assignment is due, you have planned poorly; if you are still programming an hour before it is due, you have planned very poorly.

Extra Points for Submitting Early

If you submit your program early, you will receive extra points (1 point if you submit it 24 hours early, 2 points if you submit it 48 hours early). Since each program is worth 50 points, you can raise your grade on a program by 4% (almost half a letter grade) by turning it in two days early. Note that turning in a program more than two days early still results in just 2 extra points: the maximum you can get for an early turn-in.

Given Extra Points for Submitting Early and No Late Submissions, you should immediately start working on your programs when they are assigned. You should plan to finish them early, both to receive extra credit and to avoid missing a deadline. Expect that you will run into a few big "bugs" during each assignment, which will take a day to figure out and fix; plan to finish early to garner the extra credit (in the best scenario) or still finish on time (in the worst scenario).

Pair Programming

We will use pair programming on most assignments (recommended, although it is sometimes prohibited); it is only on these assignments that students can closely collaborate with their partners, turning in one copy of a jointly written program. See Pair Programming for details about pair programming, and the right and wrong ways to do it. There is a tremendous amount to be gained by both partners, if they pair program the right way: both students working together, not splitting-up the assignment.

You can keep the same partner for multiple assignments or switch. Try to find a partner in your lab who has approximately your skill level and study habits (e.g., working evening vs. weekends, work ethic to submit programs early); try to find someone who lives near you (or with whom you can easily meet outside lab) because I expect partners will need time outside labs to finish the programs. You may partner with someone in a different lab, but you both must be able to attend (and actually attend) one of your labs for 4 hours/week. I recommend finding a partner when you are attending your lab, but there is also a MessageBoard Forum for this task.

Starting/Finishing Programs

Please read each assignment completely and carefully before starting it. I suggest that you print and then read it, marking relevant material with a highlighter (details that you might forget by the end of an assignment). Then, re-read the assignment before submitting your work. Programs are typically assigned on Tuesday and due two weeks later on the following Tuesday, when the next program is assigned; students should plan to have finished their current programs on Monday, so they can start on the new programs in lab on Tuesday; see above for how this leads to extra credit.

Identifying Submissions

Only ONE STUDENT of the pair should submit the assignment (all parts of it). If students work in pairs, BOTH NAMES and their UCInetID names must appear in a comment at the top of each submitted program. For example if Romeo Montague (whose UCInetID is romeo1) submitted a program that he worked on with his partner Juliet Capulet (whose UCInetID is jcapulet) the comment at the top of each .py file would appear as:
  # Submitter: romeo1(Montague, Romeo)
  # Partner  : jcapulet(Capulet, Juliet)
  # We certify that we worked cooperatively on this programming
  #   assignment, according to the rules for pair programming
If you do not know what the terms cooperatively and/or rules for pair programming mean, please read about Pair Programming before starting this assignment.

If the names do not appear at the top of all your submissions in exactly this form, points will be deducted. If you are submitting by yourself, you may omit all lines but the first (Submitter).

Multiple Submissions

Checkmate allows students to remove a submission and then resubmit. We will grade only your final submission submitted before the Due Time (and extra credit points are based on only that submission's time). For assignments with multiple parts, please turn in each part as you finish it, so that I can accurately assess the progress of the class as a whole during this assignment. If you discover something wrong with your code after you submit it, you can always correct the code, remove the old code, and resubmit the new code.

No Retrieval

Students cannot retrieve a submission from Checkmate: it is a shortcoming of the program (but designed to protect other students from possibly downloading your work); so, you are responsible for archiving your work so that you have a copy of what you submit. Also, ensure that you always submit in the correct (most up to date) version of your code; double-check; if you are unsure, resubmit.

Instructor Solutions

I will release my solutions to all assignments the morning after they are due, the EEE dropoff box for the class.

Programming Assignments Schedule: Due at 11:30pm

#0 9/2710/4 Python, Eclipse (the Debugger Perspective), and Testing Prohibited
#1 10/410/16 Iteration and Major Data Types

IMPORTANT: In an effort to motivate students to work on these programs well before the due date (and learn the material better, possibly earning extra credit points for submitting them early), I will grade only two parts submitted on 10/15 or later (and only one part submitted 10/16).

You can submit as many parts as you want earlier. In fact, if you submit all parts by 10/14 you will earn 2 extra credit points; but if you submit all parts on 10/16, we will grade only one, discarding the other four.

So, start early on this assignment and work at a steady pace, trying to submit your work well before the due date. Submit only two programs on 10/15 or later; submit only one on 10/16 (so either submit two on 10/15, or submit one on 10/15 and one on 10/16; but if you submit two on 10/15 and one on 10/16, one won't be graded).

#2 10/1610/30 Classes, Overloaded Operators, and Iterators Recommended
#3 10/3011/13 Namedtuple (Text Processing: Programs writing Programs) Recommended
#4 11/1311/27 Annotation Checker (Mutual Recursion) Recommended
#5 11/2712/9 Inheritance and Animation Prohibited