1. CS 3724 Introduction to HCI Dr. Scott McCrickard McBryde 626 mccricks@cs.vt.edu

2. Who are these people? Dr. McCrickard (professor) Dr. McCrickard (professor) assistant professor in CS since 2000assistant professor in CS since 2000 research interests include HCI, notification systems, design reuseresearch interests include HCI, notification systems, design reuse Qing Li (teaching assistant) Qing Li (teaching assistant) Ph.D. student in computer sciencePh.D. student in computer science interested in info vis and data aggregationinterested in info vis and data aggregation Alan Fabian (teaching assistant) Alan Fabian (teaching assistant) Master’s student in computer scienceMaster’s student in computer science interested in notification systems design and evaluationinterested in notification systems design and evaluation

3. What is HCI? The Human The Human Single user, groups, I/O channels, memory, reasoning, problem solving, error, psychologySingle user, groups, I/O channels, memory, reasoning, problem solving, error, psychology The Computer The Computer Desktop, embedded system, data entry devices, output devices, memory, processingDesktop, embedded system, data entry devices, output devices, memory, processing The Interaction The Interaction Direct/indirect communication, models, frameworks, styles, ergonomicsDirect/indirect communication, models, frameworks, styles, ergonomics

4. HCI at VT Scott McCrickard Scott McCrickard Doug Bowman Doug Bowman Chris North Chris North Manuel Perez Manuel Perez Francis Quek Francis Quek Deborah Tatar Deborah Tatar Steve Harrison Steve Harrison Others in CS, ISE, … Others in CS, ISE, …

5. An Aside: VTURCS VTURCS = Virginia Tech Undergraduate Research in Computer Science Work with professors on ongoing research projects. Work with professors on ongoing research projects. Receive travel money to attend conferences. Receive travel money to attend conferences. Present your work at annual symposium. Present your work at annual symposium. Attend the Project Fair in mid-fall for details (see http://vturcs.cs.vt.edu for details)

6. Three VTURCS Opportunities Notification systems designer Notification systems designer In-depth look at notification systems designIn-depth look at notification systems design Extends work done in this classExtends work done in this class Contact Dr. McCrickard for detailsContact Dr. McCrickard for details LINK-UP system programmer LINK-UP system programmer Implement usability engineering toolsImplement usability engineering tools Paid positionPaid position Contact Dr. McCrickard or Edwin Bachetti for detailsContact Dr. McCrickard or Edwin Bachetti for details ADVANCE web interface developer ADVANCE web interface developer Develop web-centric applications and interfacesDevelop web-centric applications and interfaces Help with the dissemination of information about female participation in grad schoolHelp with the dissemination of information about female participation in grad school Paid positionPaid position Contact Dr. McCrickard or Jamie Smith for detailsContact Dr. McCrickard or Jamie Smith for details

7. History and Future of HCI Much of the class will consider systems that are in use today Much of the class will consider systems that are in use today Class projects may speculate on emerging (but feasible) paradigms Class projects may speculate on emerging (but feasible) paradigms To understand present and future, start with the emergence of HCI To understand present and future, start with the emergence of HCI

8. History of HCI Vannevar Bush, 1945 “As We May Think” Vannevar Bush, 1945 “As We May Think” Vision of post-war activities, Memex Vision of post-war activities, Memex “…when one of these items is in view, the other can be instantly recalled merely by tapping a button” “…when one of these items is in view, the other can be instantly recalled merely by tapping a button”

9. History of HCI (con’d) JCR Licklider, 1960 “Man-Computer Symbiosis” JCR Licklider, 1960 “Man-Computer Symbiosis” Tightly coupled human brain and machine, speech recognition, time sharing, character recognition Tightly coupled human brain and machine, speech recognition, time sharing, character recognition

10. History of HCI (con’d) Douglas Engelbart, 1962 “Augmenting Human Intellect: A Conceptual Framework” Douglas Engelbart, 1962 “Augmenting Human Intellect: A Conceptual Framework” In 1968, workstation with a mouse, links across documents, chorded keyboard In 1968, workstation with a mouse, links across documents, chorded keyboard

11. History of HCI (con’d) XEROX Alto and Star XEROX Alto and Star WindowsWindows MenusMenus ScrollbarsScrollbars PointingPointing ConsistencyConsistency Apple LISA and Mac Apple LISA and Mac Inexpensive High-quality graphics 3rd party applications

12. History (and future) of HCI Large displays Large displays Small displays Small displays Peripheral displays Peripheral displays Alternative I/O Alternative I/O Ubiquitous computing Ubiquitous computing Virtual environments Virtual environments Implants Implants Speech recognition Speech recognition Multimedia Multimedia Video conferencing Video conferencing Artificial intelligence Artificial intelligence Software agents Software agents Recommender systems Recommender systems......

13. Why Usability Engineering? Need an iterative discovery-oriented process Need an iterative discovery-oriented process But at the same time need to manage itBut at the same time need to manage it Demands well-defined process with metrics Demands well-defined process with metrics Specifying usability goals as objectivesSpecifying usability goals as objectives Assessing and redesigning to meet these objectivesAssessing and redesigning to meet these objectives Manage usability as a quality characteristic, much like modularity or nonfunctional requirementsManage usability as a quality characteristic, much like modularity or nonfunctional requirements

14. How Do We Do It? Need to capture, communicate, store, share, and reuse knowledge Need to capture, communicate, store, share, and reuse knowledge …and be able to find it again later!

15. How Do We Do It? Need to capture, communicate, store, share, and reuse knowledge Need to capture, communicate, store, share, and reuse knowledge WordsWords PapersPapers BooksBooks LibrariesLibraries …and be able to find it again later!

16. Scenarios in UE: A Simple Example A student, Akbar, is working on a research paper in the lab. While working on the paper, he wishes to be informed of happenings in his community. Akbar uses the Notification Collage (NC), running on a second monitor, to inform him of such information with occasional glances. When shuffling through items on the NC, he sees that a project partner has found information of immediate relevance. Fortunate to learn this, Akbar includes the information in his paper, finishing early. A scenario describing a situation:

17. Scenario-Based Development 1.3: Make decisions but keep options open. scenarios are concrete descriptions but are also very flexible 1.4: Analyze use but let it evolve. scenarios describe use in detail, but as a tentative, working representation 1.5: Be innovative but only if adding value. scenarios focus on the usability consequences of specific design proposals 1.6: Be precise but include everyone on the team scenarios describe the problem situation using natural language understood by all stakeholders 1.7: Balance action with reflection. scenarios offer a vivid description of use that provokes questions and “what if” discussions Why Scenarios?

18. Scenarios and Claims Scenarios convey what actors are like, what forces influence their behavior Scenarios convey what actors are like, what forces influence their behavior Claims elaborate on scenarios, explaining how and why a feature has impacts Claims elaborate on scenarios, explaining how and why a feature has impacts Claims analysis documents why scenarios were written by isolating the most important features Claims analysis documents why scenarios were written by isolating the most important features

19. Scenarios and Claims Organizing information using the collage metaphor + allows users to informally post information + accommodates a wide range of different information types - BUT the lack of organization can hinder efforts to read/see a particular item - BUT overlapping items may force users to shuffle through them

20. Tradeoffs and SBD Design by definition is invention, creativity Design by definition is invention, creativity Never just one approach, never one correct answerNever just one approach, never one correct answer BUT some answers are demonstrably betterBUT some answers are demonstrably better Interactive system design tremendously complex Interactive system design tremendously complex Many interdependencies, eg schedule, cost, competitive advantage, local expertise,...Many interdependencies, eg schedule, cost, competitive advantage, local expertise,... Users and their needs are one large set of dependenciesUsers and their needs are one large set of dependencies Tradeoffs are useful in analyzing these relations Tradeoffs are useful in analyzing these relations Here, we focus on tradeoffs affecting users’ experiencesHere, we focus on tradeoffs affecting users’ experiences Guides design thinking, also serves as design rationaleGuides design thinking, also serves as design rationale

21. How Should We Measure Usability? Bottom line is whether the users got what they wanted, i.e., is the client satisfied Bottom line is whether the users got what they wanted, i.e., is the client satisfied Practically speaking, need to break this down so that we can operationalize our objectives Practically speaking, need to break this down so that we can operationalize our objectives Our textbook definition: Our textbook definition: The quality of an interactive computer system with respect to ease of learning, ease of use, and user satisfaction Can the users do what they want to do in a comfortable and pleasant fashion?Can the users do what they want to do in a comfortable and pleasant fashion?

22. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders, field studies Usability specifications Activity scenarios Interaction scenarios iterative analysis of usability claims and re-design metaphors, information technology, HCI theory, guidelines formative evaluation DESIGN ANALYZE PROTOTYPE & EVALUATE

23. Learning SBD — By Example Virtual science fair as a case study Virtual science fair as a case study Complement to real world science fairsComplement to real world science fairs Goal to extend interactions across time & spaceGoal to extend interactions across time & space Cumulative, illustrates activities at each phase Cumulative, illustrates activities at each phase Examples of methods used in projectsExamples of methods used in projects Use as model for group materials & analysesUse as model for group materials & analyses Many details specific to this example Many details specific to this example E.g., collaboration, community network, educationE.g., collaboration, community network, education Other case studies under construction on the Web at http://ucs.ist.psu.eduOther case studies under construction on the Web at http://ucs.ist.psu.edu http://ucs.ist.psu.edu

24. Scenarios in Usability Engineering Stories of people and their activities, sometimes includes computer use, always includes goals Stories of people and their activities, sometimes includes computer use, always includes goals Typical elements of the story are: Typical elements of the story are: A settingA setting One or more actors or agentsOne or more actors or agents An orienting or motivating goal or objectiveAn orienting or motivating goal or objective Mental activity, plans or evaluation of behaviorMental activity, plans or evaluation of behavior A “storyline” sequenced by actions and eventsA “storyline” sequenced by actions and events Emphasis on use, i.e., people’s needs, expectations, actions, and reactions Emphasis on use, i.e., people’s needs, expectations, actions, and reactions

25. Course Overview Lectures and activities Lectures and activities Individual homework assignments Individual homework assignments Readings Readings Tests Tests Design project Design project

26. Textbook Mary Beth Rosson and John M. Carroll, Usability Engineering: Scenario-Based Development of HCI (RC) Mary Beth Rosson and John M. Carroll, Usability Engineering: Scenario-Based Development of HCI (RC)

27. Other Useful Books Ben Shneiderman, Designing the User Interface Ben Shneiderman, Designing the User Interface Deborah Hix and Rex Hartson, HCI Deborah Hix and Rex Hartson, HCI Don Norman, Design of Everyday Things Don Norman, Design of Everyday Things Fred Brooks, The Mythical Man Month Fred Brooks, The Mythical Man Month

28. Other Resources Email is the best way to contact Dr. McCrickard (mccricks@cs.vt.edu), Qing (qili4@vt.edu), and Alan (alfabian@cs.vt.edu) Email is the best way to contact Dr. McCrickard (mccricks@cs.vt.edu), Qing (qili4@vt.edu), and Alan (alfabian@cs.vt.edu) Blackboard contains lecture slides, assignments, signup sheets, discussion boards, and related materials Blackboard contains lecture slides, assignments, signup sheets, discussion boards, and related materials The listserv (cs3724_xxxxx@listserv.vt.edu) is used only for time-sensitive postings by the professor and GTAs The listserv (cs3724_xxxxx@listserv.vt.edu) is used only for time-sensitive postings by the professor and GTAs

29. Evaluation Group project (60%) Group project (60%) Homeworks (15%) Homeworks (15%) Activities (10%) Activities (10%) Midterm (5%) Midterm (5%) Final (10%) Final (10%) Extra credit (up to 3%) Extra credit (up to 3%)

30. Project Overview Group project with 4-5 people per group Group project with 4-5 people per group Projects will be graded per team, with a component of the grade based on individual effort as reported by members Projects will be graded per team, with a component of the grade based on individual effort as reported by members Choose groups carefully – think about when they can meet, where they live, what their skills are Choose groups carefully – think about when they can meet, where they live, what their skills are Maintain and post material on a project Web site (email location to coordinator) Maintain and post material on a project Web site (email location to coordinator)

31. Project Topics All topics will relate to the emerging field of notification systems All topics will relate to the emerging field of notification systems All projects will be centered around a common theme (probably navigation- related) All projects will be centered around a common theme (probably navigation- related) Flexibility in terms of platforms, languages, targeted users, etc. Flexibility in terms of platforms, languages, targeted users, etc. More details next week More details next week

32. Adminstrivia Force-adds and prerequisite forms Force-adds and prerequisite forms Prerequisite is CS 2604, REQUIREDPrerequisite is CS 2604, REQUIRED Everyone must complete the forms TODAYEveryone must complete the forms TODAY Must attend today AND WednesdayMust attend today AND Wednesday Add decisions by next meetingAdd decisions by next meeting

33. Adminstrivia Force-adds and prerequisite forms Force-adds and prerequisite forms Prerequisite is CS 2604, REQUIREDPrerequisite is CS 2604, REQUIRED Everyone must complete the forms TODAYEveryone must complete the forms TODAY Must attend today AND WednesdayMust attend today AND Wednesday Add decisions by next meetingAdd decisions by next meeting

34. For Wednesday Buy the Rosson and Carroll book (if you haven’t already) Buy the Rosson and Carroll book (if you haven’t already) Read Chapter 1 Read Chapter 1 Look through the whole book Look through the whole book HW 1 to be assigned on Wednesday HW 1 to be assigned on Wednesday