Administrivia  Review Deliverable 2 –Overview (audience) –Excellent additions  User Goals  Usability Goals  User Group (who are you designing for?)

Slides:



Advertisements
Similar presentations
Agile Usability Testing Methods
Advertisements

CS305: HCI in SW Development Evaluation (Return to…)
Each individual person is working on a GUI subset. The goal is for you to create screens for three specific tasks your user will do from your GUI Project.
IS214 Recap. IS214 Understanding Users and Their Work –User and task analysis –Ethnographic methods –Site visits: observation, interviews –Contextual.
IS 214 Needs Assessment and Evaluation of Information Systems Managing Usability © Copyright 2001 Kevin McBride.
Part 4: Evaluation Days 25, 27, 29, 31 Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what,
213: User Interface Design & Development Professor: Tapan Parikh TA: Eun Kyoung Choe
Midterm Exam Review IS 485, Professor Matt Thatcher.
Heuristics  Basis  Evaluators –Qualifications –Training  Preparation –Scenario  Results –List of problems –Severity –Group synthesis.
Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Each spokesperson.
Administrivia  Feedback on first Deliverable –Audience: Management –Requirements  Description of the system (what it is, how it works)  Define user.
Part 4: Evaluation Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what, where, and when Chapter.
Administrivia EPost and Portfolio EPost and Portfolio Analysis of Design process Analysis of Design process.
Inspection Methods. Inspection methods Heuristic evaluation Guidelines review Consistency inspections Standards inspections Features inspection Cognitive.
Design Process …and the project.
Analysis of Design Process Lewis/Gould 1981 Study TC518 W ’06 Students Early Focus on Users 62%58% Empirical Measurement 40%69% Iterative Design 20%62%
Warm-up, Free-write Task: –On a blank sheet of paper, begin to write down what you know about the users of your product, the tasks they use the product.
Feedback from Mid-term Evaluation  What could better help you learn –Assignments  Assignments are too vague (expectations are not clear)  Unsure about.
Syllabus – Weekly schedule. Project Sharing – Exercise 3 Team level discussion Teams share results of contextual inquiry Note: Jennifer & Anita circulate,
Elicitation Methods Information types Information types Information Information Internal Perspectives Internal Perspectives Behavior Behavior Facts Facts.
Mid-Term Exam Review IS 485, Professor Matt Thatcher.
Damian Gordon.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five.
Review an existing website Usability in Design. to begin with.. Meeting Organization’s objectives and your Usability goals Meeting User’s Needs Complying.
Y. Rong June 2008 Modified in Feb  Industrial leaders  Initiation of a project (any project)  Innovative way to do: NABC ◦ Need analysis ◦ Approach.
Usability Methods: Cognitive Walkthrough & Heuristic Evaluation Dr. Dania Bilal IS 588 Spring 2008 Dr. D. Bilal.
ZEIT2301- Design Studios and Design Critiques School of Engineering and Information Technology Dr Kathryn Merrick Bldg 16, Rm 212 (Thursdays.
#17 - Involve Users in the Development Model of Multinational Corporations - Is it worth it? Experience Report IRCSE '08: IDT Workshop Friday 31 October.
Presentation: Techniques for user involvement ITAPC1.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
Part 1-Intro; Part 2- Req; Part 3- Design  Chapter 20 Why evaluate the usability of user interface designs?  Chapter 21 Deciding on what you need to.
Human Computer Interaction
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
What is Usability? Usability Is a measure of how easy it is to use something: –How easy will the use of the software be for a typical user to understand,
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
SWE 4324 UCD - WEB A FINAL VERSION Evaluation of a feature Note about Webs – Webs are the interactive class you must participate for a satisfactory understanding.
Usability Testing Chapter 6. Reliability Can you repeat the test?
1 ISE 412 Usability Testing Purpose of usability testing:  evaluate users’ experience with the interface  identify specific problems in the interface.
Y ASER G HANAM Heuristic Evaluation. Roadmap Introduction How it works Advantages Shortcomings Conclusion Exercise.
Introduction to Web Authoring Ellen Cushman Class mtg. #21.
User Interface Design & Usability for the Web Card Sorting You should now have a basic idea as to content requirements, functional requirements and user.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
Project Sharing  Team discussions (15 minutes) –Share results of your work on the Project Scope Proposal –Discuss your choice of methods and results –Prepare.
Administrivia  Final Exam –Due Date – Thursday, March 17 –Q & A  Deliverable 2 –Q & A.
Mid-Term Evaluation  Course and Instructor evaluation  Jennie Dorman.
Usability Evaluation, part 2. REVIEW: A Test Plan Checklist, 1 Goal of the test? Specific questions you want to answer? Who will be the experimenter?
Usability Engineering Dr. Dania Bilal IS 592 Spring 2005.
CS5714 Usability Engineering Usability Inspection Copyright © 2003 H. Rex Hartson and Deborah Hix.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #15.
By Godwin Alemoh. What is usability testing Usability testing: is the process of carrying out experiments to find out specific information about a design.
June 5, 2007Mohamad Eid Usability Testing Chapter 8.
Introduction to Evaluation without Users. Where are you at with readings? Should have read –TCUID, Chapter 4 For Next Week –Two Papers on Heuristics from.
Usability Heuristics Avoid common design pitfalls by following principles of good design Nielsen proposes 10 heuristics, others propose more or less. Inspect.
Administrivia  Feedback from the mid-term evaluation  Insights from project proposal.
Steps in Planning a Usability Test Determine Who We Want To Test Determine What We Want to Test Determine Our Test Metrics Write or Choose our Scenario.
Usability Engineering Dr. Dania Bilal IS 587 Fall 2007.
Computer/Human Interaction Fall 2015 Northeastern University1 Name of Interface Tagline if you have one Team member names and schools/years Team member.
Evaluation / Usability. ImplementDesignAnalysisEvaluateDevelop ADDIE.
1 Usability Analysis n Why Analyze n Types of Usability Analysis n Human Subjects Research n Project 3: Heuristic Evaluation.
BUS 660 Entire Course (2 Sets) FOR MORE CLASSES VISIT This Tutorial contains 2 Sets of Papers for each Assignment (Check Details Below)
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #20.
Getting Prepared for the Webinar
“It was years after we had taken usability to guide us that it was said by some other companies that they could not afford to employ a usability specialist.
Administrivia Final Exam Deliverable 3 Feedback on Heuristic Eval
Usability Evaluation, part 2
Katherine Prentice, MSIS Richard Usatine, MD
SY DE 542 User Testing March 7, 2005 R. Chow
Administrivia Issues – EPost and Portfolio
Usability Techniques Lecture 13.
A Fundamental Challenge
Introduction to Web Authoring
Presentation transcript:

Administrivia  Review Deliverable 2 –Overview (audience) –Excellent additions  User Goals  Usability Goals  User Group (who are you designing for?)  Success Criteria

Administrivia  Review Deliverable 2 (continued) –Rationale  Reasoning for problem is separate from reasoning for solution  Principles differ from guidelines  Dumas & Redish (p. 53) –Principle: broad statements (or goals) usually based on research about how people learn and work –Guideline: how to achieve specific goals for different users, environments and technologies  Explain how you are applying the principle in your solution and support the principle with guidelines or findings or study results  Barnum: inspection methods are generally better at finding problems than determining the appropriate improvement

Administrivia  Review Deliverable 2 (continued) –Business Case  Be specific about the return on investment, business goals and revenue/cost. What measurable difference will it make to the company? For example, how do they measure success today and how much might that measure be expected to improve?  Too general: increase usage, increase users, increase sales, improve satisfaction, contain expenses, improving usability

Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Volunteers to share especially challenging or surprising insights –Lessons learned

Where are we in the UCD process?

Usability Testing  Test early and often, not just at the end  Evaluation Technique –Real users –Real tasks –Observe and Record  Two types –Discover problems (to improve/form the product)  Think-a-loud (typical) –Summarize the usability (measure against goals)  Usability goals  Compared to other testing –Functional Test –QA Test –Beta Test

Usability Testing  Preparation –Choose frequent and critical tasks –Tasks related to concerns you have –Develop test script  Select Participants –Screening criteria (create gaps to separate) –Minimum of 3 participants per user group  3-5 (Nielsen)  8 minimum for a summative test  Results –List of problems –Severity –Organize & Prioritize

Usability Testing  Measurable usability goals –How many of what type of user will be able to do what within what measure? –80% of Novice web site users will be able to Contact Us in less than 25 seconds. –What is a reasonable measure?  Consider how many test participants you have  How confident do you want to be in the results?  Bias –Inappropriate instructions or assistance –Leading questions –Subtle feedback (positive or negative) –Confirming understanding of the task

Usability Testing  Introduction –What to expect (how long?) –Work as you would under normal circumstances –Ethics  Voluntary (free to stop or leave at any time)  Permission to record  An evaluation of the software not of their abilities  Interaction with participants –Think-aloud –Handling questions (rhetorical) –Assistance  Issues –How do you know when a task is done? –Time limit

Usability Testing  Limitations –Only evaluates part of the interface –Scripted tasks –Not a true real-world situation –May not reveal problems of proficient users –Even with think-a-loud, intent may not be clear

Usability Testing  Prepare –Avoid bias –Introduction –Develop test script –Take notes –Take measures –Prompt participant (if necessary)

Activity – Usability Test  Form Groups –Individual work – choose tasks –Individual work – define measurable goals –Individual work – identify measures –Group work – share and discuss

Activity – Usability Test Discussion Topics  What are important decisions?  What types of variations could you imagine?  What are the complexities– what makes it hard?  What factors are important for achieving success with this method?

Discussion of Readings  Facilitate class discussion of topics / ideas / themes garnered from the online discussion, related to assigned readings. –Discussion Leaders 1. Sarah Sosiak 2. Ona Anicello 3. Astrid Lipke 4. Monica Risse

Project Exercise Usability Study  Design and execute a usability study of your prototype with 3 users.  Prepare a one page description summarizing –Method for testing –Results of the study –Potential implications for redesign  Bring copies of the exercise to class (one copy for each member of the team, one copy for the instructor) and also post it to your design portfolio.  Due next Thursday

Looking back / Looking ahead Where we’ve been  Topics – Readings and discussion –What is UCD? –Collecting and summarizing info about users, tasks and context –Problem definition –Design  Project –Insights about users, tasks, and contextual issues –Actual data from observing real users –Problem definition –Proposal –Design Where we’re going  Redesign: –Represent design –Support and justify  Readings: –Cost-justifying usability –Justifying user visits –Benefits  Upcoming Exercises: –Final Design Solution  Issue Statement: A reminder 1. Jaana Linsenmayer 2. Kris Anderson 3. Carol Taylor