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. What it will look like - What components it will require - How the screens will be laid out






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






3. Physical - cultural - functional - informational






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






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






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






7. Comprehensibility and learnability






8. Overload - Feedback - Recognition/Recall - Orientation






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






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






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






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






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






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






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






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






17. Observation - elicitation






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






19. Progressive Disclosure - Constraints






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






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






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






23. Primary - secondary - facilitator - indirect






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






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






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






27. Location - Logical Grouping - Conventions - Redundancy






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






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






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


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






32. Time - finance - personnel - laboratory






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. Articulatory distance is large because we are presented with the command prompt - no indication of functionality






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






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






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






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






39. Participants - design - tester






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






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






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






43. Goals - Execution - World - Evaluation






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






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






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






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






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. They increase productivity - They offer constraint and consistency checks - They facilitate team approaches - They ease maintenance






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