Assignments are usually made in the first lecture of the week. Unless stated
otherwise, they are due at the second lecture of the following week. However,
you should always check Late Breaking News for changes in due dates.
For every programming assignment you must submit printout of source code
and console or file output obtained by running the program. (I have to
be able to see that the program actually worked!)
For every assignment you must put the following information on the first
page. Omission will result in your paper being returned without credit.
Name and student ID number (Jane Doe, 808-00-8888)
Class and section (CPSC 331, TTH 8:30 AM)
Assignment number (Assignment 2)
Due date (2/23/01)
For programming assignments, this information should be included as
comments in the actual code.
Include ample internal documentation in your source code.
Always have separate files for your driver and functions or classes. For
class templates, you can either follow the author's style with an #include
"className.cpp" in the className.h file, or put the implementation
directly in the className.h file.
When you are asked to submit emperical results, you must always include
some kind of discussion of what the results mean.
If you have used any source code that you did not personally write, identify
it and indicate where you got it.
For pencil & paper kinds of problems, work neatly. Use enough paper
to allow you to lay out your work in an orderly manner, leaving enough
space for grading comments. Use only one side of paper.Do not
use spiral notebook tear-outs. Make sure the answer is clearly identified.
If more than one page, also mark each page with your name.
Seek help when you need it, but do your own work! Never give anyone a copy,
paper or electronic, of anything you do, and never accept a copy of anything
someone else does.