All programming assigngments are to be done coded individually. This will be strictly enforced. All code in which you consult others, including but not limited to class examples, text books, and other students, should be attibutted.
Submissions that do not compile will receive a grade of zero. All submissions must include a makefile which compiles your program when I type "make". If you cannot complete a programming assignment, make as much progress as you can by implementing your design. Functions do not have to do anything useful (in some cases they may be empty), but they do need to be present. Also, try to present some evidence of the progress you made. For example, if you have to do a series of calculations but you could only get through some of them, have your program display the result of the last calculation you did.
Submissions should be made by creating a tar file using tar cvfz <filename>.tar.gz <files> which includes all pertinent files. This file should be attached to an email and sent to my cs email account.
A paper copy should also be turned in at the beginning of the next class. The paper must include the following statement with your signature underneath:
"I hereby declare that I have abided by the Honor Code during this assignment."
Late policy: 20% will be deduct for each class meeting.
| Programming Assignment | Due Date | Description |
|---|---|---|
| 1 | 2/4/2008 | Using C to implement Priority Queues |
| 2 | 2/20/2008 | Binary Tree Fun |
| 3 | R is for Retrieval | |
| 4 | 4/4/2008 | DFS Cycle Detection on Directed Graphs |
| 5 | 4/18/2008 | His and Hers Graph Algorithms |
| 6 | 4/30/2008 | Power Grid Repair |