What is the precise distinction between
Try it free
Try studying this deck
Flashcards · Quiz · Match · all 10 cards · no account needed.
Cards (10)
- 1Front
What is the precise distinction between usability and user experience (UX) in HCI?
BackUsability is a measurable attribute of a system focused on effectiveness, efficiency, and satisfaction in achieving specific goals. UX is broader, encompassing all perceptions, emotions, and responses a user has before, during, and after interacting with a system, including aspects beyond task completion such as aesthetics and meaning.
- 2Front
How does the concept of 'learnability' in HCI differ from 'memorability', and why does the distinction matter?
BackLearnability measures how quickly a novice user can reach proficiency with a system. Memorability measures how well an infrequent user can re-establish proficiency after a period of non-use. The distinction matters because optimizing for one can trade off against the other; a system with many shortcuts may be powerful but harder to remember after gaps.
- 3Front
In HCI design principles, what is the difference between a 'guideline' and a 'heuristic', and which carries more prescriptive weight?
BackA heuristic is a general rule of thumb used to evaluate interface design (e.g., Nielsen's 10 heuristics), applied especially in expert reviews. A guideline is a more specific, context-bound recommendation often tied to a platform or domain standard. Guidelines typically carry more prescriptive weight because they are more concrete and actionable.
- 4Front
What is the relationship between HCI and accessibility, and why can accessibility not be treated as a post-hoc add-on?
BackHCI's goal of making systems usable for all users inherently includes users with disabilities. Accessibility must be designed in from the start because retrofitting it disrupts interaction models, information architecture, and underlying code, often requiring costly rework and resulting in inferior, bolted-on solutions rather than seamlessly integrated inclusive design.
- 5Front
What distinguishes the UI from the UX in the context of HCI, and what is a common misconception about their relationship?
BackThe UI (User Interface) refers to the tangible points of interaction—visual layout, controls, typography, and screen elements. UX is the holistic experience resulting from those interactions and beyond. A common misconception is that improving visual UI automatically improves UX; in reality, a polished UI can still produce poor UX if the underlying interaction model, task flow, or information architecture is flawed.
- 6Front
What is 'Gulf of Evaluation' in HCI, and how does it differ from 'Gulf of Execution'?
BackThe Gulf of Execution is the gap between a user's intended action and the actions available in the system—difficulty in knowing how to act. The Gulf of Evaluation is the gap between the system's output and the user's ability to interpret whether their goal was achieved—difficulty in understanding feedback. Both concepts originate from Donald Norman's action cycle theory.
- 7Front
Why is Fitts' Law relevant to HCI interface design, and what are its practical design implications?
BackFitts' Law states that the time to acquire a target is a function of the distance to and size of the target (T = a + b log2(2D/W)). In UI design, this means interactive targets (buttons, links) should be large and placed close to common cursor positions. Edge and corner positions are strategically valuable because screen boundaries act as infinite-size barriers, reducing pointing time.
- 8Front
What is the difference between formative and summative evaluation in HCI, and at what stage of design is each applied?
BackFormative evaluation occurs during the design process to identify usability problems and inform iterative improvements—it shapes the design. Summative evaluation occurs after design completion to measure whether the system meets defined usability criteria—it judges the outcome. Using only summative evaluation without formative stages risks discovering unfixable problems too late.
- 9Front
How does 'affordance' differ from 'perceived affordance' in HCI, and why does the distinction have critical design consequences?
BackAn affordance is an actual property of an object that enables a specific action (e.g., a button can be pressed). A perceived affordance is the user's belief about what actions are possible, which may not match reality. Critically, design succeeds or fails based on perceived affordances—if a clickable element doesn't look clickable, the actual affordance is irrelevant to user behavior.
- 10Front
What is 'error tolerance' as an HCI principle, and how does it differ from 'error prevention'?
BackError prevention involves designing interfaces that make mistakes difficult or impossible to commit (e.g., disabling invalid options, confirmation dialogs). Error tolerance accepts that errors will occur and focuses on limiting their consequences—enabling easy recovery, undo actions, and graceful degradation. Both are necessary: prevention reduces frequency, tolerance reduces severity and recovery cost.
Study this deck free
Create a free account to flip through these flashcards, quiz yourself, play match, and track what you've mastered — or fork the deck to make it your own.