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. Functionality->presentation filter | (comprehensibility barrier)| efficiency usability ->|(learnability barrier) | Effectiveness Usefulness






2. Observation - elicitation






3. Goals - Execution - World - Evaluation






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


5. Time - finance - personnel - laboratory






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






7. Primary - secondary - facilitator - indirect






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. 1.ease of learning - 2.low memory requirement - 3.flexible interaction - 4.low screen requirement - 5. sppropriate for beginner






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






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






12. Comprehensibility and learnability






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






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






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






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






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






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






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






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






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






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






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






24. Menu options create small articulatory distance






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






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






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






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






29. Progressive Disclosure - Constraints






30. Participants - design - tester






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






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






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






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






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






36. 1.run out of metaphors 2.mixed metaphors 3.carry connotations and association






37. Physical - cultural - functional - informational






38. Direct - indirect - ethnographic observation - distributed cognition






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






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






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






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






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






44. Unscientific - Partial - Unstable - Inconsistent - Personal






45. Location - Logical Grouping - Conventions - Redundancy






46. Overload - Feedback - Recognition/Recall - Orientation






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






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






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. Gulfs of execution relate to the effectiveness principle - Gulfs of evaluation relate to the efficiency principle