BTCOE504 (A):

HUMAN COMPUTER INTERACTION

PROF. A.B.DESAI
UNIT 3: IMPLEMENTATION SUPPORT

• What Is Implementation Support?

• When creating an interactive system (like a software application that
users interact with), it's crucial to understand not just how the system
should look and function but also how to turn those ideas into actual
working software.
• The Challenge
• Initially, we focused on the design and overall plan of the interactive
system without worrying about the nitty-gritty details of the hardware
or specific devices. However, to make the system work in reality, we
need to address these details.
• Translating Design to Code
• Specification to Code:
• You have a detailed plan or specification for what the application should do.
• The programmer's job is to translate this plan into code that the computer can
execute.

• Low-Level Coding:
• At a basic level, coding involves reading input from devices (like a mouse or
keyboard) and displaying output on the screen.
• This process can be tedious and prone to errors because it's very detailed and
specific to the hardware.
ELEMENTS OF WINDOWING SYSTEMS

• What Are Windowing Systems?

• Windowing systems are software frameworks that help manage how multiple
applications interact with the user and with each other on a computer screen. They
enable graphical interfaces, like the ones you see in most modern operating systems
(e.g., Windows, macOS, Linux).
• Key Features of Windowing Systems
• Hardware Independence:
• Abstract Terminal: Device Drivers:

• Imaging Models:
• Imaging Model: Primitives: Input Handling:
• Input Events: TManaging Multiple Applications:
• Multiple Windows:
• Resource Sharing:
ARCHITECTURES OF WINDOWING
SYSTEMS
• Replicated Management:
• Each application manages its own windows and processes. This approach is less
efficient and portable because each app has to handle its own resource management.

• Kernel-Based Management:
• The operating system’s core (the kernel) manages windowing and resource sharing.
This makes apps easier to manage but ties them closely to the operating system.

• Client–Server Architecture:
• Client–Server Model: The window management is handled by a separate system (the
server) that communicates with applications (the clients). This is the most portable
model because the server provides a generic interface for any application.
PROGRAMMING THE APPLICATION

• Two programming paradigms which can be used to organize the flow of

control within the application. The windowing system does not
necessarily determine which of these two paradigms is to be followed.
• read–evaluation loop: which is internal to the application program itself
• notification based: which the main control loop for the event processing
does not reside within application
USER INTERFACE MANAGEMENT SYSTEMS

• The set of programming and design techniques which are supposed to add
another level of services for interactive system design beyond the toolkit level
are user interface management systems, or UIMS
• The main concerns of a UIMS, for our purposes, are:
 a conceptual architecture for the structure of an interactive system which
concentrates on a separation between application semantics and presentation;
 techniques for implementing a separated application and presentation whilst
preserving the intended connection between them;
 support techniques for managing, implementing and evaluating a run-time
interactive environment.
THE LOGICAL COMPONENTS OF A UIMS
WERE IDENTIFIED AS
1. Presentation The component responsible for the appearance of the interface, including
what output and input is available to the user.

2. Dialog control The component which regulates the communication between the
presentation and the application.

3. Application interface The view of the application semantics that is provided as the
interface.
EVALUATION TECHNIQUES:
EVALUATION TESTS THE USABILITY, FUNCTIONALITY AND ACCEPTABILITY OF AN INTERACTIVE
SYSTEM.
EVALUATION MAY TAKE PLACE: – IN THE LABORATORY – IN THE FIELD.

• Some approaches are based on expert evaluation:

1. – analytic methods
2. – review methods
3. – model-based methods
• Some approaches involve users:

1. – experimental methods
2. – observational methods
3. – query methods.
• An evaluation method must be chosen carefully and must be suitable for the
job.
GOALS OF EVALUATION:
THREE MAIN GOALS
To assess the extent and accessibility of the system’s functionality,

• To determine if the system provides the necessary features and

functions required by users to complete their tasks.
To assess users’ experience of the interaction

• To evaluate how users interact with the system and their overall
satisfaction with the experience.
To identify any specific problems with the system.

• To pinpoint particular issues within the system that cause problems or

confusion for users.
EVALUATION THROUGH EXPERT ANALYSIS

• Involves assessing a system using specialized knowledge rather than

direct user testing. This approach can be applied at various stages of
design and offers a cost-effective way to identify potential issues.
 Application
Method Purpose Method Focus Requirements
Stage
Detailed
Experts simulate design/prototyp
Learning
Cognitive Evaluate ease of user actions to e,
process and Early design to
Walkthroug learning for new complete a task representative
user prototype
h users and check for task, list of
interaction
usability issues actions, user
experience info
Multiple experts
Design
Identify usability independently
Adherence to Several specifications,
Heuristic problems based review the system
usability evaluators (3-5), prototypes, fully
Evaluation on general using usability
principles set of heuristics implemented
principles guidelines
systems
(heuristics)
Experts use
Predict and cognitive/design Quantitative Specific
Model-
evaluate user models (e.g., predictions of cognitive/design Throughout design
Based
performance GOMS, keystroke- user models, detailed process
Evaluation
using models level model) to performance design info
assess design
Apply findings
Experts review and Application of Access to Any stage,
Using from existing
use research established relevant especially when
Previous research to
findings to inform research literature and validating design
EVALUATION THROUGH USER PARTICIPATION

•Laboratory Studies are useful for controlled, detailed evaluations.

•Field Studies offer insights into real-world use.
•Empirical Methods provide data-driven results on specific hypotheses.
•Physiological Monitoring helps understand physical reactions during use.
Approach Description Advantages Disadvantages Best For
Users test the
May not reflect real-
system in a Evaluating specific
Controlled conditions, world conditions, can
Laboratory controlled interface features,
detailed recording, miss natural
Studies environment, like a controlled
interruption-free. interactions and
usability lab or a experiments.
context.
quiet room.
Observers visit the Can be noisy and
user’s actual work Real-world context, disruptive, Studying natural use,
Field environment to see natural user behavior, observations might be long-term tasks, and
Studies how the system observes interactions influenced by the contextual
performs in real- with actual work tasks. presence of interactions.
world settings. researchers.
Conducting
controlled
Provides precise data, Requires careful design Testing specific design
experiments to
Empirical can test specific and statistical analysis, aspects or
gather data on user
Methods hypotheses and may need many hypotheses with
performance and
variables. participants. detailed data.
system
effectiveness.
Using technology to
Provides objective data
track physical Can be invasive, Understanding deep
Physiologi on user’s physical
responses like eye requires specialized physical reactions,
cal reactions, can reveal
movements, heart equipment and stress, or
Monitoring unnoticed user stress or
UNIVERSAL DESIGN: INTRODUCTION

• Universal design is about designing systems so that they can be used

by anyone in any circumstance.
• Multi-modal systems are those that use more than one human input
channel in the interaction.
• These systems may, for example,
• use: – speech – non-speech sound – touch – handwriting – gestures.
• Universal design means designing for diversity, including:
• – people with sensory, physical or cognitive impairment – people of
different ages – people from different cultures and backgrounds.
 UNIVERSAL DESIGN PRINCIPLES
Principle Description Examples
1. The design should be useful to people with a Curb cuts on sidewalks help wheelchair users
Equitable range of abilities and should not stigmatize and strollers. Automatic doors assist
Use or exclude anyone. everyone, not just those with disabilities.

2. The design should accommodate a variety of A keyboard with customizable key layouts or
Flexibility abilities and preferences, allowing for voice commands that adapt to different
in Use different methods of use. users' needs.
3. Simple The design should be easy to understand
User interfaces with clear icons, simple
and and use, regardless of user knowledge or
instructions, and helpful prompts.
Intuitive experience.
4.
The design should effectively communicate Websites that use text, audio, and visual
Perceptible
information in multiple ways to elements to ensure information is accessible
Informatio
accommodate different abilities. to people with different sensory needs.
n
5. The design should minimize the impact of
Undo buttons in software and error messages
Tolerance mistakes and help users avoid or recover
that guide users on how to fix problems.
for Error from errors.

6. Low
The design should be comfortable to use and Doors with automatic openers or touchless
Physical
require minimal physical effort. faucets that don’t require much effort to use.
Effort
MULTI-MODAL INTERACTION
USER SUPPORT: INTRODUCTION

• Users have different requirements for support at different times.

• User support should be:
– available but unobtrusive– accurate and robust – consistent and flexible.
• User support comes in a number of styles:
– command-based methods – context-sensitive help – tutorial help – online
documentation – wizards and assistants – adaptive help.
• Design of user support must take account of:
– presentation issues – implementation issues
 REQUIREMENTS OF USER SUPPORT
Requirement Description Examples
A help button within a software that opens a
Help should be accessible at all times, without
Availability help panel or window without closing the
needing to close the current application.
main task.
Updated help documentation that matches the
Accuracy and Help content must accurately reflect the current
latest version of the software and covers all
Completeness state of the system and cover all relevant areas.
features.
Help content and presentation should be
Using the same terminology and style in both
Consistency uniform across different parts of the system and
online help and printed manuals.
consistent with other documentation.

The help system should handle errors

A help system that continues to function even
Robustness gracefully and always be available, especially
if the main application crashes.
when the system has problems.
Help should adapt to the user’s needs, Context-sensitive help that provides different
Flexibility providing different levels of assistance based information based on where the user is in the
on their expertise and context. application.
Help that appears in a small, non-intrusive
The help system should not interrupt or
Unobtrusiveness overlay or split-screen that doesn’t disrupt the
interfere with the user's current work.
workflow.
APPROACHES TO USER SUPPORT

•Command Assistance
Meaning: Provides help on specific commands or functions when the user knows what they need.
Example: UNIX man command, which displays documentation for a specific UNIX command.

•Command Prompts
Meaning: Shows help or correct usage when a user makes an error in command input.
Example: A command line interface error message showing the correct syntax after an incorrect
command is entered.

•Context-Sensitive Help
Meaning: Offers help based on what the user is currently working on or where they are in the
application.
Example: Tool-tips in Microsoft Office that display information when you hover over a button.
•Online Tutorials
Meaning: Guides users through tasks or features in an application through interactive lessons or demonstrations.
Example: An interactive tutorial in a software application that walks you through setting up a new project.
•Online Documentation
Meaning: Provides detailed reference materials and instructions available digitally.
Example: An online help guide that includes searchable topics and instructions for a software application.
•Wizards and Assistants
Meaning: Tools that guide users step-by-step through tasks or offer suggestions based on user behavior.
Example: The resume wizard in Microsoft Word that helps you create a resume by asking questions and generating a
template.
•Adaptive Help Systems
Meaning: Customizes help based on the user’s experience level, context, and needs.
Example: A help system that adjusts its suggestions and information based on your recent actions or familiarity with
the application.
ADAPTIVE HELP SYSTEMS

• Adaptive Help Systems are designed to personalize assistance based on the

individual user's needs, experience, and context. Here's a summary of how they
work and some challenges they face:
 How Adaptive Help Systems Work:

• Monitoring User Activity: The system tracks what the user is doing, their
mistakes, and their experience level.
• Constructing a User Model: It builds a profile of the user based on their
interactions, preferences, and familiarity with the system.
• Providing Contextual Help: The system offers help tailored to the user’s current
task and their specific needs or knowledge level.
• Suggesting Alternatives: It may suggest actions or features that the user might
not be aware of but could be relevant.
Challenges:

• Knowledge Requirements: Gathering and interpreting data on user

interactions can be complex and resource-intensive.
• Control and Initiative: Deciding how much control the system should
take in guiding the user without overwhelming or confusing them.
• Adaptivity Scope: Determining what aspects of the system should
adapt and how to handle variations in user expertise across different
parts of the system.