CS147-2009-DesignReviews

CS147-2009-DesignReviews - stanford hci group http:// cs...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: stanford hci group http:// cs 147.stanford.edu Scott Klemmer Autumn 2009 Design Reviews Thursday, October 15, 2009 Genres of assessment Automated Usability measures computed by software Empirical Usability assesses by testing with real users Formal Models and formulas to calculate measures Inspection Based on heuristics, skills, and experience of evaluators Thursday, October 15, 2009 When to do a design review? Before user testing. Don't waste users on the small stuff. An expert usability inspection will identify minor issues that can be resolved before testing, allowing users to focus on the big issues. Before redesigning. Don't throw out the baby with the bathwater. An expert usability inspection will expose the elements of your existing design that work and should be retained (not just the bad stuff). When you know there are problems, but you need evidence. Perhaps you've received complaints from customers or found yourself stumbling around your own site. An expert usability inspection can help you articulate problems and provide you with the ammunition to build a business case for redesign. Before release. [Smooth] off the rough edges before go-live. Source: http://www.etre.com/usability/inspection Thursday, October 15, 2009 Begin Review with a Clear Goal Thursday, October 15, 2009 Heuristic Evaluation Developed by Jakob Nielsen Helps find usability problems in a UI design Small set (3-5) of evaluators examine UI independently check for compliance with usability principles (heuristics) different evaluators will find different problems evaluators only communicate afterwards findings are then aggregated Can perform on working UI or on sketches Thursday, October 15, 2009 Visibility of System Status Keep users informed about what is going on Example: pay attention to response time 0.1 sec: no special indicators needed, why? 1.0 sec: user tends to lose track of data 10 sec: max. duration if user to stay focused on action for longer delays, use percent-done progress bars searching database for matches Thursday, October 15, 2009 Visibility of System Status Thursday, October 15, 2009 Match between system & world...
View Full Document

This note was uploaded on 01/12/2010 for the course CS 147 at Stanford.

Page1 / 37

CS147-2009-DesignReviews - stanford hci group http:// cs...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online