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. Unscientific - Partial - Unstable - Inconsistent - Personal






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






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






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






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






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






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






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






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






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






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






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






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






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






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






16. Direct - indirect - ethnographic observation - distributed cognition






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






18. Goals - Execution - World - Evaluation






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






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






21. Progressive Disclosure - Constraints






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






23. Menu options create small articulatory distance






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






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






26. Participants - design - tester






27. Time - finance - personnel - laboratory






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






29. Physical - cultural - functional - informational






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






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






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






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






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






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






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






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






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






39. Primary - secondary - facilitator - indirect






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






41. Overload - Feedback - Recognition/Recall - Orientation






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






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






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. Direct indirect - corporate documentation - logs and notes - questionnaires






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






47. Location - Logical Grouping - Conventions - Redundancy






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






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






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