1 / 17

Part 1: Usability Testing

Part 1: Usability Testing. Usable systems. are consistent. support the user‘s workflow. avoid errors. provide good feedback. give users control. Usability Testing - An introduction. Goals: To assure that the REGNET system is usable (for the different target groups).

loc
Download Presentation

Part 1: Usability Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Part 1: Usability Testing

  2. Usable systems ... are consistent support the user‘s workflow avoid errors provide good feedback give users control Usability Testing - An introduction Goals: To assure that the REGNET system is usable (for thedifferent target groups) The usability of an interfaceis a measure of the effectiveness, efficiency and satisfaction with which specified users can achievespecified goals in a particularenvironment with that interface REGNET Project Team Meeting Content Group

  3. Methods of usability testing proposed for the REGNET project: Heuristic Tests: Tests by experts, using generally accepted usability criteria. User Tests (Scenario based tests): Get/collect users view ofsystem features. Card Sorting: Determine the optimal information architectureof the system Usability Testing - An introduction Why usability testing? - To facilitate ease of learning in using the system - To increase the speed of task completion - To minimize the error rate whilst using the system-- To increase the subjective user satisfaction Results: detailed catalogue of recommendations to enhance the user interface REGNET Project Team Meeting Content Group

  4. Usability Testing I - Heuristic tests REGNET Usability Index Basis for the heuristic tests in order to define usability requirements for the portal site. Test areas: • Navigation und Orientation • Interaction and Exchange of Information • Up-to-Dateness and Quality of Information • Design of Information and Text • Location and access to the system REGNET UI, see working material REGNET Project Team Meeting Content Group

  5. Usability Testing I - Heuristic tests Suggestion for testing Suggestion: 1. 3 partners should carry out a heuristic test (end-user-view of the portal). 2. Report the results (to IMAC) (excel spreadsheet together with comments). 3. IMAC will collect and analyse the results and formulate requirements for the improvement of the portal. 3-5 experts will find about90% of usability problems Usability experts / persons with experience incomputers + internet (overview about similarweb sites projects)! REGNET Project Team Meeting Content Group

  6. Usability Testing I - Heuristic tests To Do‘s (Working group and discussion) Evaluate „Web Usability Index“(As provided by IMAC) • Which test criteria are needed for the REGNET Project? • Which additional test criteria should be included for the REGNET Project? Agreement on task assignement • How many tests? • Responsible partners Agreement of test schedule Working group REGNET Project Team Meeting Content Group

  7. Usability Testing II - Scenario based tests Scenario based tests - Asking user to work with the system • Users perform different tasks on a system • Activities are monitored by expert staff • Users are debriefed after the experiment regarding their general impression • Results of the experiment are evaluated by experts Why scenario based tests? • 1. Status Quo Investigation • - Data on User Experience • 2. Optimization • - Navigation, Wording, Information Architecture, Look and Feel REGNET Project Team Meeting Content Group

  8. Usability Testing II - Scenario based tests Suggestion for testing • Experiments are performed by content partners (monitoring user) • Each content partner identifies 2 potential system users • Each content partner translates the questionnaires !? • Each content partner carries out the tests according to the test manual • Each content partner uses a standard sheet for the de-briefing of the test persons • Results are gathered and evaluated by IMAC Estimation: 30 tests, perpartner 1 day. REGNET Project Team Meeting Content Group

  9. Usability Testing II - Scenario based tests To Do‘s (Working group and discussion) • Agreement on test effort (No. of Test-Persons) per Content Partner(Proposal: 2 test persons from the specialists user group per partner. Each user group is represented with at least three test persons) • Define user groups from which the test persons are selected • Discuss and finalise questionnaire(Proposal for questionnaire provided by IMAC) • Agree on the schedule for user testing User groups Questionnaire, see working material Workinggroup REGNET Project Team Meeting Content Group

  10. Usability Testing II - Scenario based tests Test user groups List of professional user groups(internal) to be considered in the first phase (according to your feedback). All roles covered? Other groups to be added? (all groups should equally be covered ...) REGNET Project Team Meeting Content Group

  11. Usability Testing II - Scenario based tests Test user groups List of end user groups(external) to be considered in the secondphase (according to your feedback). REGNET Project Team Meeting Content Group

  12. Usability Testing II - Scenario based tests Next steps (after Sofia) • Create test guidelines • Translation of templates • Set-up test environement • Identify test persons • Carry out tests • Collect reports • Evaluate Reports + Recommendations Working in groups REGNET Project Team Meeting Content Group

  13. Usability Testing III - Card Sorting Card Sorting Experimental approach for the validation of the information architecture (portal). Goal: To define the final structure of the web site (Administrativ view, end user view) IBMs Usort / EZCalc http://www-3.ibm.com/ibm/easy/eou_ext.nsf/Publish/410 Why Card Sorting? - to validate the existing Regnet information architecture - easy and cheap to conduct - enables to understand how 'real people' are likely to group items - to identify terminology that is likely to be misunderstood - to identify items that are likely to be difficult to categorize and find Suggestion for testing: 3 tests per partner(professional test user groups, administrativeview), 1 h per test (0,5 days per partner). REGNET Project Team Meeting Content Group

  14. Usability Testing III - Card Sorting • „Items of information“ (menu entries) are translated by the content partners and loaded into the system • During tests the various „items“of information are dragged from a source window to the target windows • Related Items are grouped together in the target window • Not-related items are dragged into distinct groups • Similar groups are put in higher-level groups • Groups are given „meaningful“ names by test-persons • Result file are created and send to IMAC REGNET Project Team Meeting Content Group

  15. Usability Testing III - Card Sorting • IMAC loads results files into evaluation software • Diagrams are generated to guide the navigational design of the site to meet users expectations(cluster analysis) • IMAC proposes renaming of menu entries / information architecture for end-users / specialist users portal view “Life-Test” - Administrative view - End-user view REGNET Project Team Meeting Content Group

  16. Usability Testing III - Card Sorting To Do‘s (Working group and discussion) • Agreement on carrying out such tests • Agreement on Test Effort(No. of Test-Persons per Content Partner)Proposal: • 3 test person from each of the specialists user group per content partner • Agreement on the schedule for card sorting Card Sorting exercise REGNET Project Team Meeting Content Group

  17. Usability Testing III - Card Sorting Next steps (after Sofia) • Create test guidelines • Translate cards • Set-up test environement • Identify test persons • Carry out tests • Collect reports • Evaluate Reports + Recommend • Scenario based tests QA REGNET Project Team Meeting Content Group

More Related