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. Ease of Learning - Efficiency of use - Memorability - Error frequency and severity - Subjective satisfaction






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






3. Direct - indirect - ethnographic observation - distributed cognition






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






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






6. Physical - cultural - functional - informational






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






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






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






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






11. Overload - Feedback - Recognition/Recall - Orientation






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






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






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






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






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






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






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






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






20. Observation - elicitation






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






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






23. Menu options create small articulatory distance






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






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






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






27. Progressive Disclosure - Constraints






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


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






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






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






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






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






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






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






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






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






38. Goals - Execution - World - Evaluation






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






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






41. Time - finance - personnel - laboratory






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






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






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






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






46. Unscientific - Partial - Unstable - Inconsistent - Personal






47. Comprehensibility and learnability






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






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






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