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.low command retention 2. steep learning curve 3.high error rates 4.heavy reliance on memory 5.frustrating for novice users






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






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






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






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






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






7. Menu options create small articulatory distance






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






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






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






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






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






13. Overload - Feedback - Recognition/Recall - Orientation






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






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






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






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






18. Primary - secondary - facilitator - indirect






19. Location - Logical Grouping - Conventions - Redundancy






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






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






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






23. Comprehensibility and learnability






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






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






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






27. Time - finance - personnel - laboratory






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






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






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






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






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






33. Participants - design - tester






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






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






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






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






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






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






40. Physical - cultural - functional - informational






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


42. Speech input 1.hands - free operation 2.poor lighting situations 3.mobile application 4.in the home - speech output 5.on - board navigational systems






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






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






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






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






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






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






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






50. Progressive Disclosure - Constraints