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. Participants - design - tester






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






3. Observation - elicitation






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






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






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






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






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






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






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






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






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






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






14. Comprehensibility and learnability






15. Unscientific - Partial - Unstable - Inconsistent - Personal






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






17. Physical - cultural - functional - informational






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






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






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






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






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






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






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






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






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






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






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






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






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






31. Time - finance - personnel - laboratory






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






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






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






35. Menu options create small articulatory distance






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






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






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






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






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






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


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






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






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






45. Overload - Feedback - Recognition/Recall - Orientation






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






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






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






49. Direct - indirect - ethnographic observation - distributed cognition






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