Saint Louis University |
Computer Science 180
|
Dept. of Math & Computer Science |
The table below lists the programming assignments and associated due dates.
| Program | Topic | Due | Collaboration Policy |
|---|---|---|---|
| prog01 | Credit Card | Monday, 3 February 2014, 11:59pm | pair |
| prog02 | Leaky Stack | Friday, 21 February 2014, 11:59pm | individual |
| prog03 | Smart Stack | Monday, 3 March 2014, 11:59pm | pair |
| prog04 | Merge | Monday, 24 March 2014, 11:59pm | individual |
| prog05 | Image Compression | Monday, 31 March 2014, 11:59pm | pair |
| prog06 | Huffman Decoding |
Monday, 28 April 2014, 11:59pm |
pair |
| prog07 | Huffman Encoding | Monday, 5 May 2014, 11:59pm | pair |
For each assignment, you must submit all source code files that you have created or modified. For many assignments, we will have provided you with a number of files containing source code that need not be modified. In such cases, there is no need for you to re-submit these files; we have them already.
You are required to submit a text file titled "readme" with every program you submit. Please do not submit any formatted files such as those produced by Microsoft Word or other word processors. It will be read at the time your program is graded, so it allows you to give helpful information.
The content of the file should generally include
Your name
A brief (i.e. one or two paragraph) overview of your program and any interesting design decisions that you made.
A clear citation of any help you received on this program from other (approved!) sources, as detailed in the policy on Academic Integrity.
Many of our program assignments explicitly require the inclusion of additional, specific information in this file. Please read the individual program assignments carefully.
Finally, you may include any other discussion that you feel will be helpful when grading your assignment. For example, if there are known bugs or problems with your program, you might briefly discuss them here.
For some of the programming assignments, you will be asked to submit an additional file "inputfile" that provides test input for the program. In these cases, we will run all of the students' programs on all of the students' test inputs. Your goal will be to have your test input fool as many students as possible while having your program work correctly on as many of the other test inputs as possible.
In such cases, please make sure that your input files conform strictly to the expected format standards when the program driver is run using your file as input. Again, such input files must be submitted as a plain unformatted text file (for instance one created with "Notepad" on a Windows system). Do not submit any formatted files such as those produced by Microsoft Word or other word processors.