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






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






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






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






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






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






8. Time - finance - personnel - laboratory






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






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






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






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






13. Location - Logical Grouping - Conventions - Redundancy






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






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






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






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






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


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






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






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






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






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






24. Physical - cultural - functional - informational






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






26. Ease of Learning - Efficiency of use - Memorability - Error frequency and severity - Subjective satisfaction






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






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






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






30. Menu options create small articulatory distance






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






32. Overload - Feedback - Recognition/Recall - Orientation






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






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






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






36. Comprehensibility and learnability






37. Unscientific - Partial - Unstable - Inconsistent - Personal






38. Primary - secondary - facilitator - indirect






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






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






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






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






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






44. Direct - indirect - ethnographic observation - distributed cognition






45. Participants - design - tester






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






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






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






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






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