CHAPTER 8: IMPLEMENTATION SUPPORT

1. Introduction

 Transition from abstract design to practical coding.

 Importance of programming support for interactive systems.

2. Elements of Window Systems

 Enable device independence through abstract terminals.

 Support simultaneous tasks via resource sharing.
 Allow imaging models for output interpretation and input event handling.

3. Programming Paradigms

 Read-Evaluation Loop:
 Control is internal to the application.
 Each event must be handled by the application.
 Can be tedious and error-prone.
 Notification-Based Programming:
 Control flow is external; events are managed by a notifier.
 Applications register callback procedures for event handling.
 Reduces the burden of event processing within the application code.

4. Toolkits

 Provide predefined interaction objects (widgets).

 Promote consistency in design across applications.
 Trade-offs:
 Customization vs. maintaining toolkit integrity.

5. User Interface Management Systems (UIMS)

 Purpose:
 Offer higher-level abstraction for interactive system design.
 Separate semantics of applications from user interface design.
 Advantages of Separation:
 Portability: Reuse applications across different systems.
 Reusability: Components can be reused, reducing costs.
 Multiple Interfaces: Develop various interfaces for the same functionality.
 Customization: Interfaces can be tailored for effectiveness without changing
underlying application.
6. UIMS Conceptual Architecture

 Major components:
 Application: Manages core functionality.
 Presentation: Handles user interface appearance and interactions.
 Dialog Control: Regulates communication between application and presentation
layers.
 Key models:
 Seeheim model, MVC (Model-View-Controller), PAC (Presentation-Abstraction-
Control).

7. Implementation Considerations

 Distinction between logical and implementation concerns in UIMS.

 Techniques for dialog control:
 Menu networks
 State transition diagrams
 Event languages

8. Graphical Specification Languages

 Make programming accessible for non-experts.

 Potential downside: Loss of expressiveness in coded functionality.

Key Concepts to Remember

 High-level tool support simplifies coding for interactive systems.

 Different programming paradigms affect how interactions are controlled.
 UIMS framework separates application logic from user interface concerns.
 Familiarity with visual specification can aid in understanding practical
development

CHAPTER 9 ON EVALUATION TECHNIQUES IN HUMAN AND

COMPUTER INTERACTION:
 Introduction to Evaluation:
 Evaluation should occur throughout the design life cycle.
 Distinction between designer/usability expert evaluations and actual user studies.
 Goals of Evaluation:
 Assess system functionality and accessibility.
 Evaluate user experience of interaction.
 Identify specific usability problems within the system.
  Expert Analysis Approaches:
 Cognitive Walkthrough: Detailed review of user actions to accomplish tasks.
Evaluators ask questions about user goals, action visibility, and feedback
understanding.
 Heuristic Evaluation: Critique based on established usability principles
(heuristics). Evaluators independently assess usability problems, scoring
severity.
 Model-based Evaluation: Uses cognitive and design models for integrated
design and evaluation.
 Using Previous Studies: Reuse data from similar prior evaluations to inform
new designs.
 User Participation in Evaluation:
 Laboratory Studies (LS): Controlled tests in usability labs; advantages and
disadvantages in context.
 Field Studies (FS): Observes users in their natural environment; offers natural
use insights but potential interruptions.
 Empirical Methods: Experiments to test hypotheses with controlled variables.
Importance of representative participant selection and appropriate sample sizes.
 Observational Techniques:
 Think Aloud: Users verbalize their thoughts during task execution.
 Protocol Analysis: Various methods for recording user actions (e.g., video,
audio).
 Post-task Walkthrough: Discussing actions with users post-observation.
 Query Techniques: Gather direct feedback through interviews and
questionnaires; emphasize pilot studies for testing.
 Physiological Monitoring: Eye tracking and other physiological responses to
gauge cognitive processing and emotional response.
 Choosing Evaluation Methods: Consider design stage, laboratory vs. field,
subjective vs. objective measures, qualitative vs. quantitative data, timing,
intrusiveness, and available resources.

Summary:

 Evaluation tests usability, functionality, and acceptability of interactive systems

using various approaches and methods tailored to specific needs in the design
process.

Chapter 10: Universal Design

10.1 Introduction

 Definition: Universal design involves creating products to be usable by as many

people and in various situations.
 Application to HCI: It means designing interactive systems that anyone can use,
regardless of ability, utilizing any technology platform.
 Strategies for Implementation:
 o Built-in redundancy
o Compatibility with assistive technologies

10.2 Universal Design Principles

 Established by a group at North Carolina State University in the late 1990s,

seven principles guide the framework for developing interactive systems:
1. Equitable Use: Design should be beneficial for diverse abilities; access
should be equal without exclusion or stigmatization.
2. Flexibility in Use: Allows choices in methods of use, adapting to user's
pace, precision, and preferences.
3. Simple and Intuitive Use: Interfaces should be understandable
regardless of user attributes; feedback should be provided.
4. Perceptive Information: Communicate effectively under various
conditions, accommodating user abilities.
5. Tolerance for Error: Design minimizes negative impacts of user errors or
unintended actions.
6. Low Physical Effort: Systems should require minimal physical exertion to
reduce fatigue and discomfort.
7. Size and Space for Use: Ensure accessibility for users of all sizes and
mobility levels.

10.3 Multi-modal Interaction

 Concept: Interaction involving multiple sensory channels enhances user

experience by mimicking natural human interactions.
o Increases interaction bandwidth.

10.3.1 Sound in the Interface

 Audio Confirmation: Effective in reducing errors, integrating both speech and

non-speech elements.
o Speech in the Interface:
 Structure of Speech: Consists of phonemes and their variations
(prosody and co-articulation).
 Speech Recognition: Challenges due to language complexity and
external noise; limited success but increasing usage.
 Speech Synthesis: Struggles with natural intonation; beneficial for
users with disabilities.
 Uninterpreted Speech: Can be useful through recorded sounds
without needing computer processing.
o Non-speech Sounds: Quick to assimilate, independent of language, but
require learning their meanings.
 Examples include naturally occurring sounds and abstract sounds
(Earcons).
10.3.2 Touch in the Interface

 Haptic Interaction: Touch provides critical information, particularly for users with
visual impairments.
o Devices used include electronic braille and force feedback systems.

10.3.3 Handwriting Recognition

 Methods: Captured via digitizer tablets or electronic paper; recognition varies

significantly between individuals.

10.3.4 Gesture Recognition

 Challenges in recognizing user-dependent gestures; often captured through data

gloves.

10.4 Designing for Diversity

 Considerations for Various Impairments:

o Visual Impairment: Use of sound and touch.
o Hearing Impairment: Interface usage minimally affected.
o Physical Impairment: May need alternative inputs like speech recognition
or eye-gaze systems.
o Speech Impairment: Multimedia offering synthetic speech and text
options aids communication.
o Dyslexia: Minimizing text reliance, employing voice input and checking
tools.
o Autism: Facilitates communication through impersonal computer
interaction.

10.4.1 Designing for Different Age Groups

 Older People: Need clear, simple designs due to mobility issues.

 Children: Require special considerations in both software and hardware for
limited coordination.

10.4.2 Designing for Cultural Differences

 Considerations: Variations in symbols, gestures, reading direction, and color

meanings must be accounted for in design.

Summary

 Universal Design: Systems designed for usability by anyone under varying

circumstances while promoting inclusivity.
 Multi-modal Systems: Integrating multiple input channels like speech, non-
speech sound, touch, handwriting, and gestures.
 Diversity Consideration: Important to address needs of individuals with
sensory, physical, or cognitive impairments, different ages, and cultural
backgrounds.