Write up the results of your testing. Begin your report with an executive summary. The body of the report should be no longer than four pages. Put your test scenarios, raw data, your testing procedure, and your informed consent and pre-test questionnaire in an appendix.

What will be an ideal response?

Grading approaches will vary for this. Here are some guidelines that we’ve used when grading test writeups.
Format considerations:
1 Check the length of the report without the cover page and without any printed appendices. If the report is longer than 4 pages, write "Report is too long" and deduct 10 points.
2 The report should begin with an executive summary with a heading entitled "Executive Summary". The executive summary should be two paragraphs long.

a. If there is no executive summary, write "no executive summary" and deduct 15 points.
b. The there is an executive summary but it is not labeled with a heading, write "Add a heading called 'Executive Summary'" and deduct 3 points.
c. If the executive summary is longer than 2 paragraphs, write "Shorten the executive summary" and deduct 5 points.
d. If the executive summary does not appear at the beginning of the report, write "Place executive summary at beginning of report" and deduct 7 points.

1 Every time you see a verb in passive voice, write "passive voice" and deduct 1 point.
2 There should be no discussion of the testing procedure in the body of the report. If such a discussion appears in the report, write "Move description of testing procedure to appendix" and deduct 10 points.

Content considerations
1. Examine the appendices to see that they contain
a. ( 10 points) the test scenarios.
b. ( 5 points) a copy of a pre-test questionnaire.
c. ( 5 points) a copy of the informed consent document.
d. ( 20 points) the raw data, which are the observations they recorded during the tests. These can take the form of either scanned documents or a file of transcriptions. Some students used a scanner to make copies of the note cards. Some may include the actual cards. Other students preferred to type up the observations and put them in a Word document. Any of these three forms is okay.

If any of these items are missing, deduct the specified number of points.
Compare the raw data to the findings that appear in the report. The wording in the report may be different from the notes taken during observation, but it is important to find a correspondence between the findings in the report and the
McCracken and Wolfe User-Centered Website Development
Answers to Questions
observations taken during testing. If a finding (or user problem) appears in the report but does not appear in any form in the raw data, circle the finding in the report and write "Raw data does not support this." and deduct 15 points.
Deduct 15 points for each time this happens. This is an egregious mistake -- the central purpose of a usability report is to communicate the problems encountered during the testing. The students need to learn that one cannot include "problems" that did not occur during testing.
1 Look for the recommendations in the report. Do the students give a rationale or a reason for each recommendation? If a recommendation appears without a rationale, write "What is your reason for this recommendation?" and deduct 10 points.
2 If the students mention a user problem without also mentioning a possible way to fix the problem, write "How should the client fix this problem?" and deduct 10 points.
3 Examine the recommendations. Are they specific enough that a software developer or web developer could implement them? If not, write "Be more specific in your recommendation" and deduct 5 points.