You will be given programming challanges throughout the semester, typically one each week. You are expected to do them by yourself, on your own time. You are also expected to print your work, and give it to your instructor at the beginning of the class when it is due.
The programming challenges will be posted here.
Use a monospaced font to print any code (or pseudo-code) of your solution.
Make sure to show enough runs of your solution to reasonably prove that it works for all cases. For example, if you have an "if" statement, you should show that it works no matter if the condition is true or false. This may not apply to some programming challenges.
This should appear at the very top of the paper you hand in.
Put this information at the top-left
of the page.
Your Name
CSc 2010 Programming Challenge #1
Account: your account
name (otherwise student email)
Due date: put the due
date here
Paste a log of your activity here.
Turn in a hard-copy (printout) of your work. Electronic copies will not be accepted.
You are expected to turn in these assignments on-time. Do not turn them in early unless you have the instructor's permission to do so.
The printouts must be handed in at the start of class. Points may be deducted if you walk into class late, or if your assignment is not ready to hand in right away. Make sure that your printouts use a monospaced font.
Do NOT call your file ``hmwk1.m'', or it may overwrite your homework! Make sure to keep a backup of your work.
Include a complete but concise log of your activity. Complete means that anyone who types in what you type will see what you report. You should not include extraneous things.
Multiple pages must be attached by staple, binder clip, paperclip, etc.
You are responsible for making the printout look professional. This means removing any extraneous or weird (non-alphanumeric) characters that might appear in the printout.
Grading for these will be very simple: we check to see that you did the work, that it is correct, and that it is on time. The grading on these programming challenges will be typically a check (full credit), a check-minus (7/10th credit), an X (half credit), or a zero (no credit). In rare cases, there might be a check-plus (full credit plus bonus points). The grader may assign other grades as he/she sees fit, such as a percentage, but this is up to the grader and may be overruled by the instructor.
To be clear, these assignments deviate from the normal policy on late work. A late programming challenge will result in a lower grade, e.g. from a check to a check minus, from a check minus to an X, or from an X to a 0.
Copyright 2010-2011, Michael Weeks