1st Year Cohort programs at SFU Surrey - IAT 432: Design Evaluation

More documents

Recommendations

Info

… and speak to industry… • Most large IT companies have internal Usability teams – Test product under iter<strong>at</strong>ive development – Produce list of Usability issues to be fixed in the next dev round 6
… and they noticed something very, very wrong. • Blind usability – “gives meaningless and trivial results” – Misdirects or prem<strong>at</strong>urely kills future design directions 7
Page 1 and 2: IAT 432 Week 11 Usability Evaluatio
Page 3 and 4: Saul Greenberg • Full Professor i
Page 5: The would attend conferences… •
Page 9 and 10: What’s wrong with Usability • U
Page 11 and 12: • Ideal HCI science: Usability is
Page 13 and 14: Most Usability methods try to be ob
Page 15 and 16: • Designer-as-assessor Objectivit
Page 17: Usability devalues early-stage desi
Page 20 and 21: Usability devalues early-stage desi
Page 22 and 23: Usability is a poor predictor for c
Page 24 and 25: If Usability is so harmful, why do
Page 26 and 27: Other Approaches to Design and Eval
Page 28 and 29: • Due Wednesday, April 11 th Assi
Page 30: Lab • This week’s lab cancelled

1st Year Cohort programs at SFU Surrey - IAT 432: Design Evaluation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?