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






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






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






4. Primary - secondary - facilitator - indirect






5. Location - Logical Grouping - Conventions - Redundancy






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






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






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






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






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






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






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






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






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






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






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






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






18. Progressive Disclosure - Constraints






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






20. Observation - elicitation






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






22. Comprehensibility and learnability






23. Time - finance - personnel - laboratory






24. Participants - design - tester






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






26. Goals - Execution - World - Evaluation






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






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






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






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






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






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






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






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


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






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






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






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






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






40. Direct - indirect - ethnographic observation - distributed cognition






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






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






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






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






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






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






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






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






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


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