I made this with my 3 partners for my CEC marks in 3rd sem of MCA. It includes information about HCI, definition, types, how it works, queries of it etc. One can get idea easily about HCI after refering this presentation.

1. Human Computer Interaction
Meet Maulik Dharit Hardik
Shah Shah Sanghvi Pipaldara

2. Major Points
• Understanding Human-Computer Interaction
• Types of User Interfaces
• Guidelines for Dialog Design
• Designing Queries
2

3. Understanding Human-Computer
Interaction (HCI)
• Ensuring system functionality and usability, providing effective user
interaction support and enhancing a pleasant user experience.
• Its goal is to achieve Organizational and Individual use effectiveness
and efficiency.
• The main method of HCI in system analysis and design is to
frequently get feedbacks from users about their experiences with
prototyped design, refining the design based on the suggested
changes and doing this again and again until the design is
acceptable and feedback is being positive.
3

4. Terminologies
• Fit
• Task
• Performance
• Well-Being
4

5. Fit:
• Basically a “ fit ” can be known as “ a perfect match ”.
• A good fit between the HCI elements of the human, the
computer and the task that needs to be performed leads to
performance and well-being.
• Better fit is meant to result in better performance and greater
overall well-being for the human involved system.
5

6. 6

7. Task
• A task is a structure or unstructured , complex or simple
routine which is done under an environment.
• Complex tasks that require human, system, and task
interaction are supported by ecommerce and Web systems, ERP
systems, and wireless systems inside and outside of the
organization.
Performance
• A combination of the efficiency involved in performing a task
and the quality of the work that is produced by the task.
• If the performance in the task is good then the performance of
its outcome will be good as well.
7

8. Well-Being
• Concern for a human’s overall comfort, safety and health.
• Physical and Psychological aspects are also taken care.
•E.g. Using CASE Tools for producing DFDs on a computer
serves well-being to an analyst cause it’s a “ best fit “ of the
analyst, software objective and computer. An analyst is working
in an environment where s/he is physically comfortable and
psychologically inspired to be creative and productive.
8

9. The Technology Acceptance Model
(TAM)
• It was proposed by Davis in 1989 and was refined and improved by
Davis and others.
• Its an approach to organize thinking about whether the user will
accept and use the information technology.
• It can be used before the system is developed or after the system is
developed but for both the purpose is different.
9

10. • If TAM is used before development of system
then it will be accomplished on the 2 keys.
– Ease of use
– Usefulness
• If TAM is used after development then it will be
used to shape a training program.
10

11. Designing for cognitive styles of
individual users
• Making sure data is made available in different forms
– Tables
– Graphs
– Text
11

12. Pivot Tables
• Allows a user to arrange data in a table in any way they choose
• Gives users greater control over how they look at data in different
ways within a table.
12

13. 13

14. Physical Considerations in HCI
Design
• Vision
– HCI prospective tells to think on the limitation of human vision.
– Factors such as distance from display to a person, angle of vision, color, font
size, type of display, uniformity and placement etc.
• Hearing
– In an office noisy dot matrix printers and phone conversation will lead to
overload hearing and personnel ipod players or noise canceling headphones
will diminish their skill of work.
– Analyst needs to consider noise while designing the office system.
14

15. Physical Considerations in HCI
Design
• Touch
– Touch is all about the input devices that are used to enter data in a system.
– For this the well know interfaces are Key board, mouse, touch screen, stylus
touch etc.
– According to the requirement these devices are updated to serve well-being
to the users.
15

16. Considering Human
Limitations, Disabilities, and Design
• Users of a computer system may be having some disabilities or
some physical limitation.
• HCI approaches special software packages, hardware devices and
concepts that can serve well-being to such special users.
16

17. • Blind or those with low vision
– Braille keyboards
– Special software that reads Web pages and other
documents aloud
– Screen magnifiers
• Deaf or impaired hearing
– Include access to written versions of the audio
material
– Headphones
17

18. • People with limited mobility
– Use of speech input rather than keyboard
– Use of see spot in place of mouse (Bio Medical)
18

19. Implementing good HCI practices
• Matching the user interface to the task.
• Making the user interface efficient
• Providing appropriate feedback to users
• Generating usable queries
19

20. Interface Design Objectives
• Match the user interface to the task
• Make the user interface efficient
• Provide appropriate feedback to users
• Generate usable queries
• Improve productivity of computer users
20

21. Types of User Interfaces
• Natural-language interfaces
• Question-and-answer interfaces
• Menus
• Form-fill interfaces
• Command-language interfaces
21

22. • Graphical User Interfaces (GUIs)
• Web interfaces
22

23. Natural-Language Interfaces
• Permit users to interact with the computer in their everyday or
"natural" language
• Implementation problems and extraordinary demand on computing
resources have so far kept natural-language interfaces to a
minimum
23

24. Question-and-Answer Interfaces
• The computer displays a question to the user on the display
• The user enters an answer through mouse click or keyboard
stroke
• The computer acts on that input information in a preprogrammed
manner
• Users unfamiliar with applications may find question-and-answer
interfaces most comfortable
24

25. 25

26. Menus
• Provides the user with an onscreen list of available selections
• Not hardware dependent
• Can be put aside until the user wants to use them
• Can be nested within one another to lead a user through
options in a program
• GUI menus
• Object menu
26

27. 27

28. GUI menus are used to control PC
software and have following guidelines:
• The main menu bar is always displayed
• The main menu uses single words for menu items. Main menu
options always display secondary pull-down menus.
• The drop-down menus that display when a menu item is clicked
often consist of more than 1 word.
• Menu items in grey are unavailable for current activity.
28

29. Form-Fill Interfaces
(Input/output Forms)
• Onscreen forms or Web-based forms displaying fields containing data
items or parameters that need to be communicated to the user
• Advantage
– The filled-in form provides excellent documentation
• Disadvantage
– Users experienced with the system or application may become
impatient
29

30. 30

31. Command-Language Interfaces
• Allows the user to control the application with a series of
keystrokes, commands, phrases, or some sequence of these
• Affords the user more flexibility and control
• Require memorization of syntax rules
• May be an obstacle for inexperienced users
31

32. 32

33. Graphical User Interfaces
• Provide users constant feedback on task accomplishment
• Continuous feedback on the manipulated object means that
changes or reveals in operations can be made quickly without
incurring error messages
• An appropriate model of reality or an acceptable conceptual model
of the representation must be invented
33

34. Other User Interfaces
• Pointing devices
• Touch-sensitive screens
• Speech recognition and synthesis
34

35. Guidelines for Dialog Design
Key-points for designing good dialogs:
• Meaningful communication
• Minimal user action
• Standard operation and consistency
35

36. Meaningful communication
• It is because the computer understand what the people are entering
and people understand what the computer is presenting. (e.g.)
• The system should present information clearly to the user.
• An appropriate title for each display, minimizing the use of
abbreviations and providing clear user feedback.
• Data in an edited format. (e.g. date , amount fields)
• The cursor may change shape depending on the work being performed.
36

37. • Web-sites must display more text and instruction to guide the user
through the sites.
• Images must be used with the pop-up text or little bit description and
all images must be labeled.
• Status line is an another way of providing instruction for users.
• Tool-tip is helpful to identifying the function of a command button.
37

38. Minimal User Action
• Keying codes instead of whole words (e.g.)
• Entering data that are not already stored on files (e.g.)
• Supplying the editing characters (e.g. date , amount field)
• Using default values for fields on entry screens
• Designing an inquiry, change, or delete program so that the user needs
to enter only the first few characters of a name or item description
• Providing keystrokes for selecting pull-down menu options
38

39. • Use radio buttons and drop-down lists to control displays of new Web
pages or to change Web forms
• Provide cursor control for Web forms and other displays so the cursor
moves to the next field when the right number of characters has been
entered
39

40. Standard operation and consistency
• Locating titles, date, time, and operator and feedback messages in the
same places on all displays
• Exiting each program by the same key or menu option
• Canceling a transaction in a consistent way
• Obtaining help in a standardized way
• Standardizing the colors used for all displays or Web pages
40

41. • Standardizing the use of icons for similar operations
• Using consistent terminology in a display or Web site
• Providing a consistent way to navigate through the dialog
• Using consistent font alignment, size, and color on a Web page
41

42. Description:
This tab control dialog box has seven tabs. The chosen tab
“Paper” appears as if it is in front of the other tabs
42
back

43. 43
back

44. 44
back

45. 45
back

46. 46
back

47. Designing Queries
• Help reduce users’ time spend in querying the database
• Help them find the data they want
• Six different types of queries are among the most common
47

48. It Is Possible to Perform Six Basic Types of Queries on a Table that
Contains Entities, Attributes, and Values
48

49. Query Types
Query Type 1
• What is the value of a specified attribute for a particular entity?
• The purpose of the query is to find the value.
• Query Notation
• V  (E, A)
49

50. V  (E, A)
Query Type 1 – What did employee number 72888 make in year 2009?
50

51. Query Types
Query Type 2
• What entity has a specified value for a particular attribute?
• Because values can also be numeric, it is possible to search for a value
=,>,>=,<,<= etc…
• Query Notation
• E  (V, A)
51

52. E  (V, A)
Query Type 2 – What employee(s) earned more than $50,000 in 2009?
52

53. Query Types
Query Type 3
• What attribute(s) has a specified value for a particular entity?
• Query Notation
• A  (V, E)
53

54. A  (V, E)
Query Type 3 – What years did employee number 72845 make over
$50,000?
54

55. Query Types
Query Type 4
• List all the values for all the attributes for a particular entity.
• Query Notation
• All V  (E, all A)
55

56. all V  (E, all A)
Query Type 4 – list all the details in the earnings history file for employee
number 72888.
56

57. Query Types
Query Type 5
• List all entities that have a specified value for all attributes.
• Query Notation
• All E  (V, all A)
57

58. all E  (V, all A)
Query Type 5 – List all employees whose earnings exceeded $50,000 in
any of the years available.
58

59. Query Types
Query Type 6
• List all the attributes that have a specified value for all entities.
• Query Notation
• All A  (V, all E)
59

60. all A  (V, all E)
Query Type 6 – List all the years for which earnings exceeded $40,000 for
all employees in the company.
60

61. Building More Complex Queries
• Arithmetic operations are performed first
• Exponentiation
• Either multiplication or division
• Addition or subtraction
• Comparative operations are performed
• GT, LT , and others
• Boolean operations are performed
• AND and OR
61

62. Query Methods
• Query By Example (QBE)
– The database fields are selected and displayed in a grid, and
requested query values are either entered in the field area or below
the field.
• Structured Query Language (SQL)
– uses a series of words and commands to select the rows and
columns that should be displayed in the resulting table.
62

63. Query By Example Using Microsoft Access
63

64. Structured Query Language (SQL) for the CUSTOMER NAME
Parameter Query (Figure 14.23)
64

65. THANK YOU !!!