Usability Techniques Lecture 13.

Slides:



Advertisements
Similar presentations
DEVELOPING A METHODOLOGY FOR MS3305 CW2 Some guidance.
Advertisements

Cultural Heritage in REGional NETworks REGNET ALI Status Report.
Chapter 5 Development and Evolution of User Interface
Requirements gathering
Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
Chapter 4 Design Approaches and Methods
Usability presented by the OSU Libraries’ u-team.
Lecture 13 Revision IMS Systems Analysis and Design.
Usability Inspection n Usability inspection is a generic name for a set of methods based on having evaluators inspect or examine usability-related issues.
Evaluation Methodologies
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.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
Project Life Cycle Jon Ivins DMU. Introduction n Projects consist of many separate components n Constraints include: time, costs, staff, equipment n Assets.
Evaluation: Inspections, Analytics & Models
User Interface Evaluation CIS 376 Bruce R. Maxim UM-Dearborn.
Usability Methods: Cognitive Walkthrough & Heuristic Evaluation Dr. Dania Bilal IS 588 Spring 2008 Dr. D. Bilal.
©2011 1www.id-book.com Analytical evaluation Chapter 15.
What is Business Analysis Planning & Monitoring?
Instructional Design Brian Newberry. Instructional Design Instructional Design is a systematic process for the creation of educational resources.
1 SWE 513: Software Engineering Usability II. 2 Usability and Cost Good usability may be expensive in hardware or special software development User interface.
ITEC224 Database Programming
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
Lecture 9 Usability of Health Informatics Applications (Chapter 9)
User-Centered Development Methodology A user interface comprises “ those aspects of the system that the user comes in contact with.” ● Moran [1981]
Multimedia Specification Design and Production 2013 / Semester 1 / week 9 Lecturer: Dr. Nikos Gazepidis
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Multimedia Specification Design and Production 2012 / Semester 1 / week 5 Lecturer: Dr. Nikos Gazepidis
Chapter 3: Managing Design Processes
SEG3120 User Interfaces Design and Implementation
Lecture 7: Requirements Engineering
Web Site Usability. Benefits of planning usability Increased user satisfaction, which translates directly to trust and brand loyalty Increased user productivity,
Systems Life Cycle. Know why it is necessary to evaluate a new system Understand the need to evaluate in terms of ease-of- use, appropriateness and efficiency.
Software Engineering User Interface Design Slide 1 User Interface Design.
User Interfaces 4 BTECH: IT WIKI PAGE:
Evaluating a UI Design Expert inspection methods Cognitive Walkthrough
Usability Engineering Dr. Dania Bilal IS 582 Spring 2006.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Usability Engineering Dr. Dania Bilal IS 592 Spring 2005.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
User Interface Evaluation Introduction Lecture #15.
Creating User Interfaces (Catch-up XML?) CMS, Usability checklist reports Preparation for user observation studies Blogs, Social Spaces, etc. Homework:
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN.
Usability Engineering Dr. Dania Bilal IS 582 Spring 2007.
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
Usability Engineering Dr. Dania Bilal IS 587 Fall 2007.
1 Usability Analysis n Why Analyze n Types of Usability Analysis n Human Subjects Research n Project 3: Heuristic Evaluation.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Software Design and Development Development Methodoligies Computing Science.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
Day 8 Usability testing.
CEN3722 Human Computer Interaction Overview of HCI Dr. Ron Eaglin.
HCC 831 User Interface Design and Evaluation. What is Usability?
User-Centered Design Services for MSU Web Teams Sarah J. Swierenga, Director Usability & Accessibility Center MSU Webmasters 402 Computer Center February.
1 User testing approaches: Practical techniques toward a more usable website Arc Worldwide 1.
Cognitive Informatics for Biomedicine – Chapter 5
Objectives Describe the activities of the requirements discipline
Information Systems Development
Human Computer Interaction Lecture 15 Usability Evaluation
Topic for Presentaion-2
Chapter 6: Design of Expert Systems
Human Factors Issues Chapter 8 Paul King.
Methodologies For Systems Analysis.
SY DE 542 User Testing March 7, 2005 R. Chow
User Interface Design and Evaluation
Chapter 26 Inspections of the user interface
COMP444 Human Computer Interaction Evaluation
Evaluation: Inspections, Analytics & Models
Presentation transcript:

Usability Techniques Lecture 13

Methods There are a variety of approaches to usability evaluation that you may choose to take. The methodologies can be divided into two broad categories: those that gather data from actual users and those that can be applied without actual users present. Your choice of method depends on: Cost of evaluation Appropriateness to project Time constraints Cost of implementation Cost of training new users

Risk Usability evaluations can be conducted at many stages during and after the design and development process. In choosing a method, it is important to calculate the cost not only in terms of time and materials involved, but also in terms of the impact on the end-users, especially considering the cost of losing return visitors to your website due to unusable design.

Cognitive Walkthrough Method Cognitive walkthroughs are performed at any stage of design using a prototype, a conceptual design document, or the final product. This is a more specific version of a design walkthrough, focusing on cognitive principles. Based on a user's goals, a group of evaluators steps through tasks, evaluating at each step how difficult it is for the user to identify and operate the interface element most relevant to their current subgoal and how clearly the system provides feedback to that action. Cognitive walkthroughs take into consideration the user's thought processes that contribute to decision making, such as memory load and ability to reason.

Focus Groups This is a data collecting technique where about 6 to 9 users are brought together to discuss issues relating to the system. A human factors engineer plays the role of a moderator, who needs to prepare the list of issues to be discussed beforehand and seek to gather the needed information from the discussion. This can capture spontaneous user reactions and ideas that evolve in the dynamic group process. Focus groups are also good at discovering how the system being tested differs from the user's current expectations. As we see it, focus groups provide two major benefits. First, they are less expensive than conducting interviews with the same number of people. Second, they rely on group interaction to trigger memories that may not come up during interviews.

Prototyping Prototyping techniques involve developing representations of a target system for evaluation and testing purposes. Prototyping is an essential element of an iterative design approach, where designs are created, evaluated, and refined with the results of testing at each cycle feeding into the design focus of the next cycle. Prototypes can range from extremely simple sketches (low-fidelity prototypes) to full systems that contain nearly all the functionality of the final system (high-fidelity prototypes).

Task Analysis Task analysis is a method that evaluates how people actually accomplish things with software. Through observation and interviews with users, an analyst determines a set of goals belonging to the target user. Then, a set of tasks that support these goals is determined. These are prioritized based on criteria such as the importance of the goal to the organization and the frequency of task performance. The highest priority tasks are decomposed into their individual steps. The level of decomposition varies with the budget and type of system evaluated. The analyst then suggests ways to make the task more efficient or suggests new tasks which more effectively support the goals. It is important to recognize that the analysis is done from the perspective of the end-user—not from the point of view of managers or executives who do not necessarily use the system.

Usability Inspection / Heuristic Evaluation A usability inspection is a review of a system based on a set of guidelines. The review is conducted by a group of experts who are deeply familiar with the concepts of usability in design. The experts focus on a list of areas in design that have been shown to be troublesome for users. Usability guidelines are usually derived from studies in human-computer interaction, ergonomics, graphic design, information design, and cognitive psychology. Some areas that get evaluated are the language used in the system, the amount of recall required of the user at each step in a process, and how the system provides feedback to the user. In particular, issues such as clarity, consistency, navigation, and error minimization are analyzed. Once the problems are discovered, the experts make recommendations for resolving these issues.