Hi, I'm Bonnie. >> And I'm Aleve. >> And today, we're going to show you an example of how to do heuristic evaluations. Aleeve will be the computer, and he'll move the pieces of the prototype around while I, the evaluator, will tap around and note any usability issues that I find. >> In this prototype, there's going to be an application where the student can go and schedule appointments to meet with their professors. Notice in this example, the group added stickers to some of these screens. You don't want to lead the witness. Your evaluator should have free rein to explore as they wish. >> So I also printed out a work sheet with all ten heuristics on them. This will make it easier for me to find usability problems and note them down quickly, you can make your own online. So let's get started, so this is the first screen and I don't even know what prototype I'm testing because there's no name on it so I'll just create an account. So here I'm going to make a username and password and then pretend to be a professor and click create. I'll fill out my name and then I don't want to set up my profile so I'll just click Skip. Here is the home screen. It looks like I can view appointments, set availability or edit my profile. What if I want to view my profile? It looks like there's no way to view my profile. So I'm going to put that down as a problem of User control. Chat view profile. And I'm just going to set availability first. Here I see their start and end times, and I can check some days of the week, and add a location. I think there are a few problems here. So, I noticed that, one there's only dates of the week but they don't tell you which day it is. I think the actual date is very important and two, I think there's an issue of flexibility and efficiency of use, because if I were a professor and I use this a few times. I think, usually I would meet in the same locations and I wouldn't want to fill this out every time. So I think there should be a faster way to go through this process. So I think, I'll put down advance users function under flexibility and efficiency of use. So let's submit some times. So here are all my available times that I set. It would have been really nice if I was able to see this before setting some times, but that didn't seem like it was available. So I'll add this to visibility of system status. That I should be able to see the terms before him. Now let's close this And let's go home. So let's view my appointments now. So it says click on appointment to view details. So I'm guessing this is my appointment, click this okay so I have an appointment Tuesday January 20th with some student what if I can't make that time anymore. It doesn't look like there's a way for me to cancel it. I'll note that down under user control, can't cancel. So let's close this. And go home again. All right, so, I'm not interested in editing my profile, so, I'll just sign out and let's check out the student side of this prototype. All right, let's sign in. Okay, so, I notice that there was a forgot password here on the previous screen, but it's not here anymore. And also there is no forgot username screen. I think that would go under error prevention. If someone forgets their username, this prototype isn't able to account for it. So, forgot username. So let's sign in. All right, so here I want to make an appointment with a professor. So I'll search for the professor that I want. Let's see, I'll just add the name, Scott Klemmer. And I found Scott Klemmer. So I'll click on that. Let's see, so this is his profile. Actually, if I didn't want to make an appointment with him it looks like there's no way to go back or to cancel. So that's another problem of user control and freedom. That I must make an appointment now. So, I guess I'll make an appointment for Monday 5 to 7 pm and make appointment. So it looks like, in the time range of 5 to 7 pm I have to choose a 15 minute time slot. So I'll choose 5, 5:15 and hit Submit. Success, appointment made for Tuesday January 20 at 5 PM. I thought I'd put Monday this must be a minor error just in writing but I'll just note that down under consistency and standards. Monday changed to Tuesday. All right, so let's close this. Well, I think let's just end it here. And I have some general comments about the prototype. So one thing I noticed was that there was very little help documentation in the prototype. So there was one screen that I really like, it was the one with the calendar on it for professors. So this one was the only one that had any sort of instructions or help for me, it says click on the appointment to view details but for the rest of the prototype, it doesn't really give me any information on how to go about using the prototype. I think, it would have been really helpful to add a little bit more of that. So, I'll just note that down and hope that documentation, need more help. So, the other thing I noticed was that a lot of the prototype pages looked very different from one another. So this would make it really difficult for me to remember what page I'm on or how to continue using it because they looked so different. I think I'll write that down as a problem in recognition rather than recall. The pages are too different, too different. I think one thing that was really good about the prototype was that the match between the system and the real world seemed pretty good to me. The language that they used was rather intuitive, so it wasn't too hard for me to go through the prototype, even though I think that more help and documentation would have been better, but I'll note that down as a positive. Good match between system and real world. So, let's count how many that I have, one, two, three, four, five, six, seven, eight, nine, so I found ten. Ten, nine usability issues and one positive about it. So, that just goes to show that in one prototype, I was able to show, to find ten of them and if you really look, there are a lot of usability issues that you might be able to find. The last thing is that some of these issues apply to more than just one heuristic. And it's up to you decide which one might be most important and decide where to put the usability issue.
