ITM 734 Requirements Gathering & Task Analysis – Part 2 of 5 Cindy Corritore This material has been adapted from Georgia Tech HCI faculty,

Slides:



Advertisements
Similar presentations
Performance Assessment
Advertisements

Collaborating By: Mandi Schumacher.
Evaluation What, How and Why Bother?.
Chapter 9 User-centered approaches to interaction design By: Sarah Obenhaus Ray Evans Nate Lynch.
Collecting data Chapter 5
Chapter 7 Data Gathering 1.
Data gathering. Overview Four key issues of data gathering Data recording Interviews Questionnaires Observation Choosing and combining techniques.
Slide 1 Systems Analysis and Design with UML Version 2.0 Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination John Wiley.
6.811 / PPAT: Principles and Practice of Assistive Technology Wednesday, 16 October 2013 Prof. Rob Miller Today: User Testing.
CS305: HCI in SW Development Evaluation (Return to…)
Requirements Gathering & Task Analysis – Part 2 of 5 Why, What and How – Methods This material has been developed by Georgia Tech HCI faculty, and continues.
Ethnography A ‘How to’ Guide By Carl Hudson Outline Introduction Introduction What is Ethnography? What is Ethnography? Who invented it? Who invented.
Data gathering.
Requirements Gathering and Expressing. Agenda Questions? Project update Requirements continued Project group formation.
Design How do we come up with new (good) designs for interactive systems? Why is it so difficult?
Requirements: Gathering. Why  To understand what we are going to be doing  We build systems for others, not for ourselves  Requirements definition:
Observing users.
Types of interview used in research
Requirements Gathering Methods for Requirements Gathering and Requirements Gathering.
QUALITY ASSURANCE PROJECT Conducting Effective Meetings The purpose of this module is to enhance participants’ knowledge and skill in observing team meetings.
1 © 2009 University of Wisconsin-Extension, Cooperative Extension, Program Development and Evaluation Getting started with evaluation.
CSCI 4163 / CSCI 6904 – Winter Housekeeping  Write a question/comment about today’s reading on the whiteboard (chocolate!)  Make sure to sign.
Interviews Stephanie Smale. Overview o Introduction o Interviews and their pros and cons o Preparing for an interview o Interview Elements: o Questions.
User Interface Evaluation Usability Inquiry Methods
Fall 2002CS/PSY Task Analysis Analyzing and describing how people do their jobs/work  -> Go to their environment Examine users’ tasks to better.
Requirements Gathering. Why are requirements important? To understand what we are going to be doing We build systems for others, not for ourselves Requirements.
Chapter 11: An Evaluation Framework Group 4: Tony Masi, Sam Esswein, Brian Rood, & Chris Troisi.
CSCI 4163/6904, summer Quiz  Multiple choice  Answer individually - pass in  Then class discussion.
Data gathering. Overview Four key issues of data gathering Data recording Interviews Questionnaires Observation Choosing and combining techniques.
Breaking Down the Prompt
Behavioral Research Chapter 6-Observing Behavior.
Gathering User Data IS 588 Dr. Dania Bilal Spring 2008.
Interpretive Evaluation Agenda Simple user modeling Interpretive Evaluation - Motivation - Methods Ethnography Fitt’s Law.
Human Computer Interaction
©2010 John Wiley and Sons Chapter 6 Research Methods in Human-Computer Interaction Chapter 6- Diaries.
Inquiry and the IB. Stuents do not learn by doing. on what they have done. Rather, they learn by and.
Requirements, cont. …along with Ethics. Agenda Questions? Data gathering techniques Requirements expressing Ethics.
LOOKING FOR EVIDENCE? A CASE FOR THE CASE STUDY DR. GURU NAGARAJAN DR. SARA BHATTACHARJI.
Allison Bloodworth, Senior User Interaction Designer, Educational Technology Services, University of California - Berkeley October 22, 2015 User Needs.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Interview Techniques (Hand-in partner preferences) Thursday In-class Interviewing.
Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.
Facilitating Multi Stakeholder Processes and Social Learning Herman Brouwer / Karèn Verhoosel Centre for Development Innovation Semi structured.
Chapter 15 Qualitative Data Collection Gay, Mills, and Airasian
Ways of Collecting Information Interviews Questionnaires Ethnography Books and leaflets in the organization Joint Application Design Prototyping.
Communicating Culture interviewing. Interviewing: Definition  Interviewing is a meeting of two persons to exchange information and ideas through questions.
CSCI 4163 / CSCI 6904 – Winter Housekeeping  Clarification about due date for reading comments/questions  Skills sheet  Active listening handout.
Task Analysis Overview, utility Types of task analysis Sources and use.
Requirements Gathering CS 561. Where do Requirements Come From? Handed to you (?) Dialogue with – Customer – User Are these always the same? Are these.
Identifying needs and establishing requirements Data gathering for requirements.
AVI/Psych 358/IE 340: Human Factors Data Gathering October 6, 2008.
AVI/Psych 358/IE 340: Human Factors Data Gathering October 3, 2008.
4. Marketing research After carefully studying this chapter, you should be able to: Define marketing research; Identify and explain the major forms of.
Requirements Gathering & Task Analysis – Part 2 of 5 Why, What and How – Methods This material has been developed by Georgia Tech HCI faculty, and continues.
By: Dalila Ochoa Mary S Garcia
Understanding User's Work Ethnography The systematic study and documentation of human activity without imposing a prior interpretation on it via immersion.
Paper III Qualitative research methodology.  Qualitative research is designed to reveal a specific target audience’s range of behavior and the perceptions.
Data gathering (Chapter 7 Interaction Design Text)
Today Discussion Follow-Up Interview Techniques Next time Interview Techniques: Examples Work Modeling CD Ch.s 5, 6, & 7 CS 321 Human-Computer Interaction.
Unit 11: Use observation, assessment and planning
May 24, / Questionnaires... a. are a quick and easy way to gather information b. are only good for collecting qualitative data c. are.
Continuous Improvement. Start Simple and Continually Improve E.g., Gmail Labels 1.
Teaching Children About Food Safety Food Safety Professional Development for Early Childhood Educators.
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
Cooper Goal-Directed Design: Practice Session Dr. Cindy Corritore Creighton University ITM 734 Fall 2005.
A supported model of decision- making: The starting point: The starting point is not a test of capacity, but the presumption that every human being is.
From: A. Cooper et al.: About Face Andreas Rudin
CHAPTER OVERVIEW The Case Study Ethnographic Research
Lecture3 Data Gathering 1.
Interpretive Evaluation
CHAPTER OVERVIEW The Case Study Ethnographic Research
Presentation transcript:

ITM 734 Requirements Gathering & Task Analysis – Part 2 of 5 Cindy Corritore This material has been adapted from Georgia Tech HCI faculty, and continues to evolve. Why, What and How – Methods

Introduction to HCI How – Some (Not All) User & Task Analysis Methods 1. Ethnography - learn by immersion/doing 2. Observation - thinking out loud 3. Cooperative Evaluation 4. Interviews 5. Questionnaires 6. Focus groups 7. Study Documentation 8. Look at competitive products

Introduction to HCI Formative & Summative Evaluation Formative evaluation  Conducting this process to help guide the formation (ie, design) of a UI Summative Evaluation  Conducting this process to help summarize (sum up) the effectiveness of an existing or developmental UI Many of the user & task analysis techniques can be used for both formative and summative evaluation  Our focus right now is on formative evaluation  Will revisit some of the methods again later

Introduction to HCI 1. Ethnography Deeply contextual study Immerse oneself in situation you want to learn about (has anthropological and sociological roots)  Observing people in their cultural context Behavior is meaningful only in context

Introduction to HCI 1. Ethnographic Objectives Understanding the user  Understand goals and values  Understand individual’s or group’s interactions within a culture  Try to make tacit domain knowledge explicit in an unbiased fashion  For UI designers: improve system by finding problems in way it is currently being used

Introduction to HCI 1. Ethnography: In the Field In person observation Audio/video recording Interviews, interaction “Wallow in the data”

Introduction to HCI 1. Ethnography: Observation is Key Carefully observe everything about users and their environment Think of describing it to someone who has never seen this activity before What users say is important, so are non- verbal details

Introduction to HCI 1. Ethnography: Observations Things of interest to evaluator  Structure and language used in work  Individual and group actions  Culture affecting work  Explicit and implicit aspects of work Example: Office work environment  Business practices, rooms, artifacts, work standards, relationships between workers, managers, …

Introduction to HCI 1. Ethnography: Interviews Important Have a question plan, but keep interview open to different directions Be specific Create interpretations with users  Be sure to use their terminology At end, query “What should I have asked?” Record interviews Do retrospective if can’t see it happen

Introduction to HCI Rose et al ‘95 1. Ethnography Steps 1.1. Preparation  Understand organization policies and work culture  Familiarize yourself with system and its history  Set initial goals (focus) and prepare questions  Gain access and permission to observe & interview  Identify target users (roles) with initial interviews/information

Introduction to HCI 1. Ethnography Steps 1.2. Field study  Establish rapport with users  Observe/interview users in workplace and collect all different forms of data (lots of video is very common)  Do it (the work)  Follow any leads that emerge from visits  Record the visits (stop when repeat)

Introduction to HCI 1. Ethnography Steps 1.3. Analysis  Compile collected data in numerical, textual and multimedia databases  Quantify data and compile statistics  Reduce and interpret data  Refine goals and process used  Leave a trail (of original supporting data)

Introduction to HCI 1. Ethnography Steps 1.4. Reporting  Consider multiple audiences and goals  Prepare a report and present findings

Introduction to HCI 1. Ethnography Analysis: Affinity Diagram Write down each quote/observation on a slip of paper Put up on board Invite stakeholders, designers, etc. Coalesce items that have affinity  If they are saying similar things about an issue Give names to different groups (colors too) Continue grouping subgroups A hierarchy will be formed Try it, you’ll like it See pg

Introduction to HCI

1. Why is Ethnography Useful? Can help designer gain a rich and true assessment of user needs  Help to define requirements Uncovers true nature of user’s job  Discovers things that are outside of job description or documentation Open-ended and unbiased nature promotes discovery  Empirical study and task analysis are more formal – ethnography may yield more unexpected revelations

Introduction to HCI 1. Ethnography: Types of Findings Can be both  Qualitative –Observe trends, habits, patterns, …  Quantitative –How often was something done, what per cent of the time did something occur, how many different …

Introduction to HCI 1. Ethnography: Drawbacks Time required  Can take weeks or months for large systems Scale  Most use small numbers of participants just to keep somewhat manageable Type of results  Highly qualitative, may be difficult to present/use Acquired skill – “learn by doing”  Identifying and extracting “interesting” things is challenging

Introduction to HCI 2. Observation - Thinking Out Loud (tol?) Sit with user doing activity of interest to you (usually a task) Encourage user to verbalize what they are thinking - that’s what is of interest Video or audio record (with permission) Not everyone is good at this Hard to keep it up for long time while also doing something; need breaks

Introduction to HCI 3. Cooperative (Participative) Evaluation Sit with user doing activity of interest to you Talk with user as the do their activity  Ask questions –Why are you doing that? –How did you know the result was what you wanted? –Are there other ways to achieve the same goal? –How did you decide to do things this way? Relaxed version of thinking out loud  Observer and participant can ask each other questions

Introduction to HCI 4. Interviews Structured – “Just the facts”  Efficient  Training - interview process Unstructured – A conversation  Inefficient  Training – process + domain knowledge Semi-structured – start with focused questions, move to open-ended discussion  Good balance, often appropriate  Training – process + domain knowledge

Introduction to HCI 4. Interviews : Semi-Structured Predetermine data of interest - know why you are asking questions - don’t waste time Plan for effective question types –How do you perform task x? –Why do you perform task x? –Under what conditions do you perform task x? –What do you do before you perform…? –What information do you need to…? –Whom do you need to communicate with …? –What do you use to…? –What happens after you…? –What is the result or consequence of…? –What is the result or consequence of NOT…?  See Gordon & Gill, 1992; Graesser, Lang, & Elofson, 1987

Introduction to HCI 4. Interviews: Typical Open- Ended Questions Why do you do this (whatever the task is you are studying) How do you do this?  Gets at task-subtask structure  Then ask about each subtask Why do it this way rather than some other way?  Attempts to get user to explain method so you can assess importance of the particular way of doing task What has to be done before you can do this?  To understand sequencing requirements What leads to you doing this (trigger)?

Introduction to HCI 4. Interviews: More Typical Open-Ended Questions Please show me the results of doing this Do errors ever occur when doing this?  If answer is ‘yes,’ then learn why occur How do you discover the errors, and how do you correct them? (Adapted from Nielsen et al, CHI ‘86) Encourage digressions; ask for elaborations What else should I have asked you?

Introduction to HCI 4. Interviews: Domain Experts Expert describes how it should be done (Not necessarily how it is done) This is where ethnographic techniques come into play

Introduction to HCI 5. Questionnaires General criteria  Make questions clear and specific  Ask some closed questions with range of answers –Sometimes also have a no opinion option, or other answer option  Do test run with one or two people

Introduction to HCI 5. Questionnaires - Example Seven-point Likert Scale (use odd #) Could also use just words  Strongly agree, agree, neutral, disagree, strongly disagree

Introduction to HCI 5. Other Typical Questions Rank the importance of each of these tasks (give a list of tasks) List the four most important tasks that you perform (this is an open question) List the pieces of information you need to have before making a decision about X, in order of importance Are there any other points you would like to make? (open-ended opinion question; good way to end) Same questions can be used in interview and in questionnaire; difference is in follow-up opportunity

Introduction to HCI 5. Questionnaires – Online CU has a web-based system you can use  Less control but more possible test participants

Introduction to HCI 6. Focus Groups Group of individuals - 3 to 10  Use several different groups with different roles or perspectives  And to separate the powerful from those who are not  Careful about few people dominating discussion Use structured set of questions  More specific at beginning, more open as progresses  Allow digressions before coming back on track Relatively low cost, quick way to learn a lot Audio or video record, with permission Value

Introduction to HCI 7. Study Documentation (artifacts) Similar in some ways to the expert interview Often describe how things should be done rather than how they are done  Try to understand why not done “by the book”

Introduction to HCI 8. Look at Competitive Products Looking for both good and bad ideas  Functionality  UI style Do user task performance metrics to establish bounds on your system

Introduction to HCI 9. Contextual Inquiry Method professed by Holtzblatt and others (incontextdesign.com) Based on ethnographic methods  In context – go and watch (ethnography)  Apprentice model – the user is the expert  Interpretation of data (affinity notes, affinity diagrams, etc) – do with the user  Focus – have a focus for the sessions to keep on track

Introduction to HCI Which Methods to Use? Depends on  Resources  Current knowledge of tasks and users  Context –Can’t use talking out loud if tasks involve two people working together  Essential to use some methods  Not likely you will use all methods

Introduction to HCI exercises Problem: someone who is trying to find the netID for Cindy Corritore  Contextual inquiry  Talk Aloud  Questionnaire – develop some questions