Test your basic knowledge |

Human Computer Interaction

Subject : engineering
Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. 1.free phase 2.captive phase 3. termination phase






2. User interface independence 1.They separate interface design from internals 2.They enable multiple user interface strategies 3. They enable multiple platform support 4. They establish the role of the user interface architect 5. They enforce standards






3. Task analysis - storyboarding - use cases - primary stakeholder profiles






4. Intention formation - specification of the action - and the execution stages are complex - Require a rather accurate mental model of the computer's internal processing






5. Easy and inexpensive to make - Flexible enough to be constantly changed and rearranged - Complete enough to yield useful feedback about specific design questions






6. Structuring the information space - Creating of alternative solutions - Determining which design concept to purse






7. Consistency-Correctness - Generalizability - Conventions - Familiarity - Location - Modes






8. Speech input 1.hands - free operation 2.poor lighting situations 3.mobile application 4.in the home - speech output 5.on - board navigational systems






9. Comprehensibility and learnability






10. Goals - Execution - World - Evaluation






11. 1.language is ambiguous 2.meaning depends on context 3.dependent on visual cues






12. 1. speech recognition 2. semantic - grammar issues - vague meanings - contradictory statement






13. Translating the user's task language into the input language requires knowledge of the core language - The output language can be confusing for inexperienced users - there is very little feedback






14. Menu constraints can help the user to form the proper intentions and specify the proper action sequence - provide a context to evaluate the output language






15. We respond first to the intensity of a stimulus and only then do we begin to process its meaning






16. Location - Logical Grouping - Conventions - Redundancy






17. 1.creating descriptions of the people who do the work 2.describing the different goals involved in the work 3.documenting the work step by step 4.creating different stories about how the various aspects of the work are done 5.creating charts and diag






18. 1. Visibility of System Status 2. Match between System and the Real World 3. User Control and Freedom 4. Consistency and Standards 5. Error Prevention 6. Recognition Rather Than Recall 7. Flexibility and Efficiency of Use 8. Aesthetic and Minimalist


19. Effectiveness/Usefulness 1.Utility 2.Safety(Recovery) 3.Flexibility(Customization) 4.Stability - Efficiency/Usability






20. 1. suitable for repetitive tasks 2. sdvantageous for expert users 3.offer direct access to system functionality 4.efficient and powerful 5.not encumbered with graphic controls - low visual load - not taxing on system resource 6. scriptable






21. 1.require valid input in valid format 2.require familiarity with interface control 3.can be tedious to correct mistakes






22. Gulfs of execution relate to the effectiveness principle - Gulfs of evaluation relate to the efficiency principle






23. 1.command line 2.menu- based interface 3.form fill- in 4.question and answers 5.direct manipulation 6.metaphors 7.web navigation 8.3d environments 9.zoomable interface 10.natural language






24. Observation - elicitation






25. 1. low memory requirements 2. self- explanatory 3.easy to undo errors 4. sppropriate for beginners






26. They make it possible to try out ideas very early - They make it possible to test - revise - test - revise...They engage end users -- managers and customers






27. 1.easy to learn2.low memory requirements 3.easy to undo 4.immediate feedback to user actions 5.enable user to use spatial cues 6.easy for beginner






28. 1.ease of learning - 2.low memory requirement - 3.flexible interaction - 4.low screen requirement - 5. sppropriate for beginner






29. Use multiple independent evaluators - Use observer to record evaluator - Go through interface several times - Compare interaction against list of heuristics - Use heuristics specific to design - List heuristic problems and how the heuristic is violat


30. 1.not self- explanatory 2.inefficient use of screen real estate 3.high graphical system requirements






31. They allow an easy way to explore the problem space - They provide a way to create clusters of related elements - They provide a graphical view of the problem space - They resonate with the ways in which people process information






32. Establishing the goal - Forming the intention - Specifying the action sequence - Execute the action sequence - Perceiving the world state - Interpreting the perception - Evaluate the interpretation






33. They are quick and easy to perform - They can be done before any preliminary designs have been made - They will let you know how people organize information - They will expose underlying structures






34. 1.They facilitate the development of design procedures 2.They help in finding ways to talk about design 3.They create project management






35. They increase productivity - They offer constraint and consistency checks - They facilitate team approaches - They ease maintenance






36. 1.low memory requirement 2. self- explanatory 3. simple linear presentation 4.easy for beginner






37. Participants - design - tester






38. Brainstorming - Card sort - Semantic Networks - Personas - Scenarios - Flowcharts - Cognitive walkthrough - Use cases






39. Physical - cultural - functional - informational






40. 1.require knowledge of the task domain - 2.may require tedious clarification dialogues - 3.complex system development






41. 1.low memory requirements 2. self- explanatory 3.can gather a great deal of information in little space 4.present a context for input information






42. Primary - secondary - facilitator - indirect






43. What it will look like - What components it will require - How the screens will be laid out






44. 1.require valid input supplied by user 2.require familiarity with interface control 3.can be tedious to correct mistakes






45. Direct indirect - corporate documentation - logs and notes - questionnaires






46. Functionality->presentation filter | (comprehensibility barrier)| efficiency usability ->|(learnability barrier) | Effectiveness Usefulness






47. They are not interactive - They cannot be used to calculate response timings - They do not deal with interface issues such as color or font size






48. Articulatory distance is large because we are presented with the command prompt - no indication of functionality






49. Artificial context - Not definitive od product acceptance - Skewed sample of uses - Not always efficient






50. Direct - indirect - ethnographic observation - distributed cognition