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






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






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






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






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






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


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






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






9. Primary - secondary - facilitator - indirect






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






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






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






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






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






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


16. Time - finance - personnel - laboratory






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






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






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






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






21. Menu options create small articulatory distance






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






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






24. Location - Logical Grouping - Conventions - Redundancy






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






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






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






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






29. Progressive Disclosure - Constraints






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






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






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






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






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






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






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






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






38. Overload - Feedback - Recognition/Recall - Orientation






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






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






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






42. Comprehensibility and learnability






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






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






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






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






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






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






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






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