Copyright © 2002 Katrin Becker 1998-2002 Last Modified August 14, 2002 12:22 PM

> > > > CPSC 461 File Structures
> > > > Assignments, Fall Session

You must attempt and submit ALL assignments in order to pass this course. 'Extras' and bonuses are no guarantee of an 'A'. If they are not well-designed, they will not be given extra credit (i.e. poorly thought out or designed extras are a liability rather than an asset).

GROUP WORK OK
Hand in your assignment to the assignment boxes on the second floor of the Math Sciences Building near the elevators. Place your assignment in the box marked with your lab section and TA's name.

| Asst | Worth | Due | Notes
1 | Hardware | 5% | Friday, Sept. 27 | To be presented in Labs September 30 - October 4. Approximately 10 Minutes.
2 | Assignment: Image Search | 20% |  |
Part 1 | [outline/design] | (5%) | Friday, Oct. 11 | *note: submission of this part [only] optional If part 1 is not submitted; part 2 will be worth 10% and will still require documentation and explanation
Part 2 | [CODE; analysis; measurements] (5%) | (5%) | Friday, Nov. 8 | Demos, in labs, as appropriate [those focusing on the image matching as opposed to the search might not have demos].
Part 3 | [post-mortem] | (10%) | Friday Nov. 22 |
3 | ??? | 5% | Friday, Dec. 6 |

General Marking Criteria:
IMPORTANT NOTE: if there is any evidence that you did not do your own work on an assignment, an 'F' will be assigned for the work in question and both the CPSC Department Head and Dean of Science will be informed in writing.
A program that does not produce correct output is considered to be a non-working program. A program that doesn't work cannot receive a passing grade.
A mark of 'C' does NOT mean there was anything wrong with your work... 'C' means average.
All Assignments require at least some explanation and discussion. You will be marked on your technical writing style and your ability to communicate as well as on content. Documentation must be professional; style must be readable, and correct (proof-read your work!!!). You are responsible for the adequate testing of all your programs (even if you are only required to hand in the final results). It will be assumed that intermediate testing has been performed.
0= assignment not handed in (no reasonable effort will receive a '0')
F= major errors:

programs that don't compile
serious logic errors
failure to follow assignment specifications (i.e. without prior written approval from the T.A.)

D= less serious errors -or- unacceptable submission

numerous smaller logic errors
unjustified deviations from assignment specifications
minimal effort
programs that do not produce correct output or one that is inadequately tested (working or not)
undocumented programs (working or not)
on a discussion paper: containing too many grammatical or spelling errors

: unprofessional style
: poorly organized

C= acceptable program: AVERAGE effort

program works
clean; reasonable; acceptable documentation;
on a discussion paper: complete, correct, comprehensible, professional

B= above average: a well considered solution; well explained; clean code; efficient

A= excellent: well done; good writing; has some nice extras;

Copyright © 2002 Katrin Becker 1998-2002 Last Modified August 14, 2002 12:22 PM