Customer: Rosalva Gallardo Team members: Susan Lin Buda Chiou Jim Milewski Marcos Mercado November 23, 2010.

Slides:



Advertisements
Similar presentations
The Usability Test Process: Steps, tips, and more! Dr. Jennifer L. Bowie For Digital Rhetoric.
Advertisements

Customer: Rosalva Gallardo Team members: Susan Lin Buda Chiou Jim Milewski Marcos Mercado October 19, 2010.
Data gathering. Overview Four key issues of data gathering Data recording Interviews Questionnaires Observation Choosing and combining techniques.
Deciding How to Measure Usability How to conduct successful user requirements activity?
The Software Quality Star: A conceptual model for the software quality curriculum Ronan Fitzpatrick School of Computing, Dublin Institute of Technology,
Data gathering.
CS CS 5150 Software Engineering Lecture 12 Usability 2.
1 Overview of Usability Testing CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology April 19, 2007.
Energy Information Administration Usability Testing Colleen Blessing.
Project 4: User interface for logging food intake and activities Thanh Le Christine Liang Warren Trinh Muhammad Zaman.
Evaluation of usability tests. Why evaluate? 1. choose the most suitable data- collection techniques 2. identify methodological strength and weaknesses.
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.
Usable Privacy and Security Carnegie Mellon University Spring 2008 Lorrie Cranor 1 Designing user studies February.
1 CS 430 / INFO 430 Information Retrieval Lecture 24 Usability 2.
Reference and Instruction Automated Statistics Gathering and Reporting System Members: Patrick Chen (pyc7) Soo-Yung Cho (sc444) Gregg Herlacher (gah24)
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Testing and Modeling Users Kristina Winbladh & Ramzi Nasr.
Usability Driven GUI Design Portal as a Gateway to Intranet Resources Matthew Winkel Usability Analyst.
Web 2.0 Testing and Marketing E-engagement capacity enhancement for NGOs HKU ExCEL3.
Preparing a User Test Alfred Kobsa University of California, Irvine.
Usability Testing – Part II Teppo Räisänen
Joy Hamerman Matsumoto.  St Jude Medical Cardiac Rhythm Management Division manufactures implantable cardiac devices ◦ Pacemakers ◦ Implanted defibrillators.
SUNIL GAHLAWAT LU GAN MIYA SYLVESTER YIRAN WANG Usability and Utility of TopicLens a Visualization System for the Exploration of Topic Models.
1 SWE 513: Software Engineering Usability II. 2 Usability and Cost Good usability may be expensive in hardware or special software development User interface.
TECHNICAL DOCUMENTATIONPARTNERS DOWNLOAD DATA Download water quality data in MS Excel, CSV, TSV, and KML formats. Learn how to use the portal and data.
Interim Presentation Group 4 - May 14th, 2012 Langson Library Redesign.
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.
Presented by Abirami Poonkundran.  Introduction  Current Work  Current Tools  Solution  Tesseract  Tesseract Usage Scenarios  Information Flow.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Data gathering. Overview Four key issues of data gathering Data recording Interviews Questionnaires Observation Choosing and combining techniques.
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.
End HomeWelcome! The Software Development Process.
EasyChair Reviewer sign up and bidding Art Hsieh Jean Huang Norik Davtian Ryan Nissenbaum.
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
Software Engineering Chapter 16 User Interface Design Ku-Yaw Chang Assistant Professor Department of Computer Science and Information.
Evaluation Paradigms & Techniques IS 588 Spring 2008 Dr. D. Bilal.
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
Project 3 Cookie Cutters Kevin Huynh Sean Tsusaki Jordaniel Wolk.
Database A database program is a piece of software to organize and sort information. It creates an electronic list of information that can be sorted very.
1 A usable DSpace with extra funtionalities Ben Bosman, Lieven Droogmans, Bob Vrancken Joris Klerkx, Michael Meire, Erik Duval K.U.Leuven, Belgium
Usability Testing Chapter 6. Reliability Can you repeat the test?
Usability testing: A reality check for Plain Talk A brief overview October 7, 2008 Dana Howard Botka Manager, Customer Communications, L&I Plain Talk Coordinator,
CS2003 Usability Engineering Usability Evaluation Dr Steve Love.
Team name Usability testing plan for BelleViews School of Business and Information Management Oulu University of Applied Sciences.
Usability Assessment Methods beyond Testing Chapter 7 Evaluating without users.
Introduction to Software Development. Systems Life Cycle Analysis  Collect and examine data  Analyze current system and data flow Design  Plan your.
Software Engineering User Interface Design Slide 1 User Interface Design.
ITGS Databases.
Chapter 8 Usability Specification Techniques Hix & Hartson.
Welcome to the Usability Center Tour Since 1995, the Usability Center has been a learning environment that supports and educates in the process of usability.
Towards understanding programs through wear-based filtering Robert DeLine Amir Khella Mary Czerwinski George Robertson Microsoft Corporation SoftVis 2005.
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?
AVI/Psych 358/IE 340: Human Factors Data Gathering October 3, 2008.
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.
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.
UCI Library Website Chris Lee Archana Vaidyanathan Duncan Tsai Karen Quan.
EasyChair Reviews, comments and meta-reviews Interim Presentation Team: Super-Chairs Aaron Donk, Vatsal Shah, Ammar Taki El-Din, Gilberto Bardales.
Evaluation / Usability. ImplementDesignAnalysisEvaluateDevelop ADDIE.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Day 8 Usability testing.
GCE Software Systems Development
Project planning The systems life cycle.
T Project Review Group: pdm I2 Iteration
Usability Evaluation, part 2
Collaboration with Google Drive
CS 321: Human-Computer Interaction Design
RACIAL VIOLENCE ARCHIVE
Chapter 23 Deciding how to collect data
Usability Testing and Analytics Insights
Presentation transcript:

Customer: Rosalva Gallardo Team members: Susan Lin Buda Chiou Jim Milewski Marcos Mercado November 23, 2010

Primary Purpose Method Overview Usability experiments Data Collection Preliminary Results Current Status and Updated Project Plan Q&A

Does the new “treatment” interface improve the usability of the metrics?

Does the new “treatment” interface improve the usability of the metrics? Introduced sort functionality for metrics

Does the new “treatment” interface improve the usability of the metrics? Changed the presentation of the metrics

Does the new “treatment” interface improve the usability of the metrics? Included a mix of graphics and text for the “Reviews” metric

Does the new “treatment” interface improve the usability of the metrics? Introduced Reviewer’s information

Pilot test plus 15 usability experiments performed in the Hana Lab Average experiment time 1.5 hours Some experiments ran in parallel. Monetary compensation and incentive provided to accomplish tasks.

Experiments were run according to client’s Handbook for Source Code Retrieval Experiment. Welcome and study information sheet/consent Instructions to subject and general scenario Practice task with scenario 4 Experiment Tasks with scenarios and post-task questionnaires Participant’s background questionnaire Debriefing Interview

Think aloud protocol Excel file filled in while participant performed the tasks Morae recording Questionnaire after each task Debriefing interview Subject background questionnaire

Video recordings analyzed (1 video = 5.5 hours) Before and after pages highlighting some of the changes e.g. you needed to capture the observations of the participants and couldn’t really focus on how quickly they were switching between screens Seconds, Observations, Candidates

Similar trend is observed except for Reviews where we combined graphics and text Increase of Reviews usage New layout for metrics presented in text only did not alter the trend.

Original Experiment Customer goals were: Understand the strategies and information software developers use when they select a source code search result from the Web Identify the relationship among strategies, information used, and successful completion of the experiment’s tasks.

New Experiment Customer goals are: Same as in the original experiment Analyze how an enhanced GUI will influence users’ decisions on the information they use. Variants: New participants Use of an enhanced treatment GUI Use of a log mechanism to assist in the collection of experiment data related to GUI usage.

1. Implement user interface enhancements to experiment’s treatment GUI. 2. Implement an automated log mechanism to capture certain events during GUI usage. 3. Conduct new experiment 4. Analysis of results

Usability problemCustomer’s ViewTeam’s initial thoughts Users failed to quickly understand the information provided in the search results. “We argue that evaluation performance can be improved by increasing understanding of search results…” (Gallardo & Sim. “StrategiesInfoUsed_Paper _v10.pdf”, p.1. In submission to CHI’10) We believe that in order to increase understanding of search results, interface needs to be easy to understand at first glance. Sorting of results was not available to users. Allow users to sort by popularity and software quality metrics. This may help users choose the best candidate. Agree with customer

Usability problemCustomer’s ViewTeam’s initial thoughts Additional information (popularity and technical metrics) was shown to assist users in choosing the best candidate. This information was ignored or not frequently used. Surprisingly, metrics were only used 12.5%-50% of the time. Change the presentation and location of these metrics to make them more eye catching. The additional information should mix graphics and text to make it more appealing. However, it should not give a cluttered feel to the interface. IdemPerhaps the additional information was ignored because seemed irrelevant to the user. Include information about people who wrote the reviews on each candidate (one of the popularity metrics). We will perform comparative analysis of similar web sites as well as brainstorming sessions to decide what information to include.

Google Code, Koders.com, Source Forge, Ohloh

Prototypes

Number & type of users: 16 ICS students with experience in Java (13 graduate-level and 3 undergraduate). Tasks for users and questions we will ask them: CSV task: Find the best source code to read a CSV file and place the data into a list of strings. DIFF task: Find the best source code to compare two text files and show the differences. VALIDATION task: Find the best source code to validate addresses. TIMEZONE task: Find the best source code to convert date & time between different time zones.

Strategies for involving users Recruitment Use of incentives Where… Will meet them in the Hana Lab Each meeting will last hrs

ml