From: Paul Dourish Date: Mon May 19, 2003 11:33:22 PM US/Pacific To: Multiple recipients of list <36195-s03@classes.uci.edu> Subject: Final report requirements Reply-To: jpd@ics.uci.edu After you do your evaluations (week 9) and your presentations (week 10), the last thing that's due is a final report on your project. It is due by 4pm on Friday of week 10. The report will be similar to the one you generated for the paper prototyping, but more detailed. The report should contain the following sections (in this order): Background to the design. Who are your intended users? In what context will they use the system? What problem are you trying to solve for them? Your design. Start off with a high-level description. What's the basic approach you've taken? What principles have guided your design? What were the effects you were trying to achieve? (Don't say "ease of use" or "user-friendliness" -- be specific). In particular (and this is IMPORTANT), explain how your design approach is related to the ideas from the previous section. How does your design match the needs of your users? Only after this should you go down into design details. How does your design work? Briefly summarise the outcomes from the paper prototyping experience. I've already read these, but remind me what your experience was the first time around. Just a page or two. Now describe the week 9 evaluation. Things you must discuss include the specific issues you wanted to investigate in your design (again, not just "whether it was usable" -- have specifics in mind.) Describe the tasks you asked users to perform, and what happened, as you did for the paper prototyping. Tell me about each user separately. As for the paper prototyping, explain what changes you feel are warranted or suggested by the evaluation experiences. Finally, explain what remains to be done -- further explorations, development, features that you think would be needed but that you didn't get to. I would expect this to take at least 30 pages, double-spaced; if you write more than 50 pages, single-spaced, then you're writing too much. --p.