CS 565: Introduction to HCI
Final Report Structure Details

Your final written report should be structured in the following sequence:

• Chapter 1 (Introduction): Use your Project #1 as a starting point, but update the chapter to reflect anything that is now different. For example, if you needed to choose different scenarios, replace what you originally wrote with these new scenarios.
• Chapter 2 (Results of the GenderMag Heuristic Evaluation): Your Project #2 was a starting point, but during Project #4 you updated it to include some "Bug" IDs. If you need to label any more Bugs, go ahead and update it to be up-to-date.
• Chapter 3 (Results of Empirical Observation): Your Project #3 was a starting point, but during Project #4 you updated it to include some "Bug" IDs. If you need to label any more Bugs, go ahead and update it to be up-to-date.
• Chapter 4 (Results from Other Activities): Your Project #4's chapter with your results from the in-class activities was a starting point. If you need to add more results or label any more Bugs, go ahead and update it to be up-to-date.
• Chapters 5-n: The rest of your chapters:
  • One chapter for each scenario you defined in Chapter 1. Each scenario chapter contains:
    • Each screen (screenshot from your Mockups prototype)
    • Annotate and/or otherwise detail for that screen what you changed and your justifications of why these changes. Refer to the Bug IDs in earlier chapters, and the justification for the change you made (eg, Gestalt Proximity, TandT#25, Norman's "Affordance", Feedback from Design Gallery, or whatever you used.
    • About repetition: It's not necessary to say the same things over and over. If you have a lot of screens with similar changes, it's fine to backward-reference explanations you've already given. For example, if you changed a navigation bar that shows up on every screen, explain your changes to it the first time they're visible, then refer back to that explanation on subsequent screens.
  • If you need some additional chapters before or after your scenario chapters, feel free to add them.
• Appendices as needed

See also the Project page for additional items to turn in with this report.

---

Date of last update: May 31, 2018.