Top Banner
Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review
14

Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Dec 19, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Before usability

CS 147: Intro to HCIDan Maynes-Aminzade

After 1st Usability Review

Page 2: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

After 2nd Usability Review

After Usability

Page 3: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

After feedback from Don Norman(which cost me $25,000)

Page 4: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Plans for Today

• Assignment 2 discussion in small groups

• Group discussion of lessons learned from Assignment 2

• Quick summary of project proposals + discussion

• Terminology recap

• Form groups for projects

Page 5: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Terminology of InteractiveSystem Design

• Affordances

• Constraints

• Conceptual Models

• Mappings

• Visibility

• Feedback

Page 6: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Affordances

• Attribute of an object that allows people to know how to use it

Page 7: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Constraints

• Restricting interaction to reduce errors

Page 8: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Conceptual Model

• A set of ideas about how an interactive system behaves

vs.

Page 9: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Mapping

• Relationship between controls and their effects on the world

Page 10: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Visibility

• Making it obvious which actions are available

Page 11: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Feedback

• Send information about what is happening back to the user

Page 12: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Usability Breakdown

• My action causes something I did not expect or want

• I want to do something, and cannot figure out how

Page 13: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Assignment 1 Grading Criteria

• Good– Chose an appropriate interactive interface, and

described its problems in terms of the principles in the readings

– Characterized the breakdown as described in the assignment: what was tried, what was expected, what happened

– Described the issue in specific terms, using terminology and principles from the readings

– Suggested an alternative design that solved the problem and described how it was better grounded in the general principles

Page 14: Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.

Assignment 1 Grading Criteria

• Bad– Chose a technology problem rather than a design

problem (e.g. “system crashed” or “device was broken”)

– Copied one of the examples from the reading– Explained in vague terms (e.g. “design was bad”)– Didn’t offer an alternative design– Didn’t show evidence of doing the reading (didn’t use

the appropriate principles, or applied them incorrectly)