CS116 Summer 97
How to turn in your programs
What to turn in.
- Everything you turn in must be in CodeWarrior format.
- You must turn in a full CodeWarrior project, not just CodeWarrior
source code files. When you create your project in CodeWarrior, a
folder is created for it (with the same name as your
project). You must turn in this folder.
- Included as part of the basic CS166 project is the file
writeup.doc, which you must modify to include the
following:
- A description of the design of your program. This includes
the general organization of the various parts of your program,
and a description of your functions, your classes, and other
data structures used in your program.
- Extensive test runs of your program (more about test runs below).
- For projects, don't forget to indicate the late hours you have
used up (fill in the appropriate parts in provided for you in the
header of writeup.doc).
Where to turn it in.
You will turn in your CodeWarrior project folder electronically. This
can be done from any Macintosh computer in the Maclab. Drop your
folder into the course drop box. The path is:
MacLab Resources : Courses : Summer 1997 : CS 116 : Drop Box
How to read the point ditributions.
For each programming problem, you will be graded on the basis of the
following criteria:
- Correctness. Your solution must be correct, i.e.
it must produce the result that the problem asks for.
- Effieciency. Your solution must be efficient,
i.e. achieve the result with as little resources (time, memory,
etc) as possible.
- Style. Good style is achieved by respecting the
following points:
- Give your functions meaningful names. One should get a pretty
good idea what a given function does just by looking at its
name.
- Give your variables/constants meaningful names. Again a person
reading your code should get a good idea what a
variable/constant is used for just by looking at its name.
- Write adequate comments. One should be able to understand the
function of various parts of your code by reading the
respective comments. For example, what does a given loop do,
what is the meaning of the coditions of a given
if/else, etc.
- Test runs. You must test your program
extensively, either leaving no doubt in yours and the graders'
minds that your program works, or identifying exactly which
parts of your program work correctly and which parts don't. If
your program works correctly, but you do not provide adequate
amount of test cases to demonstrate that, then you will not get
all the test points. On the other hand, if your program does not
work correctly, and your test cases identify exactly what works
and what doesn't, then you will receive all the test points.
The shorthand [22pts: c7e4s5t6] for the point
distribution of a problem means that it has a total of 22 points, 7
for correctness, 4 for efficiency, 5 for style, and 6 for test runs.
email:behfar+cs116@cs.uchicago.edu