home—info—lects—labs—exams—hws
textbook—tutor/PIs—java.lang docs—java.util docs
Homeworks
Instructions for submitting
-
Your file must include
your name, the assignment-number,
and your 120 section (e.g. “10:00”)
at the top of your file, in comments.
-
Turn in hardcopy of your work.
Review questions can either be hand-written,
or typed as a comment in a program.
All program problems should be programs you compile and run;
turn in a printout.
Always due at start of class on the due-date.
-
If your function does not work completely,
clearly state so at the top (in comments).
You get more points for knowing what your program doesn't do,
than not knowing.
(Submitting code which doesn't compile, without acknowledging such,
may result in a summary 0.
In the workplace, it is unacceptable.)
-
If the gradebook in WebCT lists a homework but your score is empty,
then it means I think you didn't turn it in.
(Note that if I haven't released a column to the gradebook section
of WebCT, then I haven't yet finished grading for that assignment.)
It is your responsibility to report any missing scores in the gradebook.
-
Moreover: Any empty gradebook entry
which is not reported within three weeks of appearing in the gradebook
is liable to not be graded, and you will get a 0.
(Otherwise I have too many students suddenly needing regrades
in the last week, of assignments I'd graded months earlier.)
- Spelling and punctuation counts (in your comments).
The first such error is okay, but -1/2 for every error after that.
(Sentence fragments, though, can be acceptable if the context is clear.)
Grading notation
If you're wondering about
funny-looking markup
on your returned papers,
check out
home—info—lects—labs—exams—hws
textbook—tutor/PIs—java.lang docs—java.util docs