Program Assignments
Submission Procedure
We expect your code to be in your private repository in the class's GitHub organiztion.
Grading
Grades are given based on how what you turned in runs on CSIL, which is running java version 1.7. One way to know how your program will run on CSIL is ... to run it on CSIL. It is not sufficient to prove that it worked on your personal computer.
Remove all extraneous comments before your code is due.
The Pair Programming Option
On all programming assignments, you may work in pairs.
The intention is for you to use
pair programming best practices
as a way of learning to produce higher quality code.
If you choose this option for a particular assignment, turn in just 1 solution, giving both names in the @author annotation for all Java files.
Programs
Each program must be completed & submitted no later than 5 P.M. on its due date. A link to a specification of each programming assignment appears below at least 1 week before the assignment is due.
| Assignment | Due Date |
|---|---|
| 1: Visualize an n-clique | April 10th |
| 2: A Graphical Virtual Machine | April 17th |
| 3: Zap 'em! An animated Game | April 24th |
| 4: SuperZap 'em! A Modestly Enhanced Zap 'em Game | May 2nd |
| 5: GALA: GVM Assembly Language | May 21st |
| 6: GVM 2.0 (Stack machine) & Gala 2.0 (Debug tools) | June 7th |
Late Submission Policy
We subtract 0.5 points for each hour of lateness. More precisely, if a submission is m minutes late, then the amount of deducted points is 0.5 ceiling( m / 60 ). For example, if the submission is 45 minutes late, 0.5 points are deducted; if the submission is 90 minutes late 1 point is deducted.