September 22, 2019 Sam Siewert

CS415Human Computer Interaction

Lecture 6, Part 2 – Implementation and Testing Tools for HCIs

Minute Paper Summary - Biggest GUI ChallengesCoding [11]

– “especially when there are lots of use cases”– “I find the coding to be the largest challenge … chances of errors”– “While libraries are great, significant amounts of time must be spent”– “designing and planning out how it will work is easy for me, it’s just the software portion I

dislike”– “trouble converting the logic into actual code”, “coding specifically OpenCV, QtCreator editor”

Look and Feel (Prediction of Success) [11]– “the biggest problem is making something that looks and feels good to use”– “making a GUI that a majority of people think looks good”– “While people in the industry can develop and interface that they think is ideal, the user

may/will have different expectations…”– “majority may not like what was presented … not too different from the norm”– “creating an HCI that’s ‘fun’ to interact with”– “reluctant to change if the old model still works”– “hard tot determine a right/wrong when it comes to look/feel”

Design (Interaction) [9]– “appealing to the user and easy to use”, “intuitive with efficient design”– “calculator is already fairly efficient so it was difficult to think of improvements”– “intimidating due to so much interaction”– “think about your audience and make design choices based on that”– “not every use is going to use the same UI the same way”, “coming up with an idea”

Testing [4]– “when another user gets involved and starts to test it … Then I have to go about

perfecting…”, “if no working code can be generated, can’t test”

Sam Siewert 2

Minute Paper Summary - The GurusDon Norman said …1. Make it fun (6)2. Make it visually appealing, beauty (5)3. Visceral (3)4. Emotions matter (2)5. We know good design when we see it6. Not practical, but we want it anyway7. Form over function

Tony Fadell said …1. Think young (7)2. Stay a beginner, as if you are seeing for first time, easy (6)3. Habituation - acceptance blinds us from improvement (3)4. Dumb stickers and small problems (2)5. Think about details (nobody else has)6. Focus on easy tasks and designs

Sam Siewert 3

Coming Up…Quiz– Material since first Quiz – Chapters 5,6,7,8,9– On Canvas for practice

Review before Exam #1

Exam #1 – Chapters 1-9– Knowledge and Concepts – True/False, Multiple-Choice, Short

Answer– Problem Solving – Analysis, Design, Implementation, Test

Sam Siewert 4

Window ManagersContext for all Applications– Windows 7,8, 10– Linux / Unix X-Windows

UbuntuRed Hat (Centos)Fedora

– Mac OS-X– Android OS– iOS

Sam Siewert 5

Client/Server Window ManagersWindow Managers like X-Windows are Client/Server– Applications are

Clients of the Window Manager

– The Server is the Window Manager

Sam Siewert 6

X-Window SystemC programmingLow-Level to Widget LevelGUI Code GeneratorsX Series – O’ReillyDouglas Young BookX ProtocolXlibX toolkitX Widget Set (Motif, Athena)

Sam Siewert 7

Apple Macintosh Windowing SystemMacintosh and Mac SE (1984-89)– Graphics Toolbox (ROM code for Drawing and Widgets)– Common Look and Feel– Simplified Programming for Interactive GUI/WIMP Applications

Sam Siewert 8

Human-Computer Interaction,3rd Edition, by Alan Dix, Janet Finlay, Gregory Abowd, Russell Beale

X-Windows

Sam Siewert 9

Windowing System Widget SetsWindows

OS-X

Unix / Linux

Sam Siewert 10https://en.wikipedia.org/wiki/List_of_widget_toolkits

Mobile DevelopmentAndroid Studio for AOS

Phone Emulators

SDK - Java Apps

Linux NDK(Native Development Kit) – Skia Graphics Engine, SGL

Sam Siewert 11

Mobile ConsiderationsLocation / time aware, Sensors (magnetometer, sound, camera)Outdoor and indoor use (sunlight), Security/Privacy, Cloud portalNew Interaction Modes - Android Auto (NLP, Telematics), wearables

Sam Siewert 12

Widget Application UpdatesInteractive DesignEvent HandlersEvent MasksRegister Call-backUpdate State

Sam Siewert 13

WIMP InteractionToolkit Interaction Widgets and Gadgets Simplify Development

Sam Siewert 14

Class HierarchyOO is Helpful, but Not RequiredX-Windows is Object-based C code

Sam Siewert 15

Early Interactive Systems Development(Smalltalk - OO)

Smalltalk and Model-View-Controller Interactive System Programming – Xerox PARC Early 1980’s

Sam Siewert 16

Modern OO Interactive System Development

Java Swing, AWT, NetBeans

Python, PyTk

Qt Creator (C++)

Visual Studio WinForm (C#)

X-Windows (Object-based, but not OOP)

Many more … Java, Ruby, Objective-C, C++, C#, Python Sam Siewert 17

Interactive System EvaluationTesting – Traditional SQAUsability However is a Specialized form of Testing and EvaluationField Tests with Users (Human side of HCI)

Sam Siewert 18

Cognitive WalkthroughSimilar to Code Walkthrough, but with Focus on “how easy a system is to use”– Cognitive Load– Efficiency and Ability to Complete Tasks (User Community)

Normally requires a Mock-up or Prototype

Sam Siewert 19

Evaluation MethodAnswer 4 Questions for Each Step in Action Sequence (Task specified as a Goal)

Sam Siewert 20

1) Effect of Action Matches User Goal?

2) Action Visibility / Availability?

3) Recognition of Actions for Goals?

4) Visible Easy to Understand Feedback for Goal Attainment?

How to Measure? - HeuristicNielsen’s Ten Heuristics

1. Visibility of Status2. System / Real-World

Match3. User Control / Freedom4. Consistency / Standards5. Error Prevention6. Recognition over Recall7. Efficiency8. Aesthetic – Less is More9. Design for Error10. Built-in Help

Sam Siewert 21

Empirical Methods of EvaluationParticipants – Real Users, Sample Size, Small and in Depth vs. Large and Shallow (Within or Between)

Variables – Those that are Changed for each evaluation (independent or IV) and those that are Measured(dependent or DV)– E.g. Complete Task with WIMP GUI Widget #1– Complete Same Task with CLI– Task Time, Efficiency and Correct Outcome Measured DVs– CLI vs WIMP GUI Widget - IV Changed is Interaction Method

Hypothesis – Prediction of Outcome (to Test)– If Differences in Measure can’t be Explained by Chance (Null

Hypothesis is Disproven)– Outcomes Compared with Level of Significance (Sample Size,

Mean, Standard Deviation, Reliability, Confidence, T-test) Sam Siewert 22

Empirical Methods of EvaluationExperimental Design – Between-subjects and within-subjects– Between Subjects is Ideal, but Costly (need more subjects)– Within Subjects is lower Cost, but Subjects learn, develop a bias,

and results can be impacted

Sam Siewert 23

General Usability – Statistical Measures

Looking to Serve the Majority of Users - SignificanceE.g. Can Most or Majority of Users Efficiently Complete a Test Task?

Sam Siewert 24

Statistics – Mapping to HCIIndependent Variable (what is changed in each experiment)Dependent Variable (not changed – e.g. goal or task)Analysis Technique (math to determine significance of results and model)

Sam Siewert 25

Human-Computer Interaction,3rd Edition, by Alan Dix, Janet Finlay, Gregory Abowd, Russell Beale

Icon Experiment from Book

Sam Siewert 26

Evaluation through ParticipationObserver and Track User While Experiment is Run– In addition to feedback from user– In addition to other metrics (time, correctness)

Sam Siewert 27

Human-Computer Interaction, 3rd Edition, by Alan Dix, Janet Finlay, Gregory Abowd, Russell Beale

An Automobile-Integrated System for Assessing and Reactingto Driver Cognitive Load, Pompei, Sharon, Buckley, Kemp, http://www.cs.cmu.edu/~dod/papers/pompei02.pdf

Color Coding Example from Book(p. 339)

Sam Siewert 28