Usability Report Template for Web SiteWord文档下载推荐.docx

1、MethodFindings and recommendationsConclusionAppendices1.Executive SummaryThe Executive Summary comes before the table of contents and is intended to summarize the entire study in one detailed paragraph. The idea is to provide the most pertinent information for stakeholders who do not have time to re

2、ad the entire report. It is important to come right out and provide one or two major findings, such as, “The majority of users preferred prototype A over B.” That way the reader does not have to dig for the most important information.Should include a sentence or two for each of the following:purpose

3、 of the studydate of testsnumber of participantslength of testslocationmajor findings2.Purpose of the StudyThis section of the report can also be concise. If you are comparing two prototypes, for example, talk about the critical differences and what the stakeholders were hoping to find in the usabil

4、ity sessions. A good purpose section should give describe the product tested and the usability goals being measured.Should include:the primary reasons for conducting the studya description of the product and its context of usethe usability goals identified for the product3.ParticipantsIn this sectio

5、n, you should describe the participants selected for the test session. Include all relevant demographic information and explain how participants were selected. Often a table format supplemented by a few paragraphs works well for this section.how they were contactedtotal number of participantsappropr

6、iate demographic data （age, gender）computer/web experienceoccupation/major4.MethodThis section should be the most detailed so far. As with an academic study, the method section should allow someone who was not present at the sessions to replicate the procedures. Describe how you conducted the study,

7、 the type of data you collected, the tasks you used and any other relevant information that your readers may want to know.sufficient information for another person to replicate the studywhat was recorded, e.g. errors, number of clicks, commentsentire process from the initial greeting to the end of s

8、essiontask description （may include the actual list in the appendix）facilitation techniquesroles of people involved in the sessiontechnical details: network connection speed, browser version.5.Findings and RecommendationsThe findings and recommendations section of the report is the most detailed of

9、all and may be represented in various ways. At UCS, we tend to use a table with three sections: observations, interpretations, and recommendations. We find that the interpretation section allows the reader to understand how we arrived at our recommendation while giving him/her the freedom to agree o

10、r disagree with our perception of the problem. Regardless of the method used, it is important to give the reader unbiased data presented in a concise and easily understood format. If you are not familiar with the product you are testing, it may not be feasible to rank the problems and recommendation

11、s. Talk about these issues with the primary stakeholders to see how they want to proceed.information about what is and is not workingthe severity of the problemsspecific recommendations for improvementscreen shots of applicationdescriptive statistics of data collected for effectiveness and efficienc

12、ySatisfaction survey results6.DiscussionThis section allows you to make any final comments that you wish to add to the Findings section. Keep it brief and reinforce the main takeaway points you wish your reader to remember.a summary of the study, including what went well and anything that went wrong, e.g. high user cancellationspossible next steps for the design team7. Appendicesintroductory protocollist of tasksblank data collection instrumentssummary of qualitative comments