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. Direct - indirect - ethnographic observation - distributed cognition






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






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






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






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






6. Overload - Feedback - Recognition/Recall - Orientation






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






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






9. Observation - elicitation






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






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






12. Time - finance - personnel - laboratory






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






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






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






16. Goals - Execution - World - Evaluation






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






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






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






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






21. Primary - secondary - facilitator - indirect






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






23. Unscientific - Partial - Unstable - Inconsistent - Personal






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






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






26. Location - Logical Grouping - Conventions - Redundancy






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






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






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






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






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






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






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






34. Physical - cultural - functional - informational






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






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






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






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






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






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






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






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






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






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


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






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


48. Progressive Disclosure - Constraints






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






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