Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Each spokesperson.

Slides:



Advertisements
Similar presentations
References Prof. Saul Greenberg, University of Calgary, notes and articles INUSE 6.2 and RESPECT 5.3 Handbook Prof. , University of , Notes and articles.
Advertisements

+ UCD Methods For Understanding Users In Computer Science – Music application.
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.
©N. Hari Narayanan Computer Science & Software Engineering Auburn University 1 COMP 7620 Evaluation Chapter 9.
Administrivia  Review Deliverable 2 –Overview (audience) –Excellent additions  User Goals  Usability Goals  User Group (who are you designing for?)
Think-aloud usability experiments or concurrent verbal accounts Judy Kay CHAI: Computer human adapted interaction research group School of Information.
Midterm Exam Review IS 485, Professor Matt Thatcher.
Heuristics  Basis  Evaluators –Qualifications –Training  Preparation –Scenario  Results –List of problems –Severity –Group synthesis.
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.
Recap of IS214. Placing this course in context Creating information technology that helps people accomplish their goals, make the experience effective,
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%
What is a good length of string? –Depends on its use How do you design a good length of string? –Can be determined by a process What is a good user interface?
Usability 2004 J T Burns1 Usability & Usability Engineering.
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.
QUALITY ASSURANCE PROJECT Conducting Effective Meetings The purpose of this module is to enhance participants’ knowledge and skill in observing team meetings.
Usability Methods: Cognitive Walkthrough & Heuristic Evaluation Dr. Dania Bilal IS 588 Spring 2008 Dr. D. Bilal.
1 Commissioned by PAMSA and German Technical Co-Operation National Certificate in Paper & Pulp Manufacturing NQF Level 3 Lead a team, plan, organise and.
Requirements-definition User analysis
#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.
Planning and Writing Your Documents Chapter 6. Start of the Project Start the project by knowing the software you will write about, but you should try.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
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.
Usability Testing Chapter 6. Reliability Can you repeat the test?
Work package 2: User analysis and usability testing Responsible partner: Danish Data Archives WP leader: Anne Sofie Fink, DDA.
1 ISE 412 Usability Testing Purpose of usability testing:  evaluate users’ experience with the interface  identify specific problems in the interface.
COMP5047 Pervasive Computing: 2012 Think-aloud usability experiments or concurrent verbal accounts Judy Kay CHAI: Computer human adapted interaction research.
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.
Creating User Interfaces Review midterm. Work on User Observation studies Homework: Spring break! Use opportunity to work on user observation study!
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?
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #15.
ITCS 6265 Details on Project & Paper Presentation.
By Godwin Alemoh. What is usability testing Usability testing: is the process of carrying out experiments to find out specific information about a design.
Administrivia  Feedback from the mid-term evaluation  Insights from project proposal.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Ethnographic Interviews: Interviewing and Observing Users Project: Investigating Sakai 3 Capabilities to Support Learning Activities Jacqueline Mai 10/20/09.
Usability Engineering Dr. Dania Bilal IS 587 Fall 2007.
Evaluation / Usability. ImplementDesignAnalysisEvaluateDevelop ADDIE.
ICAJ/PAB - Improving Compliance with International Standards on Auditing Planning an audit of financial statements 19 July 2014.
1 Usability Analysis n Why Analyze n Types of Usability Analysis n Human Subjects Research n Project 3: Heuristic Evaluation.
School practice Dragica Trivic. FINDINGS AND RECOMMENDATIONS FROM TEMPUS MASTS CONFERENCE in Novi Sad Practice should be seen as an integral part of the.
Team Building Project Design and Development Storyboard 1.
true potential An Introduction to the First Line Manager Programme’s CMI Qualifications.
School of Engineering and Information and Communication Technology KIT305/607 Mobile Application Development Week 7: Usability (think-alouds) Dr. Rainer.
“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
SY DE 542 User Testing March 7, 2005 R. Chow
Administrivia Issues – EPost and Portfolio
A Fundamental Challenge
Introduction to Web Authoring
Presentation transcript:

Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Each spokesperson share  One challenge  One surprise  One lesson learned

Discussion of Readings  Facilitate class discussion of topics / ideas / themes garnered from the online discussion, related to assigned readings. –Discussion Leaders 1. Danny Kelly 2. Anastasia Paushkina 3. Kate Forster

Topic H: User-centered evaluations: Usability testing Driving Questions:  What methods can a UCD designer draw on in order to evaluate their solutions? What in entailed in using these methods and presenting the results? Who are the consumers of the evaluation results?  Why is empirical evaluation of design such a critical aspect of user-centered design?  How can UCD designers ensure that evaluation activities are incorporated early into the design 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 Activity (Role Play)  Practice –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 – Conduct usability study –Swap roles –Share results and discuss with class

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?

Project Exercise Usability Study  Design and execute a usability study of your prototype with preferably 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. Rob MacDonald 2. Sammy Woogerd 3. Tiffany Fehr