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


2. Physical - cultural - functional - informational






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






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






5. Comprehensibility and learnability






6. Progressive Disclosure - Constraints






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






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






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






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






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






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






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






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






15. Menu options create small articulatory distance






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






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






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






19. Direct - indirect - ethnographic observation - distributed cognition






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






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






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






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






24. Unscientific - Partial - Unstable - Inconsistent - Personal






25. Location - Logical Grouping - Conventions - Redundancy






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






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






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






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






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






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






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






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






34. Overload - Feedback - Recognition/Recall - Orientation






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






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






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






38. Time - finance - personnel - laboratory






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






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






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






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






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






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






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






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


47. Participants - design - tester






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






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






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