itis 6010/8010 principles of human computer interaction dr. heather richter [email protected]

of 41/41
ITIS 6010/8010 Principles of Human Computer Interaction Dr. Heather Richter [email protected]

Post on 02-Jan-2016




0 download

Embed Size (px)


  • ITIS 6010/8010Principles of Human Computer InteractionDr. Heather [email protected]

  • AgendaCourse Info & SyllabusCourse OverviewIntroductionsHCI OverviewEthicsIDEO VideoProject discussion

  • Course InformationBooksHuman Computer Interaction, 3rd edition, by Dix, Finlay, Abowd, Beale. (DFAB)The Design of Everyday Things, by Donald Norman, 2002. (DOET)Web and PoliciesSyllabus and LecturesAssignmentsSwiki

  • Course InformationGrading for 601010% Participation50% ProjectMore details to come20% Midterm20% Final

  • Course InformationGrading for 801010% Participation50% ProjectMore details to come10% Assignment15% Midterm15% Final

  • 8010 AssignmentAdditional reading on a more focused theory or research topicTeach or present the topic 30 minutes in classAt least 20 minutes of presentation2 page (or so) summary and study guide posted to the SwikiSee web pages for suggestions

  • Group project4 parts, each 12.5%3-4 people per group, graded as a groupOriginal interface design and evaluationEach part due by class time on the due dateProject notebook on Swiki with each write up

  • Course AimsConsciousness raisingMake you aware of HCI issuesDesign criticQuestion bad HCI design - of existing or proposedLearn Design ProcessSoftware interfaces and beyondImprove your HCI design & evaluation skillsGo forth and do good work!Introduction to theory and research topics in HCI

  • Course OverviewRequirements GatheringHow do you know what to build?Human abilitiesDesignHow do you build the best UI you can?EvaluationHow do you make sure people can use it?

    Also cognitive and contextual models, interface paradigms, design guidelines, groupware, ubiquitous computing

  • How to do wellTime and effortDo the reading and prepare for classAttend class and participateSpend time on projectAttention to detailCommunicationTell me what you learned and why you made decisions

  • Introductions Dr. Heather RichterPh.D. in C.S. from Georgia Tech in May 2005HCI, Ubiquitous Computing, and Software Engineering focusContact info:Email preferred, put 6010 or 8010 in titleOffice: 305E WoodwardOffice Hours:Thursday 4-6pmBy appointment

  • Introductions Your TurnName, student status, specializationPrevious HCI/interface experience?A product/device/application youLove to use and whyHate to use and why

  • Now lets get started

    What is Human-Computer Interaction?

  • HCIBasic definition:The interaction and interface between a human and a computer performing a taskWhat tasks? Write a document, calculate monthly budget, learn about places to live in Charlotte, drive homeTasks might be work, play, learning, communicating, etc. etc.not just desktop computers!

  • Why do we care?Computers (in one way or another) now affect every person in our societyTonight - count how many in your home/apt/roomWe are surrounded by unusable and ineffective systems!Its not the users fault!!Product success may depend on ease of use, not necessarily powerYou will likely create an interface for someone at some pointEven if its just your personal web page

  • Famous QuotationsIt is easy to make things hard. It is hard to make things easy. Al Chapanis, 1982

    Learning to use a computer system is like learning to use a parachute if a person fails on the first try, odds are he wont try again. anonymous

  • Goals of HCIAllow users to carry out tasksSafely




  • UsabilityImportant issueCombination ofEase of learningHigh speed of user task performanceLow user error rateSubjective user satisfactionUser retention over time

  • UI Design / Develop ProcessUser-Centered DesignAnalyze users goals & tasksCreate design alternativesEvaluate optionsImplement prototypeTestRefineIMPLEMENT

  • Know Thy Users!Physical & cognitive abilities (& special needs)Personality & cultureKnowledge & skillsMotivation

    Two Fatal Mistakes:Assume all users are alikeAssume all users are like the designer

  • Design EvaluationBoth subjective and objective metricsSome things we can measureTime to perform a taskImprovement of performance over timeRate of errors by userRetention over timeSubjective satisfaction

  • Its HARD!Design is more difficult when the designer takes responsibility.

    Think about the user(s), the situation and make the system appropriate.

    Co-evolution makes it even harder.

  • Working with PeopleIssues of rights, respect, ethics

    YOU will be observing and talking to people to:Gather requirementsGet initial design feedbackPerform evaluations of your design

    Important to be professional with any interaction with potential users

  • Why an issue?Usability testing can be arduous; privacy is importantEach person should know and understand what they are participating in:what to expect, time commitmentswhat the potential risks arehow their information will be usedMust be able to stop without danger or penaltyAll participants to be treated with respect

  • IRB, Participants, & EthicsInstitutional Review Board (IRB)Federal law governs proceduresReviews all research involving human (or animal) participantsSafeguarding the participants, and thereby the researcher and universityNot a science review (i.e., not to asess your research ideas); only safety & ethics

  • Ethics CertificationEthics is not just common senseTraining being standardized to ensure even and equal understanding of issues

    Go get your certification:

  • Recruiting ParticipantsWho you are recruitingMust fit user population (validity)How you are recruitingMust adequately disclose purpose and tasksCompensationDoes compensation fit task? Reasonable expectations?

    Note: Maintaining proper ethics applies to all participants, even friends and family

  • ConsentWhy important?People can be sensitive about this process and issues Errors will likely be made, participant may feel inadequateMay be mentally or physically strenuousWhat are the potential risks (there are always risks)?Examples?Vulnerable populations need special care & consideration Children; disabled; pregnant; students (why?)

  • Study procedures and materialsMatch what consent form statesOnly deception when necessary and not harmfulOnly necessary information is gatheredParticipant is not unduly burdenedPrivacy of the gathered dataData to be stored anonymously, securely, and/or destroyed

  • Attribution TheoryStudies why people believe that they succeeded or failed--themselves or outside factors (gender, age differences)

    Make sure participants do not feel that they did something wrong, that the errors are their problem

  • Respecting your participantsBe well prepared so participants time is not wastedMake sure they know you are testing software, not themExplain procedures without compromising resultsMake them aware they can quit anytimeMake sure participant is comfortableSession should not be too longMaintain relaxed atmosphereNever indicate displeasure or angerState how session will help you improve system (debriefing)Dont compromise privacy (never identify people, only show videos with explicit permission)

  • IRB @ UNCC

    On-line tutorialGuidelinesConsent procedures and template formsProtocol application forms

    IRB Protocol 101 Training 10am, 2/1: 5pm, 2/2: 10am & 5pm

  • AgendaCourse Info & SyllabusCourse OverviewIntroductionsHCI OverviewEthicsIDEO VideoProject discussion

  • Project StructureGroup project 3 or 4 peopleWorth 50% of grade, 12.5% per partDesign and evaluate an interface1 - Understand the problem 2 - Design alternatives3 - Prototype & evaluation plan4 Evaluation

  • Project Groups3-4 peopleYou decideDiverse is best!Consider schedules, email habits, etc.

    Cool nameForm by end of class next week

  • Project topicsGroup-oriented picture frame

    Microsoft Interface Design Imagine Cup

    Problem of your choice

  • Programming requirementsLeverage team expertise

    Full functionality is NOT intention

    But good evaluation requires authentic experience

  • Project adviceThink of someone elseAvoid being biased by your intuitionsThink off the desktop too!Mobile, handheld, environmentalThink everydayHomeThink about people first, then technology

  • Previous ProjectsSystem for organizing and showcasing artMall kioskFriend Finder on a cell phoneSystem to assist real estate agents with directions and details for showing housesSystem for assisting anesthesiologistsCampus companionUniversity remote control for a hotel roomMoney tracker in your wallet

  • Course ReCapTo make you notice interfaces, good and badYoull never look at doors the same way againTo help you realize no one gets an interface right on the first tryYes, even the expertsDesign is HARDTo teach you tools and techniques to help you iteratively improve your designsBecause you can eventually get it right

  • Next timeHistory & Paradigms, more project planning

    Read: DFAB 4Activity: project brainstormStart to form groupsThink about project topics