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. Direct indirect - corporate documentation - logs and notes - questionnaires






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






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






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






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






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






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






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






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






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






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






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






13. Progressive Disclosure - Constraints






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






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






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






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






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






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






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






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






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






23. Participants - design - tester






24. Physical - cultural - functional - informational






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






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


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






28. Location - Logical Grouping - Conventions - Redundancy






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






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






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






32. Direct - indirect - ethnographic observation - distributed cognition






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






48. Overload - Feedback - Recognition/Recall - Orientation






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






50. Goals - Execution - World - Evaluation