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. Task analysis - storyboarding - use cases - primary stakeholder profiles






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






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






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






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






6. Physical - cultural - functional - informational






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






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






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






10. Primary - secondary - facilitator - indirect






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






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






13. Location - Logical Grouping - Conventions - Redundancy






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






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






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






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






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






19. Goals - Execution - World - Evaluation






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






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






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






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






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






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






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






28. Comprehensibility and learnability






29. Direct - indirect - ethnographic observation - distributed cognition






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






31. Unscientific - Partial - Unstable - Inconsistent - Personal






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






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






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






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






36. Menu options create small articulatory distance






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






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






39. Time - finance - personnel - laboratory






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






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






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






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






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






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






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






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


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






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






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