Noor AL Jiboury (Onondaga Community College), Tatiana Tavares (UFPB), Alexandre Nóbrega (UFPB) One of the lessons learned in area of HCI (Human Computer.

Slides:



Advertisements
Similar presentations
Design, prototyping and construction
Advertisements

Software Development Languages and Environments. Programming languages High level languages are problem orientated contain many English words are easier.
Copyright 1999 all rights reserved The HCI Design Process n User Interfaces are not just built by sitting down and drawing up designs for them n Just like.
Cognitive Walkthrough More evaluation without users.
User Interface Evaluation and Design for Deaf-Blind Users Daniel Cutler, Pollyane Carvalho, André Felipe, and Prof Tatiana Aires Tavares SUNY Oswego and.
CSC 205 Software Engineering I 1 Overview - Cognitive Walkthroughs Brief introduction to Human-Computer Interaction Introduction to Cognitive Walkthroughs.
Evaluation Through Expert Analysis U U U
Testing HCI Usability Testing. Chronological order of testing Individual program units are built and tested (white-box testing / unit testing) Units are.
User interface design Designing effective interfaces for software systems Objectives To suggest some general design principles for user interface design.
Virtual Learning Environments – How usable are they? Ian Cole Lecturer in Information & Communication Technology University of York United Kingdom.
Chapter 6: An Introduction to System Software and Virtual Machines
What is a prototype? A prototype is a small scale model of your larger product. Can be a physical object, or a simple software program. Many physical.
Programming. Software is made by programmers Computers need all kinds of software, from operating systems to applications People learn how to tell the.
Web 2.0 Testing and Marketing E-engagement capacity enhancement for NGOs HKU ExCEL3.
Chapter 6: An Introduction to System Software and Virtual Machines Invitation to Computer Science, C++ Version, Fourth Edition ** Re-ordered, Updated 4/14/09.
Online Personal Finance Management Tool CHI 170 Project Final Presentation by Bert Gao; Bey Wang; Francisco Crespo.
CSI-553 Internet Information Presented by: Ignacio Castro June 28, 2006 Internet Usability.
What is HCI? IMD07101: Introduction to Human Computer Interaction Brian Davison 2011/12.
Usability Methods: Cognitive Walkthrough & Heuristic Evaluation Dr. Dania Bilal IS 588 Spring 2008 Dr. D. Bilal.
1 Chapter-01 Introduction to Computers and C++ Programming.
Lab 8 – C# Programming Adding two numbers CSCI 6303 – Principles of I.T. Dr. Abraham Fall 2012.
Introduction to Usability By : Sumathie Sundaresan.
INTROSE Introduction to Software Engineering Raymund Sison, PhD College of Computer Studies De La Salle University User Interface Design.
Predictive Evaluation
Learning Objectives Data and Information Six Basic Operations Computer Operations Programs and Programming What is Programming? Types of Languages Levels.
INTRODUCTION TO FRONTPAGE. TOPICS TO BE DISCUSSED……….  Introduction Introduction  Features Features  Starting Front Page Starting Front Page  Components.
System Design: Designing the User Interface Dr. Dania Bilal IS582 Spring 2009.
CSCD 487/587 Human Computer Interface Winter 2013 Lecture 3 HCI and Interactive Design.
Interacting with IT Systems Fundamentals of Information Technology Session 5.
Program Development Life Cycle (PDLC)
Application in Computer Vision Final Project Nir Slakman, Oren Zur and Noam Ben-Ari.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Usability Evaluation June 8, Why do we need to do usability evaluation?
1 Nassau Community CollegeProf. Vincent Costa Acknowledgements: An Introduction to Programming Using Visual Basic 2012, All Rights ReservedAn Introduction.
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
Bryan Kern (SUNY Oswego), Anna Medeiros (UFPB), Rafael de Castro (UFPB), Maria Clara (UFPB), José Ivan (UFPB), Tatiana Tavares (UFPB), Damian Schofield.
The Software Development Life Cycle. Software Development SDLC The Software Development Life-Cycle Sometimes called the program development lifecycle.
Software Architecture
COMPSCI 345 / SOFTENG 350 Review for mid-semester test AProf Beryl Plimmer.
User interface design and human computer interaction Xiangming Mu.
A centre of expertise in digital information management 1 UKOLN is supported by: SWMLAC Workshop: Accessibility and Usability Marieke Guy.
Interaction Design Dr. Jim Rowan Foley Introduction What’s in the Book that we’ll cover.
Usability Engineering Dr. Dania Bilal IS 582 Spring 2006.
Instructions These lessons are interactive and require your participation. Please follow the instructions on each slide. Here are a few common symbols.
User Interface Evaluation Cognitive Walkthrough Lecture #16.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Introduction to Usability By : Sumathie Sundaresan.
Usability Engineering Dr. Dania Bilal IS 592 Spring 2005.
June 5, 2007Mohamad Eid Usability Testing Chapter 8.
Cognitive Walkthrough More evaluating with experts.
Introduction to Evaluation without Users. Where are you at with readings? Should have read –TCUID, Chapter 4 For Next Week –Two Papers on Heuristics from.
RUGGAAMUFFIN Requirements analysis and design Shane Murphy.
1 Usability evaluation and testing User interfaces Jaana Holvikivi Metropolia.
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
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.
Getting ready. Why C? Design Features – Efficiency (C programs tend to be compact and to run quickly.) – Portability (C programs written on one system.
JavaScript Introduction and Background. 2 Web languages Three formal languages HTML JavaScript CSS Three different tasks Document description Client-side.
COGNITIVE WALKTHROUGH Vigneshwar Poojar. The cognitive walkthrough is a formalized way of imagining people’s thoughts and actions when they use an interface.
A centre of expertise in digital information management UKOLN is supported by: Usability on a Shoestring Budget (1) Emma Tonkin & Greg.
Usability Engineering Dr. Dania Bilal IS 582 Spring 2007.
Usability Engineering Dr. Dania Bilal IS 587 Fall 2007.
Software. Introduction n A computer can’t do anything without a program of instructions. n A program is a set of instructions a computer carries out.
Prof. James A. Landay University of Washington Winter 2007 Video Prototyping January 22, 2007.
1 Web Site Usability Motivations of Web site visitors include: –Learning about products or services that the company offers –Buying products or services.
CEN3722 Human Computer Interaction Overview of HCI Dr. Ron Eaglin.
Human-Computer Interaction
Evaluation Techniques 1
Usability ECE 695 Alexander J. Quinn 3/21/2016.
The User Interface Design Process
Cognitive Walkthrough
Presentation transcript:

Noor AL Jiboury (Onondaga Community College), Tatiana Tavares (UFPB), Alexandre Nóbrega (UFPB) One of the lessons learned in area of HCI (Human Computer Interaction) is that usability evaluation (to test if the interface is easy to use by users) should start early in design process.The early the problems are detected, the greater the chance that they will be fixed. Usually the test used at the end of design cycle, where making changes to the interface is difficult and require a lot of time and work [1]. Introduction A little bit about usability method in practices method in practices We want to say thanks to... A study case about user interfaces evaluation for LIBRAS Language LIBRAS? What? Usability is an important condition for the design to be used by wide rang of people. Where its defined by its five quality components. Which are: learnability (how easy is to doing the basic tasks), efficiency (how fast the user can do the tasks after learning the design), memorability (if the design is usable after not using it for period of time), error (how many errors the user make, how several are these errors, and how easy they can recover from the error) and satisfaction (what the test users think about the design) [2]. LIBRAS is the name of the Brazilian Sign Language where it used by the majority of deaf people in Brazil. LAVID lab want to help this majority of people to be able to understand what's on TV, so they started developing new ideas of how to help them. Creating the Second window interface for LIBRAS Legend in digital Movies was their move to help. This design will give the deaf people in Brazil a great chance of watching and understanding any video they want. The design had two different parts, these parts are: 1. LIBRAS Dictionary, will translate words into signs. Where each sign is represented by an animated image or video file that has a code associated to it. 2. LIBRAS Generator, receives the input streams of audio, video, or closed caption from video encoder or closed caption generator. Directions will be given to the users using the LIBRAS language with Portages subtitle. Where it first will be asking the user to upload a video, then chose where we want the avatar window to be, finally we will chose the size of the avatar window. To make sure that the program is working in the right way we will be performing a usability test with the help of deaf people. For this application, the method called cognitive walkthrough approach will be used to evaluate the interface. Which analyses a specific sequence of steps; when an action is required by the user to accomplish a task. A group of users will test the interface by going through a group of tasks to evaluate the understandability and all of the five quality component. We will let the test users test the product and they will tell about their experience with the software, what's good and bad and what to fix and add. Where it involves a step by step task testing and a complete and detailed description of prototype, tasks and list of actions [3]. We ran three different groups of testing for each interface. The first group had three test users the second group had two test users and the third group had three test users. We followed this way of testing because it is better to distribute the budget for the user testing across many small tests because we want to improve the design not documents its weaknesses, the first group of testers will help us to solve 85% of the problems, the second group of users will help us with 15% of problems that was not found on the first test, finally, the third group will help us to find the last 2% of problems that may be left[4]. Where we evaluated all of the four tasks 1.Upload video file 2.Upload subtitle file 3.Determining avatar window position 4.Determining avatar window size After doing the tasks, users had to go through evaluation form. After reviewing the evaluation forms that the testers filled we came up with the following: 1.Puss button, so users do not have to start all over when they miss part of the direction video. 2.To be able to skip the directions, if the user is familiar with the design, where it's better to let them skip that part instead of wasting their time. 3.Let the directions on the buttons visible to the eye, by using simple language. 4.Display conformation button on the video window, because it will be easy to notice and know what the next step is. 5.Make the avatar movement faster, so the avatar would correspond to the actors actions. Figure 02: (a) LIBRAS - Brazilian Sign Language. (b) CineLibras – Brazilian application for deaf people. (c) CineLibras virtual interpreter. (a) (b) (c) Figure 03: The test users and the application. Figure 01: Usability. URL: yTest.png (a) (b) (c) Result References: 1."Usability Evaluation with the Cognitive Walkthrough" by John Rieman, Marita Franzke, and David Redmiles. 2."Introduction to Usability" by Jakob Nielsen. 3."introduction to Cognitive Walkthrough" by Emma Tonkin. 4."Why You Only Need To Test With 5 Users" by Jakob Nielsen