SENG 310: Human Computer Interactionaalbu/SENG 310 2007/SENG 310-1.pdfSENG 310 : Human Computer...

SENG 310: Human Computer Interaction

Instructor: Alexandra Branzan [email protected]://www.ece.uvic.ca/~aalbu

SENG 310 : Human Computer Interaction, Lecture 1. 2

Topics

Course overviewMain issues in UI designProject

Required reading: Dix pp. 1-8.


Course outline

Web page:www.ece.uvic.ca/~aalbu/seng310_summer2007.htm

Bookmark and check frequentlyOffice hours: MR 10:00-11:00 EOW321Otherwise by appointment (email)


Who am I?

Courses taught:summer 2006: Human Computer Interaction (UVic)spring 2006: Fundamentals of Computer Vision (UVic)2005: Introduction to Virtual Reality (Laval)2004: Computer Vision for Video Understanding (Laval)

Research:- Computer vision- Pattern recognition- Image processing- Vision-based (perceptual) user interfaces


What is Computer Vision?[Computer vision] started as a branch of artificial intelligence,and it turned out to be a multifaceted and complex issue." Roberto Manduchi, Dept. Of Computer Engineering, University of California, Santa Cruz

Original goal of vision : understanding a single image representing a static scene ( object identification, structure retrieval etc.)

Most recent trend: video understanding (motion representation, activity recognition, tracking, optical flow etc.)

Real-time video understanding finds many applications in user interfaces.


Raw input data for liver cancer reconstruction

2D segmentation


Human motion analysis

Motion is at the core of human behavior. For example, we move when we communicate (through facial expressions and gestures), when we interact with each other and with objects in the world.Recovering this motion is necessary if we want computers to understand human actions. It’s not easy! Models : deformable motion, articulated motion. Assumptions: simple background, limited occlusion etc.


Course information

Textbook: Alan Dix, Janet Finley, Gregory Abowd, Russel Beale: Human Computer Interaction, 3rd edition.

Additional readings will be posted on the course website.

SlidesClass attendance


Course objective

To present HCI as a usability engineering process integrating design, implementation, and evaluation.


Introduction to usability

User Interface Hall of Shame


Introduction to usability (cont’d)A more usable alternative

clicking on a checkbox in Click & Print opens a dialog box for entering the information to be printed on a certificate.


The user interface is importantIt strongly affects the perception of software (i.e. ease of use ratings)Usable (user-friendly) software sells betterUnusable web sites are abandonedThe user perception of software is often biased“Oops, I missed the File menu again! How stupid of me.”

adapted from Dr. Rob Miller’s Lecture notes on UI Design and Implementation, MIT 2004.


User Interfaces are hard to design

You are not the user–Most software engineering is about

communicating with other programmers–UI is about communicating with users

• The user is always right–Consistent problems are the system’s fault• …but the user is not always right– Users aren’t designers, and should not be forced to fill

“Yeah, the interface is bad, but users can customize it however they want it.”



User Interfaces are hard to build

User interface takes a lot of software development effort

• UI code accounts for ~50% of:–Design time–Implementation time–Maintenance time–Code sizeMyers & Rosson, “Survey on user interface

programming”, CHI ’92.adapted from Dr. Rob Miller’s Lecture notes on UI Design and

Implementation, MIT 2004.


Usability defined

Usability: how well users can use thesystem’s functionality• Dimensions of usability– Learnability: is it easy to learn?– Efficiency: once learned, is it fast to use?– Memorability: is it easy to remember whatyou learned?– Errors: are errors few and recoverable?– Satisfaction: is it enjoyable to use?



Usability dimensions vary in importance

Depends on the user–Novice users need …–Infrequent users need …–Experts need…

• But no user is uniformly novice or expert– Domain experience– Application experience– Feature experience



Usability is only one attribute of the system

Software designers have a lot to worry about:

– Functionality – Usability– Performance – Size– Cost – Reliability– Security – Standards• Many design decisions involve tradeoffsamong different attributes• We’ll take an extreme position in this class



Usability engineering is a process


In this course, you’ll learn

- how to analyze users and their tasks- how humans perceive and process information- the importance of iterative design (project)- how to build prototypes (project)- how to evaluate UIs

• Expert (heuristic) evaluation• User testing

– current research in user interfaces- how to design a particular type of user interface

(project)


Evaluation

3 midterms 45%2 assignments 20%project 35%

You must pass the combined mid term score in order to pass the class.The assignments must be completed individually. Late assignments will not be accepted.


How to get a good mark

prepare: read materials before you come to classparticipate: ask questions during classdon’t rush through assignmentsProject: do your best for the two intermediate milestones; be a team player; write your final report in a professional way; prepare well for the final presentations and demos


Project: general

One project description for all teamsThe scope of the project is intentionally left open. This way, each group can explore the design space and come up with innovative and original solutions.5% from the project mark (35%) comes from how well your team does compared to other teams.Collaboration between teams is therefore discouraged and will be penalized.


Project: team forming

Teams will be composed of 4 students.Choose your team members. Select a name for your team (optional) and send me an email about the team composition.Email me immediately if you would like to be assigned on a team.I reserve the right to change the team composition (e.g. by adding a new member).


Project: milestones

Task and user analysisMilestone 1: prototype 1 (low-fidelity, i.e. paper prototype)Milestone 2: prototype 2 (high-fidelity, UI must have some functionality)Final report: guidelines will be posted on the web site.Demonstration (in class)


Project: context

In this project, you will design a web-based user interface for professional readersThe project will be done in collaboration with the Humanities Computing group in the Department of Englishhttp://www.youtube.com/watch?v=LRBIVRwvUeETechnical contacts : David Kerr [email protected], Jeff Cockburn


Project: tools

You are free to choose any tool for web design. Hint: choose the one that you are most familiar with, so that you won’t spend most of the time in learning how to use the software. Be sure that your team includes a technical specialist.Design with the user in mind: user requirements gathering (invited lecture: Dr. Ray Siemens)


Project: example from SENG 310 2006

http://www.funland.tiffyn.com/


Next course (Thursday)

History of Human Computer Interaction

SENG 310: Human Computer Interactionaalbu/SENG 310 2007/SENG 310-1.pdfSENG 310 : Human Computer...

Documents

Transcript of SENG 310: Human Computer Interactionaalbu/SENG 310 2007/SENG 310-1.pdfSENG 310 : Human Computer...