CISB213 Human Computer Interaction Introduction and Overview

Lecturer Rohaini Ramli Level 4 – BW4 C16 Meeting by appointment is preferred

Subject : Structure CISB213 Human Computer Interaction 3 credits, 3 hours a week Materials – To be advised next week Assessment –Test 1 10% –Test 2 10% –Group Project 30% –Final Exam 50%

Subject : Learning Outcomes At the end of this semester, the student should be able to: Identify the basic concept of HCI Describe the evolution of HCI Discuss the design issues Assess and implement the interaction design processes Use different models of interaction design principles/rules Apply the usability evaluation techniques effectively

Course Plan WeekTopics Week 3-4Introduction to Human-Computer Interaction The Human The Computer The Interaction Week 5Interaction Design Basics Introduction Design Process User Focus Week 6 HCI in the Software Process Introduction The Software Life Cycle Usability Engineering Iterative Design and Prototyping Design Rationale

WeekTopics Week 7Design Rules Introduction Principles to Support Usability Standards & Guidelines Golden Rules & Heuristics Week 8Evaluation Techniques What is Evaluation? Goals of Evaluation Evaluation Methods Choosing an Evaluation Method Week 9 Universal Design Introduction Universal design Principles Multi-modal Interaction Designing for Diversity Course Plan

WeekTopics Week 9User Support Introduction User Support Requirement Approaches to User Support Designing User Support Systems Week 10Cognitive Models Introduction Goal and Task Hierarchies Linguistic Models Physical and Device Models Week 11 Communication and Collaboration Models Introduction Face-to-face Communication Text-based Communication Course Plan

WeekTopics Week 12Meeting the Changing Needs of IT Development and Use Groupware Ubiquitous computing Augmented realities Course Plan

Assessment Plan

Reference Human–Computer Interaction, 3rd Edition, by Alan Dix, Janet Finlay, Gregory D. Abowd, Russell Beale, Prentice Hall, Designing the User Interface-Strategies for Effective Human-Computer Interaction, Fifth Edition, by Ben Shneiderman and Catherine Plaisant, Pearson Addison Wesley,

11 Why Bother?

12 Why Systems Fail? Inadequate requirements13% Lack of user participation12% Inadequate resources11% Unrealistic expectations10% Lack of support at senior level9% Changing specification8% Lack of planning8%

13 The Perfect User (every designer ‘s wish)

14 Common Issues in User Interface Design Software developers are forced to “do it all” Often based on intuition and experience than on theory-based models Tendency to let the art of interface design beats its usability Inconsistent features that do not fit into a good user interface design criteria

15 Why Study HCI? Business view :  to employ people more productively and effectively - people costs now far outweigh hardware and software costs  people now expect “easy to use” systems - generally they are not tolerant of poorly designed systems - if a product is hard to use, they will seek other products

16 Why Study HCI? Human Factors view :  Humans have limitations.  Errors are costly in terms of - loss of time & money - loss of lives in critical systems - loss of morale

17 What is HCI Short for human-computer Interaction. A discipline concerned with the study, design, construction and implementation of human-centric interactive computer systems.

18 The goal of HCI usability. The goals of HCI are to develop or improve the safety, utility and effectiveness of systems that include computers, often through improving usability.

19 What is usability? Usability can simply be thought of as the practical implementation of good HCI, but, more formally : –Usability means easy to learn, effective to use and providing an enjoyable experience

20 UI Development process : User Profiling Usability goals Task analysis & understanding the process Prototyping Evaluation Programming How to design and build usable UIs?

21 Important!!! users should be involved throughout the development of the project (How?) specific usability and user experience goals need to be identified, clearly documented and agreed at the beginning of the project

22 Understanding interaction User centric design is the formula for usability The key to User-centered Design is to understand Interaction We need to understand : –What Interaction is –What are the elements involved

23 Interaction Model The most influential model of interaction is Donald Norman’s ( : Execution-Evaluation cycle Norman divides interaction into : –Execution User activities aimed at making the system do something –Evaluation Evaluating whether the system did actually do what the user wanted

24 Understanding Interaction Execution –If User cannot make system do what they want e.g. cannot understand how to do it, unclear icons, unclear indication etc. –Will result in the Gulf of Execution i.e. difference between the user’s formulation of the action and the actions allowed by the system

25 Understanding interaction Evaluation –If user cannot see what happened to system e.g. if system has done what they want but no feedback is given to the users etc. –Will result in the Gulf of Evaluation i.e. difference between the representation of the system state/result and the expectations of the user Good Design aims to reduce these gulfs

Your first task Work individually Take a picture of one badly designed object you can find here at UNITEN Prepare a PowerPoint slide to explain why do you think the object is badly designed To be presented in the next class.

27 Q & A