Hci Final

Front 1

Model Human Processor

Back 1

three systems (perceptual system (input), motor system (output), cognitive system), each system has its own memory and processing

Front 2

differences between human and computer

Back 2

easier to identify/parameterize, fewer simplifications/approximations necessary, general familiarity

Front 3

batch processing

Back 3

create a program using punch cards, place cards into a reader (or give to an operator), return later for output

Front 4

rich interaction

Back 4

interaction occurs in fraction of a second, communication from remote machines, no limitation as to location

Front 5

list keyboards

Back 5

QWERTY, DVORAK, Chorded, One-handed

Front 6

Handwriting Recognition

Back 6

easy for user, especially technology novices, keyboard-free, can be inaccurate (but improving), handwriting is very individual, handwriting is slow by comparison to typing

Front 7

Speech Recognition

Back 7

easy to use, fast, external noise interference/contribution, sensitive to context changes (whisper, cold), difficulty with large or strange vocabularies

Front 8

Touch-Sensitive Screens

Back 8

fast, intuitive, occlusion, fingers can contaminate screen, "gorilla arm"

Front 9

Eye Gaze

Back 9

intuitive, no occlusion at all, no limb movement required, more error prone than mouse, "Midas Touch", expensive

Front 10

Dedicated Displays

Back 10

Large display (errors), no single point of failure, static layout may not accommodate all users, difficult to change

Front 11

Moore's Law

Back 11

processor speed doubling every 18 months, memory doubling every 12 months

Front 12

Execution-Evaluation (EEAC)

Back 12

goal, Execution(form intention, specify the action sequence, execute the action sequence), evaluation(perceive the system state, interpret the system state, evaluate the system state with respect to goals and intentions)

Front 13

Gulf of Execution

Back 13

a gap between user goals/intentions and the system's ability or support for these actions

Front 14

interaction framework

Back 14

user -> articulation -> input -> performance -> system -> presentation -> output -> observation

Front 15

why is interaction framework better than EEAC

Back 15

has distinct execution and evaluation steps for user and system, potential system distances can be ascribed to a particular translation step, lower difficulty is desirable, system difficulty is preferable to user difficulty

Front 16

mental model

Back 16

internal formulation about how something works, allows mental simulation of a device or process, often derived from past experience, often an approximation

Front 17

5 properties of mental models (Heim)

Back 17

unscientific (based on guesswork & approximation), partial (do not describe full systems, just relevant aspects), unstable (not concrete formulations, but adaptable), inconsistent (do not necessarily form cohesive model; some parts may be incompatible with others), personal (specific to each individual)

Front 18

WIMP

Back 18

Windows, Icons, Menus, Pointers

Front 19

The Golden Rule of Design

Back 19

Understand your materials {human (capabilities, limitations, tendancies), computer (available technology, mainstream systems)}

Front 20

The Process of Design

Back 20

Front 21

Stakeholders

Back 21

primary stakeholders (people actually using the system), secondary stakeholders (people who do not directly use the system, but receive output from it or provide input to it), tertiary stakeholders (people who do not fall into either primary or secondary categories, but who are directly affected by success or failure of system), facilitating stakeholders (people who are involved with system design, development, and maintenance)

Front 22

requirements gathering options

Back 22

Structured Interviews, Focus Groups/Workshops, Participatory Design, User-Initiated Requirement Gathering, Designer-Initiated, Contextual Enquiry, Cultural Probes,

Front 23

Structured Interviews

Back 23

a meeting between a designer(s) and a user(s), Advantages (prepared questions can be supplemented with clarifying questions, users supply information that is not anticipated by the designer) Disadvantages (time consuming, intimidating)

Front 24

Focus Groups/Workshops

Back 24

a group of users meet together with a designer to discuss requirements, Advantages (similar advantages to interviews, less time consuming from designer perspective) Disadvantages (time consuming, feedback can be unbalanced)

Front 25

Participatory Design

Back 25

users become a part of the design team, Advantages (users typically understand needs better than anyone, users 'own' the design – are likely to use the design) Disadvantages (sometimes not possible (e.g. Geographical constraints), users often do not understand technological capabilities and constraints)

Front 26

Personas

Back 26

a rich description of a person(s) who represents your core user group , not all details are relevant to your interface design  rather, the detail is to make the person seem as real as possible  some authors suggest attaching an anonymous photo to the persona, to enhance the realism

Front 27

Analysis

Back 27

Objectives:  distilling key requirements from information gathering  determining further requirements  ordering requirements by importance  eliminating unneeded design features  evaluating effectiveness of current design  identifying gulfs in current design
Techniques:  task analysis (later)  interaction modeling/analysis

Front 28

Interaction Analysis

Back 28

a general study of an interaction that will take place between user and interface

Front 29

Design

Back 29

where we determine an interface that facilitates the required interaction

Front 30

C.R.A.P. Design

Back 30

Contrast, Repetition, Alignment, Proximity
a set of principles used when designing interfaces

Front 31

Gestalt Principles

Back 31

proximity  similarity  continuity  closure

Front 32

Colour Application - Guidelines

Back 32

simplicity, consistency, clarity

Front 33

Four colour schemes

Back 33

Monochromatic (all colors in the design have same hue ), Complementary (two hues used, one from either side of colour wheel), Analogous (several colours close together on the colour wheel ), Triadic (three colours that are somewhat equidistant from each other on the colour wheel )

Front 34

Exact Organization Schemes

Back 34

alphabetical, chronological, geographical

Front 35

Ambiguous Organization Schemes

Back 35

topical, task-oriented, audience-specific

Front 36

techniques for discovering categorizations in content

Back 36

Card Sorting , Affinity Diagramming

Front 37

Navigation Design

Back 37

a computing application allows users to accomplish some goal, goal accomplished through a task (or sequence of tasks), four guidelines: (user should know current state, user should know available actions, user should know consequence of potential actions, user should know consequence of previous actions)

Front 38

Design Rules

Back 38

1) Principles  abstract design rules  low authority/high generality
2) Guidelines  general design rules  less abstract, and often more technology oriented, than principles  low authority/high generality
3) Standards  specific design rules  high authority/low generality

Front 39

Design Principles

Back 39

Learnability (Predictability, Synthesizability Familiarity, Generalizability, Consistency), Flexibility (dialog initiative, Multi-threading, Task Migratability, Substitutivity, Customizability), Robustness (observability, recoverability, responsiveness, task conformance)

Front 40

Shneiderman's 8 Golden Rules

Back 40

1) Strive for consistency 2) Cater to universal usability 3) Offer informative feedback 4) Design dialogs to yield closure 5) Prevent Errors 6) Permit Easy Reversal of Actions 7) Support Internal Locus of Control 8) Reduce Short-term Memory Load

Front 41

Design to Implementation

Back 41

assumes: that our data gathering has obtained all relevant information for our design  that our analysis phase has perfectly determined the tasks that need to be supported  that the design developed from this analysis perfectly accommodates all tasks and all users

Front 42

Iterative Design

Back 42

we need not be perfect the first time around  omissions or mistakes in the design can be corrected  users can be re-consulted

Front 43

Benefits of Prototyping

Back 43

 it is often difficult to describe (in words) a task that needs to be performed  with a prototype, a user/designer can better articulate their ideas  prototypes typically allow some type of interaction  these interactions can be analyzed to determine shortcomings in the design, which can then be addressed

Front 44

Design Dimensions

Back 44

an interface design can be defined along two dimensions*  features – how many features the interface has  this is typically referred to as the horizontal axis  functionality – how much functionality the interface has  this is typically referred to as the vertical axis

Front 45

prototype fidelity

Back 45

resemblance to the final product

Front 46

Evaluation

Back 46

tests the usability, functionality, and acceptability of an interactive system

Front 47

Experimental Evaluation

Back 47

often used when testing new design ideas , can include both observational and query techniques

Front 48

controlled experiment components

Back 48

 hypothesis (es)  variables  participants  experimental design  data measurement  data analysis

Front 49

Factorial Design

Back 49

a design applicable in experiments with multiple independent variables (eg. age, GPS user)

Front 50

Randomization

Back 50

participants randomly assigned to a condition or treatment order whenever possible, however, participant attributes counterbalanced across conditions if possible

Front 51

Systematic Errors

Back 51

 measurement instruments  experimental procedures  participants/experimenter  experimental environment

Front 52

Significance Testing

Back 52

 the use of statistical probability when a decision is made about a hypothesis  a typical part of experimental evaluation process  results of significance testing is typically reported when publishing results

Front 53

Significance Tests

Back 53

 Z-test  Student's t-test  Analysis of Variarance (ANOVA)  Χ2 test

Front 54

choosing a statistical test for comparing means

Back 54

Front 55

Why Non-User Evaluation

Back 55

resource constraints may limit testable users  time, geography, budget, availability

Front 56

Cognitive Models

Back 56

an attempt to model a user as they interact with an interface

Front 57

Keystroke-Level Model

Back 57

used to approximate the time performance of the user on a particular task

Front 58

User Participation – Laboratory studies

Back 58

 advantages:  sophisticated recording  interruption-free environment  easier for controlled experiments
 disadvantages:  lack of work environment context  user may perform "unnaturally"

Front 59

User Participation – Field studies

Back 59

 user evaluates design in environment where it will actually be used  designer/moderator is still present, but comes to the user

Front 60

User Participation – Remote Testing

Back 60

 users are separated from evaluators by space, time, or both  advantages:  users/designers can work asynchronously  permits the use of large user bases  enables testing from users that might not otherwise participate (e.g. disabled)  disadvantages:  harder for designer to pick up non-verbal and interpersonal cues from user

Front 61

User Participation – Measurement

Back 61

task performance , time performance , user satisfaction , time to recover from error  time spent in help  number of visits to search  keylogging, # of websites visited, mouse movements, etc.

Front 62

User Participation – Approaches

Back 62

 Observational  users are observed interacting with system  Query-based  users are queried regarding the design

Front 63

User Participation – Tasks

Back 63

 what the user will perform during testing
task lists: [ should be clear and unambiguous  critical tasks should be included, even if not frequently used (e.g. logout)  should be as all-inclusive as possible (e.g. utilize menus, toolbars, and shortcuts)]

Front 64

Observation Techniques – User Involvement

Back 64

refers to the user's involvement in the data collection, outside of his/her normal activities  the role of the user can be:  small: user performs tasks, designer observes and records  large: think aloud (can affect task time

Front 65

Data Collection

Back 65

Manual Methods (Paper and Pencil), Audio/Video recording, computer logging(users actions on sytem recorded), instrumenting(add measurement tools to known software)

Front 66

Query-based Evaluation Techniques

Back 66

Interviews/Focus Groups, Questionnaires/Surveys

Front 67

Universal Design

Back 67

designing products so that they can be used by as many people as possible in as many situations as possible

Front 68

Diversity

Back 68

User-based • gender • experience • culture • age • accessibility. Technology-based • hardware (PC, laptop, handheld device) • connectivity (modem, broadband) • operating system • browser • software

Front 69

impairments that affect interface design

Back 69

 sensory (e.g., visual, auditory)  motor (e.g., CTS, paralysis)  cognitive (e.g. dyslexia)

Front 70

Universal Design – Gender

Back 70

females often show less confidence than males with technology  females attribute failure at a task to a lack of capability  males attribute failure at a task to the difficulty of the task  women typically more risk averse than men  males less likely than females to thoroughly read complicated or lengthy “help” explanations.