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. Comprehensibility and learnability






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






3. Unscientific - Partial - Unstable - Inconsistent - Personal






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






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






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






7. Location - Logical Grouping - Conventions - Redundancy






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. Gulfs of execution relate to the effectiveness principle - Gulfs of evaluation relate to the efficiency principle






10. Menu options create small articulatory distance






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






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






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






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






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






16. Goals - Execution - World - Evaluation






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






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






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






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






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






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






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






24. Physical - cultural - functional - informational






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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


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






44. Primary - secondary - facilitator - indirect






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






46. Participants - design - tester






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






48. Overload - Feedback - Recognition/Recall - Orientation






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






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