Programming assignments

All programming assignments are to be submitted using the checkin program. When checking in assignment number i use HWi as the name of the assignment (e.g. HW1 for the first assignment). Make sure you submit your assignment as a tarball, as HWi.tar, and only include your .java files unless specified otherwise.

You can practice checking-in by submitting a file to HW0 throughout the semester. This assignment will never be graded but please remember to submit the file as a tarball, HW0.tar.

For those of you who develop software from a non CS machine, make sure your code compiles and executes 'properly' on a CS machine before submitting your assignment as these are the only machines on which your programs will be tested.

When working in teams, submit only one assignment per team. Include the names of all members of the team in the source files.

• Assignment 1. As data you can use this example ratings file.
• Assignment 2. As data you can use this example events file.
• Assignment 3. As data you can use this example events file.
• Assignment 4. The event file of assignment 3 is still applicable.
• Assignment 5. And the data file.
• Assignment 6, the events and parameters file. There is also an opportunity for extra credit (worth 10 pts)

The grading policy for programming assignments is here.

All programming assignments are due at 5pm on the due date.

Written assignments

Written assignments are due in class on the due date.

• Assignment 1
• Assignment 2
• Assignment 3
• Assignment 4