midterm HCI Flashcards
how humans use computer in general
HUMAN COMPUTER INTERACTION
study of HCI began in FACTORIES
1980
provided an in depth interactions between humans and weapons
WWII
start of the HCI study
1949
prioritization of task over work
DERIVE THEORY
3U Principle
USEFUL
USABLE
USED
accomplish what it requires
USEFUL
doing it naturally and easily
USABLE
make the user wants to use it
USED
MODEL HUMAN PROCESSOR - 3 sub systems
Perpetual System
Motor System
Cognitive System
controls actions; joints, muscles, tissues, etc.
Motor System
process information that connects the perpetual and motor system
Cognitive System
eyes are the primary source of information; process/interpret what you see
VISION
VISUAL PERCEPTION - process elements
⁃ FACTORS:
- Size and Depth
⁃ 2. Brightness
⁃ 3. Color
processing of text/ identification of visual patterns
READING
identification of the vibrations of the sound waves
AUDITORY
AUDITORY FACTORS
⁃ 1. Pitch - frequency; highness/lowness
⁃ 2. Loudness - volume of the sound
⁃ 3. Timbre - combination if pitch and loudness
touch; vital information about the environment
HAPTICS
joints
MOVEMENT
SENSORY MEMORIES
⁃ Ionic
⁃ Echoic
⁃ Haptic
⁃ If you give attention to sensory memory you will get a short term memory
⁃ If you give rehearsal, you will get a long term memory
HUMAN MEMORY
3 TYPES OF REASONING
. DEDUCTIVE
INDUCTIVE
ABDUCTIVE
deriving logically necessary conclusions from the given premise
DEDUCTIVE
generalization
INDUCTIVE
presumed until proven otherwise
ABDUCTIVE
no steps, based on experience
GENERALIZATION
step by step
PROCEDURALIZATION
response to the evaluation of the entire situation
EMOTIONAL
easily learned
Learnability
the system should be able to accommodate variety of people depending on user needs
Flexibility
“usable”, used easily and effectively
Efficiency
- easily remembered
. Memorability
inform user about where they had lapses in using the system
Error Handling
- the user should enjoy the system he/she used
User Satisfaction
available for the general public, available to all users with different abilities
Accessibility
the theme, motif that the user requires
USER INTERFACE REQUIREMENT (UI REQ)
model, diagrams, process flows
⁃ validates that all your process will be suitable to the system
GUIDELINE DOCUMENT AND PROCESSES
for presenting the prototypes
UI TOOLS
the system is launched
⁃ this is where they will determine if the system is HCI friendly based on the 7 principles
EXPERT REVIEW AND USER TESTING
cannot compute bigger processes, there is a delay/lag
Computation bound
full storage affects system performance
Storage bound
some systems need dedicated gpus to function normally
Graphics bound
sending of data
Network capacity
easier for the user to use and navigate through the system
. Functional
next, previous, etc.
by sequence
⁃ from one control to another, continuation of the other
Sequential
frequently used controls
Frequency
process of creating interactive applications easy to use for users
INTERACTION DESIGN
DESIGN PRINCIPLES
CONSISTENCY
CENTER OF INTEREST
BALANCE
CONTRAST
maximization/utilization of the design process for it to be accessible to most people
UNIVERSAL DESIGN
during the early days, there are no things like wheelchairs; this is where we considered disabled people started
Disability-Specific Design
the things we cannot do before, we can do it now; innovation allows us to do this
Assistive Technology
caters the specific needs of the user
User Centric Design
Principles in IT
Perceivable - all things should be seen
0. Operable - nagagamit
0. Understandable - can be understood by use
0. Robust - compliant with coding standard
4 PILLARS OF INTERFACE DESIGN
- Clarity - elements are well-understood
0. Consistency - e.g. all throughout it should be blue
0. Responsiveness - navigation
0. Simplicity - ui minimizes the number of events/things that the user needs to do
- evaluation of the intended user to your product
⁃ can be alpha or beta testing
USER TESTING
- they can give you a professional opinion in your development and technicalities of your system
ALPHA TESTING
- they only evaluate the functions of your system
BETA TESTING
covers interactive systems
9241
usability of interactive system (use and efficiency)
9241-11
usability, efficiency, presentation of information (usability, input, and response)
9241-110
design process pertaining to the usability of the system
9241-210
- design principles (consistency, typography, etc)
9241-220
effectiveness, efficiency, satisfaction
9241-300
- 8 quality characteristics
⁃ functionality, reliability,
⁃ security and compatibility
⁃ software quality evaluation
25010
- same as 25010 but without compatibility and security
9126
after you finish, you test the code
⁃ “code build test”
Unit testing
if the approach is modular and needs integrated
Component Testing
done after the integration of one testing to another
Integration Testing
test the availability of system
Performance Testing
the system is done, you are just adding new system and you must be able to test it first if the changes are suitable to your existing components
. Sanity Testing
all the buttons of your system must be clickable
Smoke Testing
