CS 481 Homework Instructions
Homework submissions should be packaged as a .zip (right-click, "Create
.zip Archive") or .tgz (in UNIX, "tar czvf
cs481_hw1_<lastname>.tgz *") file.
- All needed source code. If it's not clear which is the main file, this should be pointed out in the README.
- A README file containing:
- Your name.
- The class and assignment.
- What the program is supposed to do (generally, what I should expect).
- Detailed build instructions, including any external libraries needed.
- A summary of the user interface, including how to exit the program.
- A LICENSE file specifying the legal rights to your code. I
to release my code to the public domain, but you could use the GPL
license, BSD, or even "Copyright <your name> 2005. All
reserved.". I'd like to make available on the course website
anything cool that has a reasonable license; please let me know if
you'd prefer I didn't.
- Homework will be graded based on:
- Completeness & Correctness: how much of the required functionality is actually there (most important).
- Clarity: how easy the code is to read and understand, including documentation (very important).
- Appearance: how good the resulting images look (important).
- Efficiency: how much time and space the code will require (not very important unless a specific goal).
- Comments are much appreciated. Large-scale comments ("This file
runs the user interface when in Fly mode") are generally more useful to
me than small-scale comments ("This is a loop index").
- If your code is derived in any way from something else,
you MUST at least clearly cite that package
in the source code comments and README file. Any project whose
relevant functionality comes mostly from code you did not write will be
considered cheating and dealt with severely. You are of course
allowed to copy huge chunks of uninteresting code (e.g., boilerplate
initialization code) from elsewhere, although
anything substantial you use should be cited.
O. Lawlor, email@example.com
Up to: Class Site, CS, UAF