Hit report doc will provided your swin email address
HIT2316/6316 Usability Report 1: Context of Use
Introduction
Table 1 shows a summary of a suggested work schedule and submission details for the Report 1: Context of Use.
Table 1: Report Submission Summary
|
|
|
|
|
|
|
|
|
|
|
| Submission Instructions | |
|---|---|
|
WARNING: You are encouraged to read the marking criteria carefully and not to rely on work submitted in previous
|
|---|
HD - Outstanding (8.5-10)
1. Excellent analysis of problem statement.
3. Analysis of context of use is used in a well reasoned argument to suggest user interface design constraints.
4. Substantial, well documented research from a variety of sources is presented to support analysis and
tables and figures are labeled with numbers and informative titles. Report is presented very professionally. Pages
are numbered and there is a table of contents. Referencing is consistent and conforms to recognised style (such as
3. Evidence collected from data gathering is used to justify analysis and documentation.
4. Analysis of context of use is used to suggest user interface design constraints.
HIT2316/6316 Usability
3. Some attempt is made to use the analysis of context of use to suggest user interface design constraints.
4. Demonstrates some attempt to apply research/data gathering techniques in regards to discovering information about the context of use.
2. Reasonable overview of context of use, but patchy and unclear in places. Some gaps and misunderstandings in how to apply documentation techniques.
3. Limited attempt at data gathering. Data gathering is not well directed. For example, interview or survey questions are not well directed to the problem statement, background research does not appear to be directly relevant to problem statement. Research activity is very narrow in focus (i.e., one or two sources).
1. Poor analysis of the problem statement. There are large gaps in description of the domain or description is not well targeted/relevant to the problem statement.
2. Description of context of use is missing some aspect or element. There is an awareness of documentation techniques, but the application of the techniques is often flawed.
N - Low Fail (0-3.5)
1. Very poor analysis of the problem statement. There are large gaps in description of the domain or description is not well targeted/relevant to the problem statement.
HIT2316/6316 Usability
Swinburne University of Technology R1- 36. English expression is poor. Meaning of sentences is often unclear. Paragraphs lack proper construction. Very difficult for reader to follow. Tables and figures difficult to read. Report is not well presented. For example, inappropriate changes in font, headings and body of report are not clearly defined, pages are not numbered. Referencing is non-existent.
