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.rapid and inflexible navigation 2.inefficient for large menu navigation 3.inefficient use of screen real estate 4. slow for expert






2. Time - finance - personnel - laboratory






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






5. Primary - secondary - facilitator - indirect






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






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






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


10. Direct - indirect - ethnographic observation - distributed cognition






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






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






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






14. Observation - elicitation






15. Physical - cultural - functional - informational






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


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






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






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






20. They can be difficult to create f the target audience is international - Having too many personas will make the work difficult - There is a risk of incorporating unsupported designer assumption






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






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






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






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






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






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






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






28. Comprehensibility and learnability






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






30. Progressive Disclosure - Constraints






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






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






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






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






36. Participants - design - tester






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






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






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






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






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






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






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






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






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






46. Menu options create small articulatory distance






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






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






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






50. Goals - Execution - World - Evaluation