A2 Level ICT

1
A2 Level ICT

• 14.6 Human/Computer Interaction

2
Human-Computer Interaction (HCI)

• Human
• the end-user of a program
• other people in the organization
• Computer
• the machine the program runs on
• Interaction
• the user tells the computer what they want
• the computer communicates results

3
Factors Influence
Now that mice are included with most computers,
applications assume a mouse will be used as a the
pointing device
? change in technology
People change their knowledge as they perform,
i.e., they learn
? change behavior
4
User Interfaces

• Part of a software program that allows
• user to interact with computer
• user to carry out their task
• HCI design, prototyping, evaluation, and
  implementation of user interfaces (UIs)

5
Hall of Shame!
6
More Bad Examples

• Netscape

7
Small File Dialog Boxes
8
Attributes of Good UIs

• Invisible
• Minimal training required - easy to learn
• High transfer of training - easy to remember
• Predictable
• Few errors
• Easy to recover from errors
• Allow people perform real tasks well - efficient
• Flexible
• Seem intelligent - do the right thing
• People like it - It is easy to make things hard.
  It is hard to make things easy.

?
9
Guidelines for Good UIs

• Follow graphic design principles
• Use language conventions
• Minimize use of short-term memory
• Design for consistency
• Provide feedback
• Prevent errors provide error correction

10
Good Graphic Design Color Choice (cont.)

• Group related objects
• alignment spacing
• decorations

• Balance white space
• Few fonts colors (5 to 7 colors max.)
• Remember color deficiency (8 of males)

11
Be Consistent

• Size, color, wording, location, ordering...
• Avoid special cases complex rules
• Same command always has same effect
• Following standards helps. Examples?
• e.g., Cut/Copy/Paste
• Seems, easy but often not followed. Why good?
• allows user to generalize

12
Speak the Users Language

• Use common words, not techno-jargon
• bad example

• Allow full-length names

13
Less is More

• Keep it simple
• Concise language
• Avoid extraneous pictures information
• fewer options and menu choices
• reduces planning time (mental)
• reduces manual size, etc.

14
Minimize User Memory Load
?

• Short-term memory. Capacity decay?
• capacity of 7 2 decay of 30 sec. to 2 min.
• Recognize, not recall (generate)
• Menus rather than type-in
• Prompts provide formats
• Dont require retyping remembered info.
• Pervasive, generic rules
• cut/copy/paste

15
Psychological Factors

• User friendly
• Novices
• Experts
• Memory
• Peer pressures
• Different backgrounds experience - users who
  have used other types of system
• Different satisfaction/dissatisfaction with
  system familiarity
• IT phobia
• Different social attitudes to IT environment
• Low user self-confidence
• Sounds that are attributed to certain commands
• Choice of colour schemes - combinations to
  reflect mood
• HCI complexity nature - can frustrate expert
  users

16
Factors to consider when designing for
human/computer interaction

• Factor - User friendly
• Making the system accessible to the widest
  audience
• Use icons in a meaningful way, so that users are
  not frustrated
• Have easily navigable screen layouts
• Provides a consistent look and feel so that
  skills are transferable between packages
• So that the system is intuitive so that the user
  feels comfortable, and the system is easy to use

17
Factors to consider when designing for
human/computer interaction

• Factor - Help mechanisms
• Using context sensitive help means that the user
  has a consistent method of getting aid
• Use of wizards can help users to complete most
  parts of a complex task by guiding them through
  the required stages
• Use of tips/assistants can point out alternative
  methods of completing a task that may benefit the
  user Built in demonstrations can show users how
  to complete complex/unfamiliar tasks
• Error messages provided by the system should not
  only be of assistance to programmers, but also to
  end-users so that they can see what has gone
  wrong and why

18
Factors to consider when designing for
human/computer interaction

• Factor - Shortcuts
• A user is familiar with a process/piece of
  software they want to complete tasks efficiently
• In order to support productivity, users should
  have the facility to customise toolbars/menus so
  that commonly used tasks are easily accessible
• The ability to use alternative input methods for
  commands such as ctrl-P for print can aid
  efficiency

19
Factors to consider when designing for
human/computer interaction

• Factor - Long-term memory
• Use standard menu items/keystrokes will help
  the end-user by reducing the amount of time
  needed to learn how to use a package

20
A2 Level ICT

• 14.7 Human Computer Interface

21
Advantages of a standardised approach

• Ease of learning training material can be
  written to match workstation HCI
• Easier transfer of skills to new packages if
  interface is maintained
• Consistency of interface maintained when users
  move between workstations
• Better self support between users
• Standard settings for defaults Word starting
  each sentence with a capital letter
• Easier distribution/use of standardised items
  such as templates/logos, etc

22
Advantages of a standardised approach

• Level of skills for different users standard
  may suit less able but not highly skilled
• Have to wait for changes in software
  configuration rather than do it themselves
• May not be able to use favourite specialised
  software unless it is included in standard
• Standard colour sets may not be appropriate for
  colour build or other disabilities
• User no longer has control over their own desktop
  environment plus expansion
• Either need for additional training/support or
  user may be confused plus expansion

23
Features of a sophisticated HCI

• On-line help
• Complex user interface
• GUI
• Multitasking
• Faster searching for on-line help
• Effective use of colour
• Well designed command/menu structures taking into
  account skills, with shortcut keys for
  experienced users
• Use of a range input/output devices appropriate
  to situation e.g. graphics tablet, plotter, etc
• User friendliness takes account of skills and
  terminology used by End users

24
Resource Implications of sophisticated HCI

• Need to upgrade some workstations if they cannot
  support standard
• Upgrades may include hard drive, screen
• May involve moving s/w from local workstation to
  a server
• May involve increased n/w traffic
• Need to upgrade server storage capacity to
  accommodate move of apps., from workstation to a
  server
• Need to upgrade n/w infrastructure from ring to
  star
• Time consideration for restructuring
• Use of staff for restructure
• Time lost during changeover
• N/W management software enables this change to
  occur

25
Implications for Customising Software for a
Specialist HCI

• More time will taken up in support - as staff
  will have to identify which icons perform which
  task
• Changes made by the users may have other
  consequences this may be difficult/impossible
  for support staff to assess without access to
  users system
• Workers that share desks dont recognise the
  environment - and support staff are not aware of
  what has been changed