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






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






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






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






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






6. Observation - elicitation






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






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


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






10. Menu options create small articulatory distance






11. Comprehensibility and learnability






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






13. Location - Logical Grouping - Conventions - Redundancy






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






15. Progressive Disclosure - Constraints






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






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. Time - finance - personnel - laboratory






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






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






21. Goals - Execution - World - Evaluation






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






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






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






25. Overload - Feedback - Recognition/Recall - Orientation






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






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






28. Primary - secondary - facilitator - indirect






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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


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






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






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






49. Unscientific - Partial - Unstable - Inconsistent - Personal






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