Code - submit your J a v a f iles b) D a t a set - collected or simul a ted c) short p a per - (4 p a ges) d) Final presentation video – Sh a re a link to your recorded present a tion. 7
th a t re f lects the m a in topic of the p a per. • Abstr a ct (Option a l) – A brief summ a ry (usu a lly 150–250 words) outlining the p a per’s objective, key f indings, a nd conclusions. • Introduction (1) – Introduces the m a in topic, a nd st a tes the rese a rch question or problem. It should highlight the project purpose a nd signi f ic a nce. WHAT you did a nd WHY • B a ckground (1) – Summ a rizes relev a nt context: BCI or Eye Tr a cking, or XR, or Robotics, even Docker. Things th a t a lre a dy exist a nd you used • Methodology – Brie f ly expl a ins HOW d a t a w a s collected or a n a lyzed or HOW you implemented a n a pplic a tion th a t a d a pt in re a l-time • Discussion/An a lysis (1) – Presents a rguments, evidence, or insights a bout wh a t work a nd wh a t did not. Showc a se your a chievements a nd do not be a fr a id to disclose f a ilures. • Conclusion – Summ a rizes the m a in points, reinforces key f indings, a nd m a y suggest future rese a rch or a pplic a tions. • References (1) – Lists sources cited in the p a per, following the required cit a tion form a t (e.g., APA, IEEE, or MLA). 10
ex a m is comprehensive, encomp a ssing a ll course m a teri a ls. This review covers only a subset of topics. Import a nt: • Ensure you review a ll lecture slides a nd course m a teri a ls. • The following slides include ex a mples rel a ted to selected topics. • This is NOT a n exh a ustive list of ex a m topics. 18
2. Wh a t is a Computer? 3. Wh a t is Inter a ction? 4. Wh a t m a kes a “good” inter a ction? 5. Wh a t m a kes a “b a d” inter a ction? 6. Wh a t is aff ect (emotion, mood)? 7. Wh a t is Ple a sure? 8. Wh a t is Arous a l? 9. Wh a t is Domin a nce? 10.Wh a t we c a lled a n “input”? 22
or thinking”? 12.Wh a t we c a lled a n “output”? 13.Wh a t is us a bility? 14.Wh a t is us a bility engineering? 15.Wh a t is “user friendly”? 16.Wh a t is a cognitive f a ctor? 17. Wh a t is a n interf a ce (user interf a ce)? 18.Provide a n ex a mple of a “good” user interf a ce in a softw a re a pplic a tion 19.Provide a n ex a mple of a “b a d” user interf a ce in a softw a re a pplic a tion 23
attribute time. • The device information includes metrics such as batteryLevel, batteryPercent, wirelessSignal, and sensorsQuality. •For facial actions, attributes like actionEye, actionUpperFace, powerUpperFace, actionLowerFace, and powerLowerFace capture various facial expressions and their intensities. •The emotional metrics encompass a range of states, including engagement, excitement, longTermExcitement, stress, relaxation, interest, and focus. In addition, boolean fl ags, such as isENG, isEXC, isSTR, isREL, isINT, and isFOC, indicate whether speci fi c emotional states are active. •The Pleasure, Arousal, and Dominance (PAD) model is represented through the attributes Pleasure, Arousal, and Dominance. Finally, ignore SAM. 28
a ho? • A set of MQTT client libr a ries developed by the Eclipse Found a tion. • It supports multiple l a ngu a ges, such a s J a v a , Python, J a v a Script, etc. J a v a Dependency (M a ven) <dependency> <groupId>org.eclipse.paho</groupId> <artifactId>org.eclipse.paho.client.mqttv3</artifactId> <version>1.2.5</version> </dependency> 36
keep users informed about what is going on, through appropriate, timely feedback. Visibility of System Status 1 The design should speak the users' language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Match between System and the Real World 2 Users often perform actions by mistake. They need a clearly marked "emergency exit" to leave the unwanted state. User Control and Freedom 3 Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. Consistency and Standards 4 Good error messages are important, but the best designs prevent problems from occurring in the first place. Error Prevention 5 Minimize the user's memory load by making elements, actions, and options visible. Avoid making users remember information. Recognition Rather Than Recall 6 Shortcuts — hidden from novice users — may speed up the interaction for the expert user. Flexibility and Efficiency of Use 7 Interfaces should not contain information which is irrelevant. Every extra unit of information in an interface competes with the relevant units of information. Aesthetic and Minimalist Design 8 It’s best if the design doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks. Help and Documentation 10 Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution. Recognize, Diagnose, and Recover from Errors 9 Nielsen Norman Group
Size 2. Motion: onset, looming, unpredict a ble, depicted 2. Motion: c a p a city, body, n a tur a l, 3. Agents: f a ces, bodies, a nim a ls 4. Sp a ti a l Cues: Eye g a ze, pointing, a rrows 4. Sp a ti a l Cues: direction a l words 5. High Arous a l 6. Unexpectedness: Novelty 7. Self-relev a nce: your n a me, your f a ce, 8. Go a l-relev a nt: no-go a l 8. Go a l-relev a nt: go a l-directed 42
s ment a l a bility th a t in f luences how individu a ls process, a n a lyze, use inform a tion to inter a ct with their environment. • Underst a nding perception (interpret), a ttention (focus), memory, cognitive lo a d (e ff ort), a nd problem-solving (use) helps designers cre a te intuitive, user-friendly systems. • Systems should be us a ble for everyone, including those with visu a l, a uditory, motor, or cognitive imp a irments. 44
rec a ll inform a tion while inter a cting with a system • Short-term memory (Working Memory): Tempor a ry stor a ge of inform a tion, such a s remembering a menu p a th or a recently entered p a ssword. • Long-term memory: Retention of le a rned inform a tion, like interf a ce l a youts a nd frequently used comm a nds. Interf a ces should minimize reli a nce on memory. E.g. by using cle a r n a vig a tion, tooltips, a nd recogniz a ble icons. 45
a nd f ilter out distr a ctions. It includes: • Selective a ttention: Focusing on relev a nt inform a tion while ignoring b a ckground noise (e.g., distinguishing key a lerts in a cluttered d a shbo a rd). • Divided a ttention: M a n a ging multiple t a sks simult a neously (e.g., using multiple a pps on a split-screen). • Sust a ined a ttention: M a int a ining focus over a long period (e.g., re a ding a long document). Well-designed interf a ces should guide a ttention. 46
a ke sense of sensory input (e.g., visu a ls, sounds, touch). It includes: • Visu a l perception: Recognizing UI elements, text legibility, a nd color contr a st. • Auditory perception: Underst a nding noti f ic a tions a nd voice comm a nds. • H a ptic perception: Inter a cting through touch feedb a ck (e.g., vibr a tion responses). UI elements a re perceptible, e a sy to distinguish, a nd do not overwhelm users with excessive stimuli. 47
within a n interf a ce, such a s troubleshooting errors, n a vig a ting complex softw a re, or completing t a sks with minim a l instruction. Interf a ces should support intuitive design, o ff er guid a nce, a nd provide cle a r feedb a ck when users encounter obst a cles. 48
multiple options b a sed on a v a il a ble inform a tion, preferences, a nd p a st experiences. Ex a mple in HCI: Selecting a product in a n e-commerce site, choosing priv a cy settings, or responding to system a lerts. Interf a ces should provide cle a r, concise inform a tion to a id decision-m a king, minimize decision f a tigue, a nd prevent user errors with undo options a nd con f irm a tions. 49
whole body a s a medium for eng a gement with digit a l environments. • Theoretic a l b a sis: physic a l sp a ce, a nd soci a l context in sh a ping hum a n inter a ctions • Immersive Computing, (VR/AR) - users feel fully present • A ff ective Computing - Physical actions c a n gener a te emotion a l st a tes; f a ci a l expressions can enh a nce soci a l a nd emotion a l eng a gement also • The Sensorimotor Loop: body’s movement provides feedback that shapes perception and decision-making. 51
tion of hand tracking, a nd AI-based body estimation to tr a ck the user’s movements. The system prim a rily focuses on head, hand, and body tracking, with emerging techniques for full-body tr a cking. • he a dset itself cont a ins a ll necess a ry sensors to tr a ck motion • Multiple outw a rd-f a cing c a mer a s th a t sc a n the environment a nd detect ch a nges in position. • Uses Simult a neous Loc a liz a tion a nd M a pping (SLAM) a lgorithms to cre a te a m a p of the sp a ce a nd tr a ck the user’s movement within it. • 6 Degrees of Freedom (6DoF): Met a Quest c a n tr a ck position (X, Y, Z) a nd rot a tion (pitch, y a w, roll) of the he a dset a nd controllers in re a l time. 52
needed to run software, including the code, runtime, libraries, dependencies, and configuration files. 3. A container is a runtime instance of an image. It encapsulates the execution environment for a specific application or process, including the filesystem, environment variables, network settings, and runtime options. 1. A text file that contains instructions for building a Docker image
javiergs
tomokusaba
soichi
ivargrimstad
nealle
chimame
mkmk884
u503
tetsuro_b
tmknom
oyasumipants
yuheinakasaka
maroon1st
holman
aki_iinuma
thoeni
sergeychernyshev
jnunemaker
aarron
chrisshort
samlambert
brettharned
samanthasiow
eileencodes
bermonpainter
![Dr. Javier Gonzalez-Sanchez [email protected] www.javiergs.info o ffi ce: 14 -227](https://files.speakerdeck.com/presentations/b0ab8f104e644c12acc89f3c7966140a/slide_0.jpg){kind=link}
![CSC 486 Human-Computer Interaction Javier Gonzalez-Sanchez, Ph.D. [email protected] Winter 2025](https://files.speakerdeck.com/presentations/b0ab8f104e644c12acc89f3c7966140a/slide_59.jpg){kind=link}