ahandrewh teaches IAT-334interface design

P2: Heuristics (due June 29/July 1 July 2/July 4)

On this page:

This is old content

Andrew is not currently teaching IAT-334. This material is left online for reference only.

Introduction

Assessing user interfaces using heuristics enables you to see issues or items in your own designs that you may not otherwise find.

In this project you will be using heuristic evaluations to assess the usability of the Canvas calendar feature.

This project is completed individually.

P2: Heuristics is worth 20% of your final grade.

Weekly instructions

This project spans multiple weeks. Please read the weekly instructions carefully.

From June 8 to June 17

This week is for planning your heuristic evaluation.

Please complete the following:

  1. Define two tasks for your heuristic evaluation. These are the tasks that those completing the evaluation will perform. Make sure the tasks are:
    • Important or typical tasks a user might do.
    • Realistic tasks a user might do.
    • Allow for enough variety in activity that your heuristic evaluation should be thorough.
  2. Select which heuristics are relevant. Working with Nielsen's heuristics and your tasks, determine which heuristics are relevant. Use at least four of the heuristics.
  3. Prepare a data sheet for collecting your evaluations. An example is given in the table below.
Task and location in taskHeuristic broken Description of usability problemVisual exampleSeverity ratingRecommendations

Name or description of task: Specific point in task problem occurred.

Name of heuristic broken.

Description of the problem that occurred.

Insert a screenshot (or screenshots) of the problem in action.

Assess the severity of the usability problem using the severity ratings for usability problems.

Make a recommendation based on the problem and severity.

Bring to your June 15/17 lab

A copy of the following:

  • Two clearly defined tasks for evaluation.
  • A set of selected heuristics.
  • An empty data sheet.

We will chat about your deliverables in-lab.

From June 15 to June 24

This week is for completing the heuristic evaluation.

  1. Working with your two tasks, selected heuristics, and data sheet complete the heuristic evaluation. Find 5-10 issues. An example of filling out the data sheet is provided in the table below.
Task and location in taskHeuristic broken Description of usability problemVisual exampleSeverity ratingRecommendations

"Adding a calendar item": Error occurred when selecting the 'More Options' button within the 'Edit Event' panel.

Visibility of system status.

Clicking on the 'More Options' button suggests that more options should appear, but instead the page refreshes and provides no indication to the user that it did anything.
The 'Edit Event' modal from Canvas with the 'More Options' button at the bottom next to the 'Submit' button

Clicking on 'More Options' in this modal resulted in the page refreshing back to the calendar view.

Usability catastrophe (4).

The action suggested by the button is not even performed as the page refreshes with no ability to edit the new event with 'More options'. The action should happen as described and ideally in the same 'Edit Event' panel to assist with efficiency of use.

  1. Once done the evaluation, select what you believe is your most important problem found. Be prepared to explain why you believe this to be the most important problem during critiques.
Bring to your June 22/24 lab

A copy of the following:

  • Your completed heuristic evaluation data sheet.
  • Your explanation for why one of the problems is most important.

We will chat about your deliverables in-lab.

From June 22 to July 1 July 4

This week is for completing a report on the heuristic problems.

  1. Assemble all project materials (from June 8 to June 29/July 1 July 2/July 4) into a document that is designed for easy and concise understanding. The document should include:
    • Background: A brief overview of what you were evaluating and why.
    • Methodology: Explain the tasks you chose, why you chose them, and the heuristics used in the evaluation.
    • Results: Summarize the findings of the evaluation. This should not be a direct copy of the data sheet and should instead focus on collecting and connecting issues.
    • Recommendations: Describe changes that should be made to correct the errors identified in the results and why they should be made.
    • Appendices: All the raw data including original data sheets and summaries from the heuristic evaluation.
  2. Write this document as if it is intended for a non-designer (such as management). The format (PDF, website, etc.) is of your choosing but should demonstrate a refined and well-designed document.

You are allowed to improve your earlier weekly deliverables for your final submission.

Grading rubric

Your project will be graded on the following criteria:

A B C D/F

Use of supporting artifacts (3 points): 'Do I have to guess what is referred to? (in background, methods, results)'
  • Uses artifacts — images, quotes, process samples, etc — in combination with the text that make the process very clear/evident.
  • Directs reader to appendices as needed.
  • Uses artifacts — images, quotes, process samples, etc — that show the process.
  • Directs reader to appendices as needed.
  • Uses artifacts — images, quotes, process samples, etc — that show some of the process.
  • Directs reader to appendices as needed.
  • Uses artifacts — images, quotes, process samples, etc — that show little of the process.
  • Does not direct to appendices as needed.

Reasonably concise writing (6 points): 'Can I follow the process? Does it stay on topic?'

The writing presents a clear narrative from beginning to end of the document without extra, un-related materials.

Each section of the document presents a clear narrative without extra, un-related materials.

Each section of the document presents a clear narrative with some extra, un-related materials.

The document presents an unclear narrative with many extra, un-related materials.

Effective argumentation (6 points): 'Am I convinced? (by recommendations)'

The recommendations use artifacts effectively in combination with written arguments to make a strong case for why a particular direction or conclusion is appropriate.

The recommendations use written arguments to make a strong case for why a particular direction or conclusion is appropriate.

The recommendations use written arguments that do not make a strong case for why a particular direction or conclusion is appropriate due to gaps in knowledge or the rationale.

The recommendations use written arguments that do not explain why a particular direction or conclusion is appropriate.

Audience (3 points): 'Would a client understand this?'

Document uses a language understandable by a lay — naive or new-to-the-topic — audience.

Document uses a language understandable by a professional or design audience.

Document uses a language understandable by a design audience.

Document uses a language not understandable by a design audience.

Polish (2 points): 'Would a client read this?'

  • Document's design — layout, type, content, interaction (if used) — allows for easy reading.
  • Document is proofread and edited with few errors. It consistently follows the rules of Standard English.
  • Document's design — layout, type, content, interaction (if used) — leads to some confusion when reading.
  • Document is proofread and edited with few errors. It consistently follows the rules of Standard English.
  • Document's design — layout, type, content, interaction (if used) — leads to lots of confusion when reading.
  • Document contains many errors that interfere with meaning. It generally does not follow the rules of Standard English.

Final submission requirements (June 29/July 1 July 2/July 4)

Final submission deadline bumped back due to Vancouver heatwave.

The final submission for P2 is a collection of all weeks of the project into a document that is designed for easy and concise understanding by a non-designer (i.e. manager). The format (PDF, website, etc.) is of your choosing but should demonstrate a refined and well-designed document.

Your project submission is due to Canvas before your June 29/July 1 July 2/July 4 lab.

Please make sure double-check all your submitted files and URLs to ensure they can be opened. We want to avoid late or problematic submission penalties whenever possible.