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






2. Participants - design - tester






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






4. Primary - secondary - facilitator - indirect






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






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. Articulatory distance is large because we are presented with the command prompt - no indication of functionality






9. Direct - indirect - ethnographic observation - distributed cognition






10. Menu options create small articulatory distance






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






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






13. Observation - elicitation






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






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






17. Time - finance - personnel - laboratory






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






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






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






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






23. Comprehensibility and learnability






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






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






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






27. Progressive Disclosure - Constraints






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






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






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






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






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


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






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






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






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






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






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






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






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






41. Physical - cultural - functional - informational






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






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






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






45. Unscientific - Partial - Unstable - Inconsistent - Personal






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






47. Overload - Feedback - Recognition/Recall - Orientation






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






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






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