DTU course 02261 - Usability Engineering January 2009 Exercise Booklet Version 02-01-2009 Written by Rolf Molich, Skovkrogen 3, 3660 Stenløse, Denmark
Table of Contents Exercise 1: Usability Assessment 3 Exercise 2: Usability Test Task Evaluation 5 Scenario 5 Your Assignment 6 Test Tasks 7 Exercise 3: Usability Test 8 Reporting requirements 9 Tips 10 Exercise 3a. Usability test of Borger.dk (Danish) 12 Exercise 3b. Usability test of DSB.dk (Danish) 17 Exercise 3c. Usability test of Trafikken.dk (Danish) 19 Exercise 3d. Usability test of www.um.dk/borgerservice (Danish) 21 Exercise 3e. Usability test of VisitDenmark.com (English) 23 Presentations 25 Exercise 4: Interview 26 Game Partner Search (GAPAS) 26 Suggested Approach 26 Reporting requirements 27 Tips 28 Exercise 5: Coordination 30 Reporting requirements 30 Copyright 2009 DialogDesign Page 2
Exercise 1: Usability Assessment Start exercise: Monday 5 January at 12.00. End exercise: Monday 5 January at 19.00. Discussion: Thursday 8 January at 09.55. This exercise consists of two parts. Part 1. Evaluate the website that your team will test in exercise 3 In exercise 3 your team must usability test one of the websites available for this course. Specifications for the usability test of the websites appear in section 3. You are welcome to indicate a preference. One of the websites (VisitDenmark) is reserved for students who do not speak Danish. The lecturer will assign a website to your team taking your preference and an even distribution of the assignments into consideration. Your team s assignment will appear on the List of Participants for this course. Part 2. Evaluate a car rental website Evaluate the usability of the car rental reservation procedure on the English language version of the Russian car rental website for Sixt Rent-a-Car, www.sixt-rent.ru/en.html The website s home page looks approximately like this: Copyright 2009 DialogDesign Page 3
General instructions Evaluate the usability using common sense and the guidelines for usable design that you heard about in the lecture on Monday 5 January. These guidelines can also be found in chapter 6 of the textbook. Summarize your experience from the usability assessment in a short note addressed to the development team describing exactly five usability issues for each of the two websites. Describe only the usability issues that you consider most important. Focus on usability issues, not functional problems (bugs). You can use whatever approach to the assessment that you consider feasible. For each of the two websites, only report the five most important problems. In other words, report a total of 5 + 5 = 10 usability problems. Do not use more than 60 minutes for each evaluation. Be brief and specific. Limit yourself to at most 1.000 words. Describe only the usability issues that you consider most important. Describe exactly five issues for each website. Put the issues in priority order, most serious issues first. You do not need to include screenshots to illustrate the problems. Include screenshots only to point out specific details in the design. Assume that the reader of your evaluation knows the websites well. Write your evaluation in English or Danish. Send your comments in one email attachment to dtu2009@molich.dk before the above deadline. Use Microsoft Word or Adobe pdf format. Use the email header format Exercise 1 - Team B01 where you replace B01 with your team number. Copyright 2009 DialogDesign Page 4
Exercise 2: Usability Test Task Evaluation Start exercise: Tuesday 6 January at 12.00. End exercise: Tuesday 6 January at 19.00. Discussion: Wednesday 7 January at 12.00. In this exercise your team must comment on a task set for a proposed usability test. The task set contains a number of common problems discussed in the lecture on Tuesday 6 January. Scenario Imagine that John Nelson, a colleague of yours, has been asked to plan and facilitate a think aloud usability test of the user experience of Sid s CD-Shop (www.sidcd.com). Sid s CD-Shop has eight physical stores that sell CDs. The stores are located in the Greater Boston area in Massachusetts, USA. Five months ago, the owner, Sidney Clemson, decided that he wanted a web store. Sid is not particularly interested in the internet, but during the past months he has felt an unpleasant, growing competition from CD web stores. The web store will open two weeks from now. A limited number of customers are currently testing the site. The logistics for the web store should be fully operational at this time - it is possible to order and receive CDs. This will be the first usability test of the web site apart from an earlier paper prototype test for which no data is available. The target group for this test are ordinary, occasional CD-shoppers, age group 25-45 years. Test participants are familiar with the internet and have limited e-commerce experience. There will be six test participants and each test session will take approximately 90 minutes in total. The test sessions will be conducted in Boston. Each task will be printed on an index card. The test participant will receive the cards with the tasks one by one. Some of the test tasks contain notes in italics; these notes are for your information only - they are not seen by the test participant. There will be a short interview with each test participant before and after solving the test tasks. As test participants proceed with the tasks, John intends to ask them what their impression is of each page, why they are choosing specific links, and where they expect the link will take them. The interview questions and the test setup are not part of your assignment. John assures you that all the tasks can be completed on the web site. Copyright 2009 DialogDesign Page 5
Your Assignment Your colleague John has suggested the tasks on the following page for the usability test. Since he is rather inexperienced with usability testing, he has asked for your frank comments about the task set. You know from previous work with him that he is eager to learn and open to suggestions. Your task is to comment on the appropriateness of the tasks on the next page for this test. Be brief and specific. You must identify at least 10 of the known issues in the task set so I suggest you provide at least 12 comments. Limit yourself to at most 1.500 words. My solution has 33 comments and less than 1.400 words. Number your comments. Each of your comments must refer to a particular task or to the task set as a whole. You are welcome to comment both on the task set as a whole and on specific tasks. Send your comments as an email attachment to dtu2009@molich.dk before the above deadline. Use Microsoft Word or Adobe pdf format. Use the email header format Exercise 2 - Team D05 where you replace D05 with your team number. Sid s CD-Shop is invented solely for the purpose of this exercise; neither the shop nor the web site actually exists. Any similarity to real companies, people and events is purely coincidental. Copyright 2009 DialogDesign Page 6
Test Tasks 1. A friend has told you about an exciting new CD-shop on the web. It s called Sid s CD-Shop. Find the homepage of the web site. 2. Is the design of the home page appropriate for Sid s CD-Shop? 3. Register yourself on the web site. Use a fake name, if you wish. Note: Registration is required for purchasing a CD but not for browsing the store catalog. 4. Buy the following two CDs for your two nephews who both had birthdays last week, which you forgot. - The Lord of the Rings (Original soundtrack) - Mother Goose Rocks! Vol. 4 Have the first CD sent to Roger Hobbitt 1 Ring Road Rivendell, MA 01056 Have the second CD sent to Parry Hotter 2004 Nimbus Way Hogwarts, Pottertown, MI 08888 Have both of them gift wrapped. Stop when the web site asks for your credit card. 5. Set a reminder ten days before December 14, which is the birthday of your friend John Whiney, so you ll remember to buy him a CD. 6. You just heard a song on the radio. The speaker said that it was with Liza Minnelli. What CDs does the shop have with her? 7. Let s assume that by mistake you have put two identical CDs into your shopping bag. Use the help system to find out how you get rid of one of them. 8. Locate the discography of Jacques Loussier. Note: Jacques Loussier is a jazz musician. 9. You ordered a CD from Sid s CD-Shop a few hours ago. You have just seen it at half the price at your local record store. Cancel the order, if possible. 10. A German friend of yours has just done you a great favor. Does this web site ship CDs to Germany? (Try to find the answer in the Customer Service section). 11. You have just heard the song Homeward Bound in an particularly good recording on the radio. Unfortunately you did not hear who recorded it but you know that you will recognize it if you hear it again. Play samples of the versions of Homeward Bound that the web site offers. Copyright 2009 DialogDesign Page 7
Exercise 3: Usability Test Start exercise: Tuesday 6 January at 12.00. Questions answered: Tuesday 13 January at 12.00. End exercise: Tuesday 20 January at 19.00. Discussion: Thursday 22 January (time to be announced) In this exercise your team must conduct a usability test of the web site that you evaluated in exercise 1. Conduct the usability test as a think-aloud test as described in the Usability Testing lecture and in chapter 11 of the textbook. The usability test must comprise at least five separate test sessions; each test session must be with one or two test participants. A test session with two test participants counts as one test session. This exercise can be broken into the following steps: 1. Read the usability test requirement specification carefully. The test requirement specifications appear after this description of the exercise (Exercise 3a - Exercise 3e). The List of Participants for the course shows the test requirement specification that has been assigned to your team. If a presentation meeting is offered for your website, I suggest that at least one representative from your team attends. If you have questions relating to the specification, please send an e-mail to the contact person. Remember to cc your e-mail to dtu2009@molich.dk. 2. Create at least 10 typical scenarios for the web site. Make sure that your scenarios (test tasks) meet the client s requirements. At least one open scenario must be included. 3. Familiarize yourself with the web site and solve your own scenarios. 4. Consider whether you want to modify the scenarios based on your own experience with the scenarios. 5. Send the scenarios to the lecturer by email and wait for approval. Include pre-test interview questions and post-test debriefing questions. Use the email address dtu2009@molich.dk. Use the header format: Scenarios exercise 3 - Team 14. If you don t get a response within 24 hours, please resend your email. If required, revise the scenarios based on the lecturer s comments. From experience, about one third of the scenarios must be resubmitted before they are approved. 6. Recruit test participants. It is part of your assignment to recruit the required test participants. You will need at least five test participants. Attempt to recruit typical users. Minimize the number of test participants who have programming experience or who have designed web sites. Write and send a usable letter or email to each test participant explaining what will happen during the test session and where the test session will take place. Do not use people who are test participants for other teams in this course. Students whose primary language is Danish must test only Danish versions of websites; they must only use test participants whose primary language is Danish. Students whose primary language is not Danish must test only English versions of websites; they must only use test participants whose primary language is not Danish. Other languages may be used; contact the lecturer. Copyright 2009 DialogDesign Page 8
7. Prepare the test sessions. Appoint a facilitator and a notetaker. The roles do not have to be the same for all tests. Setup and test the equipment. Write each scenario on a separate piece of paper. Prepare debriefing questions. 8. Carry out a pilot test session (optional). Ask a typical user or a fellow student from another team to solve your scenarios using the web site. If required, revise the scenarios and the test setup based on your experience from the pilot test session. The pilot test session does not count as a regular test session; if you run a pilot test session you must still run five regular test sessions. 9. Carry out at least five usability test sessions with the web site. Use the scenarios you created in steps 2-5. Each test session should take 30-90 minutes. Remote test sessions are permissible for teams who do not speak Danish. 10. Write test report. Observe the reporting requirements below. 11. Send your test report to the lecturer by email. Send your report as an email attachment in Microsoft Word or Adobe pdf format to dtu2009@molich.dk before the above deadline. Use the email header format Exercise 3 - Team NN. Name your report file Team NN. Replace NN with your actual team number, for example Team V12. You can ask questions about this exercise at the lecture on Tuesday 13 January. Reporting requirements You may write your report in English or in Danish. The quality of the language will carry some weight in my evaluation of your report. I recommend that you use the chapter headings and the format that DialogDesign uses for its usability reports. Use sample reports from DialogDesign as a model. You can find links to these reports on the course home page in the section Textbook. If you decide to use an alternative format, the usability of your report format will be an important element in the evaluation of your report. You can use any tool you want, for example LaTeX, to create the report as long as the appearance is reasonably similar to DialogDesign s reports. Your report must include the following chapters in the following order. The texts in brackets are the chapter titles you must use if you decide to write your report in Danish. - Executive summary (Resumé) - Approach (Fremgangsmåde) - Expectations (Testdeltagernes forventninger til webstedet) - Findings (Testdeltagernes oplevelse af webstedet) - Appendix: Usability Test Script (Testplan) - Appendix: Test Scenario Results (Testdeltagernes opgaveløsning) - Appendix: Comparison with expert review (Sammenligning med ekspertreview) - Appendix: Your Comments (Jeres kommentarer) The chapter Comparison with expert review must contain a frank comparison between your findings in exercise 1 and the results of the usability test. Which of your findings in exercise 1 Copyright 2009 DialogDesign Page 9
were confirmed by the usability test? Which were not? What can you conclude from this comparison? Limit yourself to one page. The chapter Your Comments must answer the question: How many hours has each member of your team used for this exercise. You may also use this chapter to comment on the exercise, the report format, things you would do differently next time, etc. Reports without a reasonable number of representative screenshots will not be accepted. Each usability comment must be clearly classified as a Positive comment, a Good idea, a Minor problem, a Serious problem or a Critical problem. You are welcome to copy the usability comment type definitions from the model report into your own report. Your executive summary must not exceed one page. Use the guidelines for executive summaries presented at the usability testing lecture. The executive summary must include exactly three positive comments and three critical comments. Make sure your summary is a true summary of the report. For example, the summary must only describe issues that are covered in the main body of the report. The quality of the executive summary will carry considerable weight in my evaluation of your report. Your report must contain between 20 and 40 usability comments. This is less than the model report; the TowerRecords report contains 46 comments. If you have more than 40 comments, prioritize and report only the 40 most important comments. Being able to prioritize and limit the number of comments is important for usability professionals. Do not combine several independent usability issues into one comment. My detailed evaluation scheme for the usability comments is: You get 1 point for each valid usability comment. Each duplicate or trivial comment gives 0 points. You get -1 point for each invalid or incomprehensible comment. At least 20 points are required before the usability comments are considered satisfactory. Include a suitable recommendation for improvement for each serious and critical usability problem, unless the recommendation is self-evident. Recommendations are part of the usability comment they belong to; they should not be presented as separate comments. Your report must include at least 8 reasonable recommendations. For open scenarios, describe what each test participant decided to do. Your report must not exceed 35 pages. The file size of the report must not exceed 2 MB; if necessary use 256-color screenshots to get below the 2 MB limit. Tools like Paint Shop Pro can convert high quality screenshots into 256-color screenshots. Tips If you understand Danish, download and read Regler for standard tænke højt test from http://www.sigchi.dk/sigchi/ressourcer/standardtest/index.html. There are many useful tips about usability testing in this document. Before each test the facilitator must tell the test participant that you are testing the web site, not the test participant. Explain carefully that the test participant can do nothing stupid or wrong during the test. Start by questioning the test participants a little bit before they start working on the first scenario. What is their background and internet experience? What are their expectations of web site? Have they worked with this web site before? Or with similar sites? If yes, what was their experience? Copyright 2009 DialogDesign Page 10
Avoid help unless the test participant is completely stuck. Your sense of time is different from that of the test participant. Two minutes may seem a very long time for you while it often feels like a short time for a busy test participant. It s not a problem if the test participant can t solve a scenario within 1-2 minutes, unless, of course, the test participant considers this a problem. Just as in real life, test participants will normally tell you when they would give up. When this happens, break off the current scenario and continue with the next scenario even if the test participant offers to continue. If test participants are quiet, encourage them to think aloud during the test. Avoid humorous scenarios. Use small, realistic scenarios rather than tasks. Scenarios help the test participants to better understand the purpose of each task. Avoid hidden clues - that is, words and phrases that unintentionally reveal how a scenario can be solved. Avoid reporting issues that were encountered by one test participant only. Copyright 2009 DialogDesign Page 11
Exercise 3a. Usability test of Borger.dk (Danish) Test the website Borger.dk, a common entry point for Danish citizen to public services. Kundens oplæg: Indledning og baggrund: Borger.dk er den fællesoffentlige portal, der samler det offentlige på nettet, og giver borgeren overblik og én indgang til det offentlige på nettet. Når det er relevant, guider borger.dk borgeren videre til relevante svar på andre offentlige sites. Formålet med borger.dk er at være en enkel adgang til offentlig information og digital selvbetjening. Den 20. oktober 2008 blev borger.dk lanceret i en ny version. Den nye version giver borgeren adgang til personaliseret indhold via Min Side. I dag kan borgeren derfor logge på borger.dk med sin digitale signatur, og få adgang til fx bolig- skatte eller personoplysninger. Oplæg og forslag til testindhold: Det vil være relevant at teste enkelte selvbetjeningsløsninger og Min Side, hvilket vil kræve, at testdeltagerne har en digital signatur. Forslag til testspørgsmål: 1. Hvordan er oplevelsen af at løse opgaver på borger.dk? 2. Hvad giver god mening/er værdifuldt som bruger af borger.dk? Skabes der merværdi for brugerne? Oplever brugeren fx, at: Det var nemt! eller det var smart? 3. Hvordan er overblikket på borger.dk er det nemt eller svært at finde det, som man søger? 4. Hvordan er informationerne? Er de til at forstå? Hvordan er oplevelsen, og hvordan er tekstindholdet? 5. Fremtræder borger.dk ensartet i sin opbygning af siderne, indholdet i felterne og sproget? 6. På siderne med kernetekst er der højreside-bokse som som selvbetjening, borger.dk anbefaler og kontakter? Hvordan opfattes disse af brugeren? 7. Er brugeren opmærksom på at der kan vælges (egen) kommune på borger.dk? 8. Hvordan forholder brugerne sig til emnet selvbetjening? Forstås det hvad der menes med selvbetjeningsløsninger? 9. Hvordan opleves brugen af selvbetjeningsløsning? Er det logisk, nemt, hvordan er flowet? (Prøv gerne selvbetjeningsløsninger fra nogle af de forskellige indgange: Min Side, fra hovedfunktionen selvbetjening, sider med kernetekster) Copyright 2009 DialogDesign Page 12
10. Hvordan er oplevelsen af at bruge Min Side? Hvad synes brugeren om det nuværende indhold på Min Side? 11. Oplever brugeren en nytteværdi af at være logget på borger.dk med digital signatur? 12. Kan brugeren finde hvad de søger på borger.dk? 13. Er brugeren opmærksom på muligheden med at man kan ringe 1881 og få hjælp til at bruge borger.dk? 14. Vil brugerne benytte borger.dk i fremtiden i kontakten til det offentlige? 15. Har testdeltageren nogen forslag til hvordan borger.dk kan blive endnu bedre? 16. Var der noget savnet undervejs? 17. Vil de anbefale siden? 18. Hvordan opleves afsenderforholdet? - Hvem oplever brugerne som afsender på indholdet? 19. Hvordan opleves kontakten med det offentlige? Ønsker til forbedringer hvad kan evt. gøres bedre i forhold til din sidste konkrete kontakt med det offentlige? 20. Hvad var nemt ved borger.dk? Og hvad var særlig godt ved borger.dk? 21. Hvad var eventuelt svært? - herunder svært at forstå i forhold til tekst og begreber? 22. Evt. ønsker til andre muligheder på borger.dk? Obligatoriske testopgaver Alle teams som tester Borger.dk, skal anvende følgende fire testopgaver: 1. Du skal flytte til en ny adresse i Frederiksberg Kommune. Hvem skal du informere om din flytning og hvordan skal du foretage en flytning? 2. Du bor i en privat lejebolig og er utilfreds med den indvendige vedligeholdelse af ejendommen. Hvem har ansvaret for vedligeholdelsen og hvor kan du evt. klage? 3. Hvad er betingelserne for at have ret til efterløn? 4. Lad os antage, at du er på besøg hos en af dine venner i Hillerød. Pludselig bliver en anden gæst meget dårlig og I har brug for at ringe til en vagtlæge. Hvilket nummer skal I ringe til? Hvert team skal desuden selv finde på yderligere mindst seks testopgaver. Præsentationsmøde Nej. I er velkomne til at kontakte kontaktpersonen via e-mail. Copyright 2009 DialogDesign Page 13
Gaver til testdeltagere Borger.dk har stillet fem gavekort på en biografbillet til rådighed for hver af de første 8 teams som melder sig til at teste dette websted. Gavekortene udleveres af forelæseren mod kvittering. Kontaktperson Kommunikationsmedarbejder Christer Bøgh Andersen cha@itst.dk 3545 0211 Supplerende oplysninger Den følgende tabel indeholder de 100 mest søgte ord i borger.dks søgefelt for uge 47, 2008. Report: Page Query Terms - borger.dk Date Range: 11/17/2008-11/23/2008 Page Query Terms (1-100) / 1,451 Count Percent /Soeg/_layouts/BorgerDK/searchresults.aspx k 11,968 100.00% pas 635 5.31% boligsikring 234 1.96% efterløn 198 1.65% blanketter 197 1.65% skat 195 1.63% boligstøtte 177 1.48% sygedagpenge 164 1.37% ældrecheck 153 1.28% kørekort 146 1.22% ejendomsvurdering 137 1.14% kontanthjælp 124 1.04% folkepension 120 1.00% førtidspension 111 0.93% barsel 95 0.79% børnepenge 94 0.79% su lån 89 0.74% su 89 0.74% børnebidrag 81 0.68% dp201 81 0.68% dp 201 81 0.68% pension 75 0.63% smiley 72 0.60% flytning 70 0.58% dagpenge 69 0.58% grå stær 69 0.58% børnetilskud 62 0.52% skattekort 61 0.51% Copyright 2009 DialogDesign Page 14
navneændring 61 0.51% sygesikring 61 0.51% forskudsopgørelse 60 0.50% lægeskift 58 0.48% digital signatur 56 0.47% boligydelse 56 0.47% huslejenævn 55 0.46% toldregler 55 0.46% sygesikringskort 54 0.45% genbrugsplads 53 0.44% børnefamilieydelse 52 0.43% ventetider 51 0.43% affaldstræ 50 0.42% fornyelse af pas 50 0.42% pillepas 47 0.39% bbr 46 0.38% høringsportalen 45 0.38% sygesikringsbevis 45 0.38% dp202 44 0.37% fælles pinkode 42 0.35% bibliotek 41 0.34% studielån 41 0.34% nyt pas 41 0.34% folkeregister 41 0.34% nationalfugl 41 0.34% værktøjskasse 40 0.33% tyveri 40 0.33% boligtilskud 39 0.33% nemkonto 39 0.33% nummerplader 38 0.32% gaveafgift 38 0.32% atp 38 0.32% danmarks nationalfugl 38 0.32% varmehjælp 37 0.31% ejendomsskat 37 0.31% friplads 36 0.30% beregn pension 36 0.30% underholdsbidrag 35 0.29% arveregler 34 0.28% nummerplade 34 0.28% barselsdagpenge 34 0.28% forskudsskema 34 0.28% revalidering 34 0.28% find kommune 33 0.28% beregn boligstøtte 33 0.28% høring 33 0.28% tinglysning 33 0.28% læge 31 0.26% dp401 31 0.26% Copyright 2009 DialogDesign Page 15
borgerservice 30 0.25% vielse 30 0.25% snerydning 30 0.25% særligt børnetilskud 29 0.24% fleksjob 29 0.24% id kort 27 0.23% høringsportal 27 0.23% læger 26 0.22% ældrechek 26 0.22% børnecheck 26 0.22% statsborgerskab 26 0.22% dp 202 25 0.21% job 25 0.21% blå sygesikring 24 0.20% navngivning 24 0.20% sundhedskort 23 0.19% frikort 23 0.19% cykeltyveri 23 0.19% DP 201 23 0.19% varmetilskud 22 0.18% min side 22 0.18% tilskud 22 0.18% ejendomsfakta 22 0.18% blanket 22 0.18% View Total: 6,386 53.36% Total: 11,968 100.00% Help Information Page Query Terms This report analyzes all of the parameter names and values that were used in requests to dynamic content Pages on your website. This report lists all requested Pages whose URL contained query parameters (generally after the? query token). By clicking the arrow next to each entry, you can drill down and see the variable name of each name/value pair that came after the query token. By further drilling down, you can see the values of each variable name. This report is particularly important for analyzing internal search engines and other dynamic applications where all of the interesting information is in the query part of the URL. It can also be used to track pay-per-click and other advertising campaigns, as it allows you to verify the traffic you may be paying for. Links from ads can typically be configured to contain variables even if the landing page is not dynamic. Urchin 5 2005 Urchin Software Corporation Copyright 2009 DialogDesign Page 16
Exercise 3b. Usability test of DSB.dk (Danish) Test the website DSB.dk, the website for the Danish State Railways. Kundens oplæg: Indledning og baggrund: Der blev i november 2008 lanceret en ny udgave af dsb.dk, som er DSBs ansigt udadtil. Det skal her både være muligt at finde oplysninger om trafikken, produkter mm. men også at købe billetter via Netbutikken. Da sitet henvender sig til alle i Danmark, er det af yderste vigtighed, at det er brugervenligt og nemt at tilgå. Det bemærkes, at det ikke er muligt at stille et test dankort til rådighed for køb i Netbutikken, da testen foregår på det kørende system, så testen vil ikke kunne omfatte betalingsdelen af Netbutikken. Oplæg til brugervenlighedstest af dsb.dk Undersøg alle relevante aspekter af brugervenlighed i mindst 4 af følgende områder og flows. Husk at angive i jeres rapport hvilke områder I har valgt. Rejseplan-søgning Orange-søgning Oplysninger om Orange-produkter Trafikinformation Rejsetidsgaranti Finde rundt i DSB's produkter Bestille WildCard Kundeservice Abonnementsservice Pendlerklubber Handicapservice Stationer Kontrolafgifter Service i toget Ledige job Præsentationsmøde Nej. I er velkomne til at kontakte kontaktpersonen via e-mail. Gaver til testdeltagere DSB regner med at kunne bevilge gaver til testpersonerne i form af gæstebilletter eller gavekort til DSB. Teams som er interesserede i gaver til testdeltagerne, bedes henvende sig til kontaktpersonen. Copyright 2009 DialogDesign Page 17
Kontaktperson Mårten Edgren me@dsb.dk 2468 9108 Copyright 2009 DialogDesign Page 18
Exercise 3c. Usability test of Trafikken.dk (Danish) Test the usability of Trafikken.dk, which provides up-to-date information about traffic conditions throughout Denmark. Kundens oplæg: Indledning og baggrund På trafikken.dk, som er Vejdirektoratets trafik site, er udviklet et nyt zoombart kort, der fungerer som den primære formidler af aktuel trafikinformation på det danske vejnet. Kortet er tilgængeligt via forsiden på trafikken.dk eller via direkte link: http://www.trafikken.dk/wimpdoc.asp?page=document&objno=127861. Fælles for informationen om den trafikale situation på de danske veje er, at den er stedsbestemt, dvs. informationen er tilknyttet et eller flere geografiske punkter, og illustreres således bedst vha. kort. 1 På trafikken.dk har man siden 2002 benyttet digitale kortapplikationer til formidling af trafikinformation, men har ikke før nu været i stand til teknisk at lave en dynamisk kortapplikation, der er mulig at benytte i en bred vifte af de mest benyttede browsere uden ekstra plug-ins (herunder Internet Explorer og FireFox). Det zoombare kort, der ønskes testet, blev publiceret på trafikken.dk den 4. december 2008. Målgruppe Kortets målgruppe er danske trafikanter. Forslag til testindhold Testen af kortet ønskes foretaget med fokus på brugernes intuitive brug af kortet og dets funktioner. Det kunne med fordel gøres med udgangspunkt i en kvalitativ undersøgelse af hvordan navigeringen rundt på kortet fortages samt hvordan informationer opfattes, dvs. sammenhængen mellem overskrifter (linktekster) i kortets menu og selve indholdet (tekstinformationen). Hertil vil 1 Denne form for informationsformidling betagnes ofte som geokommunikation. Læs mere her: http://www.geokommunikation.dk/ Copyright 2009 DialogDesign Page 19
det væres interessant at få undersøgt nærmere, hvordan brugerne benytter kortets funktioner, som f.eks. funktionen send kort. Brugere af kortet kan erfaringsmæssigt opdeles i to grupper: 1) Brugere, som er alment nysgerrige i at få et overblik over trafiksituationen. 2) Brugere, som søger en målrettet information. I forhold til den sidste gruppe kunne det være hensigtsmæssigt at tage udgangspunkt i konkrete brugerscenarier så som planlægning af en konkret rejse fra A til B. Kontaktperson Er der spørgsmål eller kommentarer til kortet eller indholdet kontakt da venligst Jacob Langebæk Hegner (jlh@vd.dk), direkte tlf. 7244 3415. Hvis gruppen har interesse i et formøde kan det arrangeres. Præsentationsmøde Onsdag den 7. januar kl. 15.00-16.00 på nedenstående adresse (Niels Juels Gade 13). Spørg efter Jacob Langebæk Hegner. Gaver til testdeltagere Vejdirektoratet har principielt erklæret sig villig til at give alle testdeltagere vin eller gavekort. Dette vil blive diskuteret nærmere på præsentationsmødet. Hvis dit hold vælger ikke at være repræsenteret på præsentationsmødet, så er det ikke sikkert at I kan få stillet gaver til rådighed til jeres testdeltagere. Kontaktperson Jacob Langebæk Hegner Vejdirektoratet Trafik- og Beredskabsafdelingen Niels Juels Gade 13 Postboks 9018 1022 København K Telefon 7244 3333 Direkte 7244 3415 Copyright 2009 DialogDesign Page 20