User Studies Basic principles, methods, and examples

Slides:



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

Jason Powell The University of North Texas.  Traditional instruction separates knowing from doing.  Knowledge is abstract and decontextualized.  Activity.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
Analysis Concepts and Principles
Identifying needs and establishing requirements Chapter 7b.
An evaluation framework
Administrivia Turn in ranking sheets, we’ll have group assignments to you as soon as possible Homeworks Programming Assignment 1 due next Tuesday Group.
User-centered approaches to interaction design. Overview Why involve users at all? What is a user-centered approach? Understanding users’ work —Coherence.
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Interviews Stephanie Smale. Overview o Introduction o Interviews and their pros and cons o Preparing for an interview o Interview Elements: o Questions.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY 1 Requirements Engineering T Software Development Project.
Chapter 11: An Evaluation Framework Group 4: Tony Masi, Sam Esswein, Brian Rood, & Chris Troisi.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY User Studies Basic principles, methods, and examples Sari.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Human Computer Interaction
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Object-Oriented Analysis and Design Fall 2009.
Facilitating Multi Stakeholder Processes and Social Learning Herman Brouwer / Karèn Verhoosel Centre for Development Innovation Semi structured.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Information Gathering Prototypes Structured Walkthrough.
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
CSCI 4163 / CSCI 6904 – Winter Housekeeping  Clarification about due date for reading comments/questions  Skills sheet  Active listening handout.
SBD: Analyzing Requirements Chris North CS 3724: HCI.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Identifying needs and establishing requirements Data gathering for requirements.
Lesson 11: Designing Research. Naturalistic Observation When designing a naturalistic observation researchers need to consider;  behavioural categories,
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
Fact Finding (Capturing Requirements) Systems Development.
Chapter 5 Trawling For Requirements. Determining What the Product Should Be without understanding the work that it is to become a part of Many projects.
Z556 Systems Analysis & Design Session 3 1 ILS Z556.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini XVII. Verification and Validation.
Investigating System Requirements
From: A. Cooper et al.: About Face Andreas Rudin
NEEDS ASSESSMENT HRM560 Sheikh Rahman
Meaning-based context and universal themes
SIE 515 Design Evaluation Lecture 7.
Scope Planning.
Year 10 Information & Software Technology
CMPE 280 Web UI Design and Development August 29 Class Meeting
Learning Styles & Teaching Styles
Determining What People Really Want!
Observations contextual inquiry
Software Engineering: A Practitioner’s Approach, 6/e Chapter 17 Formulation and Planning for Web Engineering copyright © 1996, 2001, 2005 R.S. Pressman.
SNS College of Engineering Coimbatore
EKT 421 SOFTWARE ENGINEERING
Abstract descriptions of systems whose requirements are being analysed
Requirements Elicitation – 1
Systems Analysis and Design in a Changing World, 6th Edition
The role of the Analyst in requirements Elicitation
Informatics 121 Software Design I
Informatics 121 Software Design I
SBD: Analyzing Requirements
Design Research Jon Kolko Director & Founder, Austin Center for Design.
Job Analysis Prof Srividya Iyengar.
CS294 Software Engineering Software Usability
Informatics 121 Software Design I
For University Use Only
Evaluation.
Core Capability Drive-Through Workshop
Use Case Modeling Part of the unified modeling language (U M L)
User-centered approaches to interaction design
Miguel Tavares Coimbra
Dr Amina Rashad and Dr Nahed Kandeel
CBMS4303: Management Information System
THE PROCESS OF INTERACTION DESIGN
COMP444 Human Computer Interaction Evaluation
Miguel Tavares Coimbra
High and Low context cultures
Presentation transcript:

User Studies Basic principles, methods, and examples 30.10.2001 Sari Kujala Qure Project Software Business and Engineering Institute (SoberIT)

Contents User studies: goal and principles User study process: methods and templates Analysing stakeholders Planning Studying users Analysing and reporting Presenting results Effort estimations, lessons learned

User studies The goal is to gather USER NEEDS for product development User need is manifested by the context of use, problems, and possibilities Context of use means the characteristics of the intended users, users' present tasks, tools and environment Understanding users’ goals is essential

Principles of user studies Plan the focus and objectives for the visit Watch, listen to, and talk with users in their own environment Treat users as experts Take the role of the apprentice. Your task is to confess your ignorance and ask stupid questions.

User studies: What to look for? Background information User’s goals and preferences Current processes and problems User’s knowledge, skills, & experiences Context of using Pros and cons of the current tools and processes

User study process Analysing stakeholders Planning Seeing users Analysing and reporting Presenting results

Analysing stakeholders Utilising existing documents Identifying stakeholders Identifying user groups Preliminary user description

Planning (Hackos and Redish, 1998) Decide issues and objectives for the study Select user study methods Plan how data will be analysed and reported Choose participating users Choose locations where to go Form a user study team and decide roles Plan how the user visits will be recorded Prepare materials for user visits Plan a pleminary schedule

User study methods Observing and video-observing Interviewing Contextual Inquiry Artifact walkthrough Thinking-aloud method Simulations, role-play Interactive feature conceptualization

Selecting user study methods

Observing Users are observed in their own environment performing their tasks Focus on gathering non-verbal information: routinised actions, detailed behaviour, environment Can be time consuming, if not used together with other methods

Interviewing Users are interviewed in their own environment using their language Focus on verbal information: user goals, tasks and sequences in general level, domain specific information Predefined interview themes are used flexibly Efficient method, but detailed and nonverbal information may be lost

Contextual Inquiry (Holtzblatt and Byer, 1998) Interviewing and observing is combined; users are watched, listen to, and talked with while they work in their own environment Focus on uncovering detailed work practice and context of use

Artifact walkthrough Users are asked for examples of artifacts: forms, reports, hand-written manuals, notes The artifacts can help to understand how tasks are done what is difficult for users to do or remember what kind of information flows there are from user to user

Thinking aloud-method Focus on gathering non-verbal information: skills, selection rules and problem solving, beliefs Users are asked to tell and show how they use a tool

Simulations If it is not possible to disturb users in real situations, the use situation can be simulated Or you can videorecord the situation and discuss with users afterwards

Interactive feature conceptualization During an interview, tools, places, persons are written in sticky notes. In the end, user is asked to rearrange the notes in categories, the over all picture is drawn together with the interviewer using arrows etc. Focus on visualisation of user information, the overall picture, checking the validity of interviews

Analysing and reporting User profiles Task sequences and hierarchies Scenarios User needs tables -> use cases Affinity diagrams Videoshots and photographs

Example: A user need table

Example: Use Case

Report contents Case summary Customer descriptions User descriptions Context of use descriptions User needs tables Findings-tables

Presenting Presentations better way in sharing than a report alone Videoshots and photographs were prefered Presentations inspired salesmen to give more examples and information

Number of person hours spent on the user studies

Lessons learned from the cases A small-scale user study pilot has been a good way of introducing user needs gathering to companies Results visible: increased innovations and customer satisfaction Motivating for people and organisation Learning by doing A multi-disciplinary team work was efficient