In user trials a product is tested by “real users” trying out the product in a controlled or experimental setting, where they are given a set of tasks.

Slides:



Advertisements
Similar presentations
Chapter 14: Usability testing and field studies
Advertisements

Why do we Evaluate products that are already on the market? When designers are trying to design new products to put on the market, it is very important.
Evaluating health informatics projects Reasons for and problems of evaluation Objective model Subjective model.
Acknowledgements: Most of this course is based on the excellent course offered by Prof. Kellogg Booth at the British Columbia University, Vancouver, Canada.
Système COopératif Routier Expérimental en France Collections of data from hundred of drivers mobilized during experiments met two main.
Designing and Developing Decision Support Systems Chapter 4.
Chapter 4 Design Approaches and Methods
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 11 Designing for Usability I.
Standard Work Standard Operations Training Pack. Aims & Objectives Target Audience Production staff, ME & Training personnel Aim To give attendees the.
System Analysis (Part 1)
Clarke, R.J. (2000) EDM-DSL 1 EDM. Clarke, R.J. (2000) EDM-DSL 2 ESD Related Definitions (1) Evolutionary Systems Development (ESD)- is the formal name.
Modelling.
Chapter 14: Usability testing and field studies. 2 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept.
Chapter 14: Usability testing and field studies. Usability Testing Emphasizes the property of being usable Key Components –User Pre-Test –User Test –User.
Evaluation. formative 4 There are many times throughout the lifecycle of a software development that a designer needs answers to questions that check.
User Observation/Field Studies: Observing users as they work in a field study, and analyzing the data collected. Matt, Nick, Federico, and Curtis  {who.
Define usability testing Usability is all about how easy a product, service or system is to use. The extent to which a product can be used by specified.
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.
Evaluation: Inspections, Analytics & Models
From Controlled to Natural Settings
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Stages of Product Development
Lesson planning? It can’t be that difficult! Svetla Tashevska, NBU.
User Centered Design Lecture # 5 Gabriel Spitz.
A Day in the Life of a UX Practitioner 21 January 2013 Dr Chandra Harrison.
©2011 1www.id-book.com Analytical evaluation Chapter 15.
SYSTEM ANALYSIS AND DESIGN
Chapter 14: Usability testing and field studies
Predictive Evaluation
Usability Testing Teppo Räisänen
Principles of User Centred Design Howell Istance.
Dtengineering 1 of 16 The Product Development Process Introduction.
 The College Board has joined the American Chemical Society and the National Science Teachers Association in objecting to simulated lab software (e.g.
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.
Evaluation Methods It is very important to choose the correct method of evaluating your chosen product, and there are many ways to do so... Product Review.
© 2003, Carla Ellis Experimentation in Computer Systems Research Why: “It doesn’t matter how beautiful your theory is, it doesn’t matter how smart you.
Final Idea: Working Drawing
1 MultiCom, a platform for the design and the evaluation of interactive systems. MultiCom, a platform for the design and the evaluation of interactive.
Human Computer Interaction
Usability testing. Goals & questions focus on how well users perform tasks with the product. – typical users – doing typical tasks. Comparison of products.
Usability Evaluation June 8, Why do we need to do usability evaluation?
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,
Models of Situations. A computer model of a system is a program and data which behaves like the real thing, e.g. a driving simulation, a graph of business.
CS2003 Usability Engineering Usability Evaluation Dr Steve Love.
User Interface Design & Usability for the Web Card Sorting You should now have a basic idea as to content requirements, functional requirements and user.
Year 9: PRODUCT ANALYSIS Resistant Materials. Today We will look at product analysis and learn what we need to consider when analysing a product. You.
Pleasing in appearance.
Friday, October 15 Objective: Students will be able to present information they have found on an engineering career. Bell Ringer: Quick Write: What is.
Chapter 15: Analytical evaluation. Aims: Describe inspection methods. Show how heuristic evaluation can be adapted to evaluate different products. Explain.
ERP Implementation Lifecycle
Day 10 Analysing usability test results. Objectives  To learn more about how to understand and report quantitative test results  To learn about some.
Session 6: Other Analysis Issues In this session, we consider various analysis issues that occur in practice: Incomplete Data: –Subjects drop-out, do not.
Oct 211 The next two weeks Oct 21 & 23: Lectures on user interface evaluation Oct 28: Lecture by Dr. Maurice Masliah No office hours (out of town) Oct.
Research Assessment Task
IB Design and Technology Evaluation Evaluation and Designing.
Title Page Title Page Add a picture of your project here.
Human Computer Interaction Lecture 15 Usability Evaluation
Unit 6 Application Design Sample Assignment.
Evaluation techniques
From Controlled to Natural Settings
Mockups and Prototypes
Chapter 22 Planning who, what, when, and where
Technological Design Process Unit 1 Lesson 4
From Controlled to Natural Settings
Evaluation.
Lecture 34: Testing II April 24, 2017 Selenium testing script 7/7/2019
Evaluation: Inspections, Analytics & Models
Practical Interface Guidelines
Presentation transcript:

In user trials a product is tested by “real users” trying out the product in a controlled or experimental setting, where they are given a set of tasks to perform. The result can be a “problem list” which contains valuable information for designers regarding the potential for improving the usability of a product.

User trials are normally applied when a prototype product is running, or when a complete product is to be evaluated. Low-tech mock-ups and prototypes may also be used. They are often used before a final product design has been agreed, and are commonly used on pre - production prototypes. They are often used as a simpler way of evaluating products compared to more extensive field trials, which commonly take place when a more completed product is to be evaluated prior to market release.

Besides the product to be tested, an area where testing can take place. The testing process may take several weeks, or even months depending on the number of testing sessions. Costs of this will vary with the number of tests, how complex the test are and how they are evaluated. User trials try and identify a set of tasks that users would perform when using the product. These can include commonly occurring tasks, but can also include tasks which would be difficult to observe in other settings. For example, in a user trial it is possible to simulate dangerous events which might not be observed in any other forms of investigation e.g. Crash testing a car.

Advanced testers Advanced testing is performed in labs, by professionals with specialised equipment. Actual users or Potential users End users (consumers) of the product are used in trials like this.

Step 1: Planning At this stage the aims of the User Trial are decided. Step 2: Test material Tasks are selected which will be performed frequently by a user. Step 3: The trial Under guidance, the testers perform the User Trial. Step 4: Data analysis The results of the tests are analysed. Step 5: Implications The results are passed on to designers, developers to focus on the possibilities for improvement in the design of the product.

Aesthetics The overall appearance of a product. Ergonomics How the product feels and handles. Function The job it is supposed to do. Performance How well the product performs its function/s. Safety How safe it is to use.

CLICK THE ARROW TO RESTART PRESENTATION