| Department of Computer Science and Engineering |
CSE 134A |
| University of California at San Diego |
Fall 2002 |
Project 1 Grading Criteria and Comments
Below are the criteria that will be used to grade
Project 1. We also mention some common mistakes that should be avoided.
Usability (8 points total)
A ___/3 Readable and appealing text and graphics,
B ___/1 Handles user input well (HTML, quotes, etc. inside messages)
C ___/2 Reasonable UI: (instructions, form structure, error messages,
information density, etc.)
D ___/2 Navigational ease of use
Common problems:
Frames:
using these unnecessarily is one of Nielsen's mistakes.
Spelling
mistakes.
Hard
to read text and background colors.
A
URL on ieng9 that doesn't work.
Code quality (8 points total)
E ___/2 Comments (especially for difficult code)
F ___/2 Clarity (variable names, code structure, flow of control, small
number of files)
G ___/2 Modularity (using functions, and not reinventing PHP functions)
H ___/2 Error handling (sufficient error checking)
Common problems:
You
should have a comment header at the top of every file, and at the top of
each function, not just at select places within the code. Aim for
simplicity when designing and organizing software; although code should
be modular, do not create so many functions that it is difficult to understand
the navigational flow. Every file within the directory should be
used in the implementation, otherwise remove it. That not only makes
for better software design, but it also makes it easier for us to grade!