Hey folks,welcome back. This is professor Hecht here. You'll notice that I'm a little stiller than usual and it's because I had to be off site to record this lecture. But we did want to make sure we got you a video on the assignment you're going to have to be doing on heuristic evaluation. So this is that video. Okay, this assignment has three primary objectives. First and foremost, we want you to become fluent in basic heuristic evaluation. We think we've designed an assignment here that definitely will accomplish this, you'll fully understand, sort of what goes in, what goes out and how to write-up to sort of basic heuristic evaluation reports. Secondly, we want to make sure you get some practice thinking of solutions to problems identified in heuristic evaluation. And then third, we want you to appreciate design that addresses some of the heuristics that we have talked about. So before you get started on this assignment, we'd like you to review all the heuristic evaluation videos especially if it's been a while since you watched them. And in particular, pay attention to the introduction, introduction to heuristic evaluation because that's where we cover a lot of the process associated with heuristic evaluation. All right, so here's the basic outline of your assignment. You're going to be responsible for filling out five heuristic evaluation reports. And in each of these reports, you're going to find an application, a website, or a technology that's been deployed but that violates one of the ten heuristics that we've covered in this module. You're also going to have to submit two reports of heuristic evaluation success stories. And in each of these success stories, you're going to find an application, website or technology again, that's in the real world but that has a feature design element that clearly addresses and solves, if you will, one of the heuristics that we have covered in this module. Across these seven different reports, five problem reports and two success stories, we're going to expect that you focus on five different heuristics of the ten that we've covered in this module. And then lastly this assignment is going to be peer evaluated and that's a critical part of the assignment. We want you to both generate these reports as well as consume them and see what your peers have found in terms of problems and success stories. Okay, a bit more about each of these reports, remember you going to have to do five of these. They're all going to be based around a violation of a heuristic in an application, website or technology that's in the real world. For each of these violations, you're going to fill out a template form about the violation. You're going to aggregate all five reports into a single PDF and then you're going to upload that PDF. And as I mentioned above here, there is a report template for you, please use that not for me but for your colleagues who will be evaluating your assignment. It makes things a whole lot easier. And then here's an example of a filled out template. You can see that I have listed the application or website name. This is using the Google Maps example that we saw earlier in this module. I'm just providing a description of the application. This is particularly important if it's a specific professional application or an application that's specific to say your country, say Ukraine or something like this that the whole world maybe wouldn't recognize. Critically, I've listed the heuristic that I think was violated. I've indicated a severity score of 3. I've provided a screenshot and this is optional but helpful to your evaluator if you use simple drawing tools. In this case, I just used drawing tools in Word to point out the part of the screenshot that is particularly important to understand the violation of the heuristic. And then below the screenshot, you can see, I've provided a couple of sentences, for an explanation of the problem and a justification of my severity ranking. And then critically, lastly, I've listed at least one way to solve this problem. With regard to the solutions, don't worry if it's going to cost a million dollars or require a development team of ten, right? Your job here is just to think about design and think about a potential solution. All right, so you have five heuristic evaluation reports and you have two success stories. And this is a bit more about the success stories. For each of them, we want you to find a feature or a design element that clearly addresses one of our 10 heuristics. And then we want you to reference the heuristic and write a description of how the feature or the design element addresses the heuristic. Again, you're going to have a template, we want you to aggregate both success stories that use the template into a single PDF and you're going to upload that to Coursera. So there's an example of a filled out template for a success story. You can see this is the Amazon.com buy 1-click example that we saw earlier in the module. The most important thing to point out here is again the screenshot with the drawing tool pointing out the part of the interface for my colleague, who will be evaluating this assignment. And then you'll see below an explanation of how this feature or this design element clearly addresses the heuristic. In this case, flexibility and ease-of-use. You can see, that listed as the third element in this template, in particular I have noted that this is an accelerator which is a clear way to address the flexibility and ease-of-use heuristic. Okay, with regard to the heuristic evaluation reports, we're going to have you guys evaluate the reports using a simple 3 point scale. So you get 2 points for having the heuristic be correctly applied and severity assessment be reasonable. 1 point, if the heuristic is correctly applied, but the severity assessment is not reasonable. And then no points if you've indicated the wrong heuristic. And with regard to the success stories, you'll get 2 points if the explanation justifies the selected heuristic. And you won't get any points if that's not the case. And then lastly, a couple of tips for evaluating your colleagues and friends. And we want you to grade somewhat easily, particularly with regard to the severity scales. Recall that, in heuristic evaluation, typically, you average several evaluator severity scales and that's because there is some expected natural variation. So only mark them down if, for instance, it's clearly a four but they indicated a one or something along these lines. And then we really want you to engage with your colleagues work. This evaluation should be fun right? Your colleagues have come up with clear problems in real world interfaces. And this is an opportunity for you to engage with those problems. Engage more of the heuristics and hopefully have a little bit of fun too. All right, that's it for me and I'll be seeing you in the next video.
