This assignment is out of 10 points. The following is how the grading breaks down.
Coding Practices (40%)
Formatting and good practices: 15%
Assignment Requirements (60%)
Functional-style Programming: 10%
Returns output in specified format: 15%
Solutions are correct: 30%
Documenatation and good practices counted more on this one than on assignment 2. though it's still only about 30%.
Whenever you have more than one subprogram in a file, you should add a line or two at the top about the program as a while. (Program documentation.) When someone opens your file, they should be able, at quick glance, see what this file does, who wrote it, and when/why. (The point of all documentation is to help some else who doesn't know what you've done or why. Or to help you, when you can no longer remember.)
Because there were fewer components to this assignment, each piece counted for more. There were a few 10's on this one, but also a number of much lower scores too. In future, I'll try not to weight getting the right answer so heavily. Sometimes, students were very close but didn't get it. For example, a few people were checking for NIL or () when they should have been looking for 'FAIL. But this meant that their program's solutions were incorrect.
On the other hand, you should know your code doesn't return the correct output because you test it on a couple of different input cases before you submit it. Right? :)
Oh, and try to keep your code lines about 80 to 100 characters wide. Longer than that, and they wrap on other people's systems, making your code even harder to read. This is especially problematic with Lisp, where matching open and closing parentheses is already difficult.
|~ztomasze Index : TA
: Assignment 1
|Last Edited: 27 Nov 2002|
©2002 by Z. Tomaszewski.