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






2. Menu options create small articulatory distance






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






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






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






6. Physical - cultural - functional - informational






7. Observation - elicitation






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






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






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






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. They require knowledge of problem space - They can lead beyond the problem space - There is no formal semantics for defining symbol meaning






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






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






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






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






17. Overload - Feedback - Recognition/Recall - Orientation






18. Primary - secondary - facilitator - indirect






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






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






21. Comprehensibility and learnability






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






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






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






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






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






27. Goals - Execution - World - Evaluation






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






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






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






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






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






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






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


35. Progressive Disclosure - Constraints






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






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






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






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






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






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






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






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






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. 1. speech recognition 2. semantic - grammar issues - vague meanings - contradictory statement






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






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






48. Time - finance - personnel - laboratory






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






50. Location - Logical Grouping - Conventions - Redundancy