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. 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






2. Progressive Disclosure - Constraints






3. 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






4. Low- fidelity prototypes - Evaluations - Wireframes - Functional prototypes






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






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






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






8. 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






9. They can be used early and often - They are inexpensive and easy to create - They make design idea visual - No special knowledge is required - all team members can create them






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






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






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






13. 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






14. Minimize help desk calls - increase product loyalty - Provide benchmarks for future products






15. 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






16. Unscientific - Partial - Unstable - Inconsistent - Personal






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






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






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






20. Location - Logical Grouping - Conventions - Redundancy






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






22. 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






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






24. 1. the people who are involved with the work 2. the things they use to do the work - 3. the process that are involved in the work - 4. the information required to do the work - 5. the constraints imposed on the work - 6. the inputs required by the wo






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






26. Observation - elicitation






27. Comprehensibility and learnability






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






29. Time - finance - personnel - laboratory






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






31. Menu options create small articulatory distance






32. Determine the function of the device - Determine what actions are possible - Determine mapping from intention to physical movement - Perform the action - Determine whether the system is in the desired state - Determine the mapping from system state t






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. Direct - indirect - ethnographic observation - distributed cognition






35. 1.low command retention 2. steep learning curve 3.high error rates 4.heavy reliance on memory 5.frustrating for novice users






36. Primary - secondary - facilitator - indirect






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






38. 1.free phase 2.captive phase 3. termination phase






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






40. 1.run out of metaphors 2.mixed metaphors 3.carry connotations and association






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






42. 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


43. Overload - Feedback - Recognition/Recall - Orientation






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






45. 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


46. Participants - design - tester






47. They are quick and easy to create - They provide a consistent model for all team members - They are easy to use with other design methods - They make the user real in the mind of the designer






48. The range of possible intentions is consistently wide - users usually have multiple options for specifying action sequences - provide multiple ways of executing action sequence






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






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