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. Menu options create small articulatory distance






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


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






4. Progressive Disclosure - Constraints






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






6. Location - Logical Grouping - Conventions - Redundancy






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






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






9. Physical - cultural - functional - informational






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






11. Goals - Execution - World - Evaluation






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






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






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






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






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






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






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






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






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






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






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






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






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






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






26. Time - finance - personnel - laboratory






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






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. Overload - Feedback - Recognition/Recall - Orientation






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






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






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






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






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






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






36. Direct - indirect - ethnographic observation - distributed cognition






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






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






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






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






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






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






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






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






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






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. Easy and inexpensive to make - Flexible enough to be constantly changed and rearranged - Complete enough to yield useful feedback about specific design questions






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






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






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