1. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved.

Slides:



Advertisements
Similar presentations
Agile Usability Testing Methods
Advertisements

SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 11 Designing for Usability I.
CS305: HCI in SW Development Evaluation (Return to…)
User Interface Design Notes p7 T120B pavasario sem.
Chapter 14: Usability testing and field studies. 2 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept.
Job Analysis OS352 HRM Fisher January 31, Agenda Follow up on safety discussion Job analysis – foundation of HR – Purpose – Various techniques.
Usability presented by the OSU Libraries’ u-team.
Defining Usability....
CSC 205 Software Engineering I 1 Overview - Cognitive Walkthroughs Brief introduction to Human-Computer Interaction Introduction to Cognitive Walkthroughs.
Usability Inspection n Usability inspection is a generic name for a set of methods based on having evaluators inspect or examine usability-related issues.
Usability 2004 J T Burns1 Usability & Usability Engineering.
Principles and Methods
Usability Specifications
SE 555 Software Requirements & Specification 1 SE 555 Software Requirements & Specification Prototyping.
Usability and Evaluation Dov Te’eni. Figure ‎ 7-2: Attitudes, use, performance and satisfaction AttitudesUsePerformance Satisfaction Perceived usability.
HCI revision lecture. Main points Understanding Applying knowledge Knowing key points Knowing relationship between things If you’ve done the group project.
Mid-Term Exam Review IS 485, Professor Matt Thatcher.
Damian Gordon.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five.
Web 2.0 Testing and Marketing E-engagement capacity enhancement for NGOs HKU ExCEL3.
Design, goal of design, design process in SE context, Process of design – Quality guidelines and attributes Evolution of software design process – Procedural,
User Interface Design Chapter 11. Objectives  Understand several fundamental user interface (UI) design principles.  Understand the process of UI design.
Requirements Gathering and Task analysis. Requirements gathering and task analysis 4 Requirements gathering is a central part of systems development understanding.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Usability 2009 J T Burns1 Usability & Usability Engineering.
Usability Methods: Cognitive Walkthrough & Heuristic Evaluation Dr. Dania Bilal IS 588 Spring 2008 Dr. D. Bilal.
Evaluation IMD07101: Introduction to Human Computer Interaction Brian Davison 2010/11.
IPortfolio assignment Mandatory Unit evidence. Centres may use some or all of these activities or some of their own devising to help candidates complete.
Product Development & User Testing
Principles of User Centred Design Howell Istance.
1 SWE 513: Software Engineering Usability II. 2 Usability and Cost Good usability may be expensive in hardware or special software development User interface.
Output and User Interface Design
Evaluation of Adaptive Web Sites 3954 Doctoral Seminar 1 Evaluation of Adaptive Web Sites Elizabeth LaRue by.
CSC 480 Software Engineering Lecture 19 Nov 11, 2002.
Interacting with IT Systems Fundamentals of Information Technology Session 5.
Multimedia Specification Design and Production 2013 / Semester 1 / week 9 Lecturer: Dr. Nikos Gazepidis
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN Application.
CS CS 5150 Software Engineering Lecture 11 Usability 1.
What about Chapter 7?. What is the usability process? Tyldesley’s 22 possible Measurement Criteria Let’s focus on usability–A usability initiative needs.
Productivity Programs Common Features and Commands.
UI Style and Usability, User Experience Niteen Borge.
1 ISE 412 Usability Testing Purpose of usability testing:  evaluate users’ experience with the interface  identify specific problems in the interface.
Midterm Stats Min: 16/38 (42%) Max: 36.5/38 (96%) Average: 29.5/36 (78%)
INTRO TO USABILITY Lecture 12. What is Usability?  Usability addresses the relationship between tools and their users. In order for a tool to be effective,
COMPSCI 345 / SOFTENG 350 Review for mid-semester test AProf Beryl Plimmer.
CS2003 Usability Engineering Human-Centred Design Dr Steve Love.
Chapter 8 Usability Specification Techniques Hix & Hartson.
Evaluating a UI Design Expert inspection methods Cognitive Walkthrough
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
Usability Engineering Dr. Dania Bilal IS 582 Spring 2006.
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
OSU Libraries presented by the u-team.
Usability Engineering Dr. Dania Bilal IS 592 Spring 2005.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
1 Usability evaluation and testing User interfaces Jaana Holvikivi Metropolia.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
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.
The Design Process A bluffer’s guide to interface design A ‘proper’ Design process.
Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2010 Stephen R. Schach
Usability Engineering Dr. Dania Bilal IS 582 Spring 2007.
Usability Engineering Dr. Dania Bilal IS 587 Fall 2007.
Evaluation / Usability. ImplementDesignAnalysisEvaluateDevelop ADDIE.
1 Testing—tuning and monitoring © 2013 by Larson Technical Services.
What Do We Mean by Usability?
Usability engineering
Usability engineering
SY DE 542 User Testing March 7, 2005 R. Chow
Chapter 6 Thinking about requirements and describing them
COMP444 Human Computer Interaction Usability Engineering
Presentation transcript:

1

Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved in Usability Engineering Lifecycle –Apply Usability Engineering Lifecycle in designing any system or application

Key Terms you must be able to use If you have mastered this topic, you should be able to use the following terms correctly in your assignments and exams: –Usability engineering –Usability lifecycle –Usability goals

Usability Usability: “ the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.”

Usability Why is usability important? It makes the difference between performing a task accurately and completely or not, and enjoying the process or being frustrated. Determine the success or failure of a system Poor usability… Reduce productivity Increase cost time and effort

Usability usually refers to software but is relevant to any product. Some ways to improve usability include: shortening the time to accomplish tasks, reducing the number of mistakes made, reducing learning time, and improving people's satisfaction with a system. Usability

According to Jakob Nielsen (2003), usability is defined by 5 quality components : Learnability : ease of learning for novice users. Efficiency : steady-state performance of expert users. Memorability : ease of using system intermittently for casual users. Errors : error rate for minor and catastrophic errors. Subjective Satisfaction: how pleasant the system is to use. Usability

Some systems are designed to focus on learnability. Others emphasize efficiency for proficient users. Some support a combination of ease of learning and an “expert mode” (for example rich menus and dialogues plus a command/ scripting language)

Extensive Computer Experience Expert User Of System Ignorant About the Domain Novice User of the System Minimal Computer Experience Knowledge able About the Domain

Novice Users: No or limited knowledge of the occupational task to be performed, and of computers and interface concepts

Knowledgeable Intermittent Users: Understanding of the task concepts Broad knowledge of computers and interface concepts. Intermittently use the system and may therefore have problems with retention Expert Frequent (Power) Users: Thoroughly familiar with both task and interface concepts. They are likely to use the system often and appreciate short cuts to speed their work.

Learnability: pick novice users of system, measure time to perform certain tasks. Distinguish between the various timings taken for some general computer experience.

Efficiency : decide definition of expertise, get sample expert users (which tends to be difficult), measure time taken to perform typical tasks.

Memorability : get sample casual users (who are usually away from system for certain time/duration) and measure time to perform typical tasks.

Errors : count minor and catastrophic errors made by users while performing some specified task.

Satisfaction : ask users subjective opinion (questionnaire, interview), after trying system for real task.

The term usability engineering describes a process of user interface development, sometimes referred to as user centred design. It is a lifecycle process that puts an early emphasis on user and task analysis and actual user involvement in the design and testing of a product. A product developed with such a user centred process is likely to be a more usable product than one that is developed independent of user considerations and involvement.

Parallel Design Sketches Participatory Design Iterative Design Final Released Product Users, Tasks, Environment Analysis Usability Goals, Competitive Analysis First Prototype Formative Testing

1. Identify user requirements and problems Profile Users Task Analysis 2. Identify usability goals based on user requirements 3. Checkout similar products 4. Design and prototype a solution (involve users) 5. Evaluate prototype Usability testing (real users and real tasks) 6. Reiterate steps 4-5 …until users are satisfied Usability Engineering Lifecycle

Identify user requirements and problems: Define your user population. Determine the distribution of skills, knowledge and experience within your user population. Assess the user’s skill level with respect to both the task and computer domain. Usability Engineering Lifecycle

Identify user requirements and problems: Typical Profile: 40 % Novice Users 57 % Knowledgeable/Intermittent Users 3 % Expert Users Other Important Information: 10 % of user population colour blind 15 % are the elderly Usability Engineering Lifecycle

Identify user requirements and problems: Task analysis allows a designer to identify the goals and purposes of the intended user group. This used to involve further analysis of user requirements or investigation/observation of customers Used to guide user interface design Usability Engineering Lifecycle

Identify usability goals based Learnability, Efficiency, Memorability, Error, Subjective Satisfaction Decide in advance on usability metrics and desired level of measured usability E.g. Errors Per Hour OptimalTargetCurrentUnacceptable > 5 Usability Engineering Lifecycle

Check out similar products (Competitive Analysis) Competitive analysis of software components Competitive analysis of competing systems Usability Engineering Lifecycle

Parallel Design (Explore design alternatives) designers should work independently, then compare draft designs Usability Engineering Lifecycle

Participatory Design Have access to pool of representative users. Guided discussion of prototypes, paper mock-ups, screen designs with representative users. E.g. Card Sorting Usability Engineering Lifecycle

Card sorting is a technique for exploring how people group items, so that you can develop structures that maximize the probability of users being able to find items Is easy and cheap to conduct Enables you to understand how “real people” are likely to group items Identifies terminology that is likely to be misunderstood.

E.g. How would you group these tasks into 3 groups? (File, Edit, View) open, cut, normal view, close, copy, zoom in, save, paste, zoom out, save, select, toolbar, print ??????

Card sorting is also a technique for allowing users actual selections out of several options to determine final design decisions Is easy and cheap to conduct Enables you to determine ‘actual’ preferences versus what users ‘think’ they prefer Allows for more accurate understanding by user since actual examples are seen

Title Content Title Content Title Content Title Content Title Content Title Content Title Content Title Content A BC D E F G H

Applying Guidelines Guidelines... general principles and advice about usability characteristics of interfaces Can be intimidating – often hundreds or thousands of specific recommendations. Usability Engineering Lifecycle

Prototyping & Testing Perform usability evaluation as early as possible in the design cycle by building and evaluating prototypes Usability Engineering Lifecycle

Check yourself to see if you can now: –Define the term “Usability Engineering” –Describe the various steps involved in Usability Engineering Lifecycle –Apply Usability Engineering Lifecycle in designing any system or application

Q & A