Note: All questions regarding the grading of the projects should be directed to the GTA, Rick Neil.

General Comments

• General formatting errors, typographical errors, etc.:  1-Point deduction per unique occurrence.
• Words that were spelled correctly but were the wrong word given the context: 2-point deduction per occurrence.  An example of this is "The user will bee able to access the system...".  This type of error is taken as an indication that the document was not proofread carefully.  A spelling checker is insufficient to catch this type of mistake.
• Failure to follow the general project formatting instructions:  No deduction for Project 1.  In general, the projects are to be in a binder with a labeled, tabbed divider between each deliverable.  Because of the confusion due to the late return of Project 0, there was no penalty for not meeting this requirement for the submission of Project 1.  On future deliverables, these instructions must be followed exactly or deductions of points will result.  If you are unsure if you are meeting the requirements, please see the GTA during office hours for clarification.

Business Objectives

• Incorrectly specifying business objectives:  5-15 point deduction depending on severity of the error.  An example of this class of error would be confusing usability goals with business objectives.

User Classes

• There were instances of statements that were vague or otherwise unclear.  Also falling into this category are statements that could have more than one meaning because of wording or a lack of proper punctuation.  These errors resulted in a 2-point deduction per occurrence.
• Poorly specified user classes by not indicating the relevant or requisite skill sets of the user class resulted in a 5-point deduction.

Usability Goals

• Including specifications from other LUCID tasks (e.g., mixing business objectives into the usability goals):  2-point deduction per occurrence.

High-level Constraints

• Ill-specified constraints (i.e., statements that are not restrictive to the design space but rather to users, the client, etc.) resulted in a 10-point deduction.  To commit this error is to clearly 'miss the boat' on what constraints are from the perspective of a design team member.
• Poorly worded constraints:  5-point deduction.  This generally involves situations in which the constraint was not clearly stated but could be inferred from the text.

High-level User Tasks

• In general, this section was, thankfully, clean.  For answers to specific questions regarding specific deductions, please see the GTA during office hours.