CAS CS 210 - Computer Systems
Fall 2010
Guidelines on Submissions of Assignments
CAS CS 210 - Computer Systems
Fall 2010
Guidelines on Submissions of Assignments
Assignments will be available on-line. If assignments are handed out, this will be done at the end of class meetings. Extra copies will be left in one of the handout/pick-up "open" boxes (located in the top), labeled "CS-210", in the hall outside of MCS 137.
Homework assignments and hard copies of your programming/lab assignments are to be handed in using the slotted homework (drop-off) inbox (located in the bottom), labeled "CS-210", in the hall outside of MCS 137 by 4:00 pm on the day they are due. Late assignments must be time-stamped by a CS Office Staff and left in the Teaching Fellow's mailbox (neither in the CS-210 slotted homework inbox nor the Instructor's mailbox). Do not hand in your assignment in the class or during office hours. Do not hand in your assignment by slipping it under the office door of the Instructor.
Graded assignments will be available for pick-up from the outbox.
If you believe that there is a chance that your assignment will be lost by the course staff, then here is how you can protect yourself: (1) make a copy of your assignment before handing it in, and (2) have the CS office time-stamp your copy of the assignment. Claims for "lost" assignments will be considered only if accompanied by a time-stamped copy of what you handed in. There are no exceptions to this rule.
Check for Assignments regularly. Start early!
PROGRAMMING / LAB ASSIGNMENTS
You will be required to submit an electronic copy of your code, in addition to both electronic and hard copies of supporting documentation and any requested written report(s). See Guidelines for electronic submissions.
When explicitly specified, you may have the option to work in teams of two on large programming assignments.
General Requirements on What to Submit
Unless automated and otherwise specified, the program you submit should work correctly and be documented. You should submit an electronic copy of the following:
1.Program: a program listing containing in-line documentation (i.e., comments).
2.Design document: a separate file (a page or so) describing the overall program design, a verbal description of "how it works", and design tradeoffs considered and made. Also describe possible improvements and extensions to your program (and sketch how they might be made).
3.Testing document: a separate file describing how to run your program. Specify the steps that must be followed to successfully run your program. Also, describe the tests you ran on your program to convince yourself that it is indeed correct. Also describe any cases for which your program is known not to work correctly.
It is fine to submit all the above documentation in one README file, given you have clear subtitles. To save trees, you are required to submit a hard copy only of the above supporting documentation and any requested written report(s), but not of your program listing/code.
[Adapted from Prof Matta’s CS 210 2009 Guide]