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.require valid input in valid format 2.require familiarity with interface control 3.can be tedious to correct mistakes






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






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


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






5. Progressive Disclosure - Constraints






6. Menu options create small articulatory distance






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






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






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






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






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


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






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






14. Location - Logical Grouping - Conventions - Redundancy






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






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






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






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






19. They only involve the elements that you have written on the cards - They suggest solutions that imply structure - They become difficult to navigate with more categories






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






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






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






23. Graphical libraries - User interface toolkits - Visual interface builders - Web development tools






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






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






26. Observation - elicitation






27. Comprehensibility and learnability






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






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






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






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






32. Goals - Execution - World - Evaluation






33. 1.rapid and inflexible navigation 2.inefficient for large menu navigation 3.inefficient use of screen real estate 4. slow for expert






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






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






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






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






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






39. Primary - secondary - facilitator - indirect






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






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






42. Participants - design - tester






43. They require knowledge of problem space - They can lead beyond the problem space - There is no formal semantics for defining symbol meaning






44. Physical - cultural - functional - informational






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






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






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






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






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






50. Direct - indirect - ethnographic observation - distributed cognition