Goal:

The goal of this assignment is to complete the final iteration on your project prototype and write up a summary of the entire project.

UI Redesign:

You have performed a pilot usability study of your prototype. Incorporate all the changes suggested by this study that you can into the final version of your UI prototype. The prototype should be frozen (that is, not modified further) by the due date of this assignment.

Write-up:

This is a group assignment, so please work as a group. Note which parts each of your team members contributes to.

A runnable version of your prototype must be available off of your project web page along with information on how to use it.

Your write-up should be comprehensive (including sketches and screen dumps). It is due on both the web and on paper on the due date shown above. Your entire write-up and web page should be up to date with all of the files stored locally (so that we can just copy the site for our archives -- links should be relative.) It is ok to reuse text that you've used for other assignments, so long as it is up-to-date.

The write-up should follow this outline (number of pages/section are approximate):

1. Problem (1 paragraph) this is the need you have been trying to solve with this application all semester
2. Solution Overview (1 paragraph)
3. Tasks & Scenarios (1 page + screen shots)
   • tasks used for design process
   • list and describe the final 3 task scenarios and why you chose them
   • storyboards of scenarios (using finished screen shots)
4. Design Evolution (2 pages + sketches & screen shots)
   • How did your UI change from initial sketches, low-fi testing, HE, and final usability test?
   • Show what the major changes were and why they were made
   • Which of the three evaluation technique (low-fi prototype run-through, heuristic evaluation, pilot usability test) was most valuable to your prototypes usability and why?
5. Final Interface (4 pages + screen shots)
   • Describe the final UI design
   • Describe the functionality (i.e., what you can do with it)
   • Describe the user interface design (i.e., how you use the functionality)
   • What was left unimplemented?
     • what was left out and why
     • any wizard of oz techniques that are required to make it work
   • Tools you used
     • tools for prototyping and implementing the UI
     • how the tools helped and how the tools did not help

Class Presentation:

Timing

Final project presentations will take place Tuesday May 4 and Thursday May 6. People need to be in class in their seats by 11:10 and no later on both days. We have to be out of the room by 12:30 and no later on both days.

We will go in reverse project order for presentation of final projects. This means that P12, Anti-Spam goes first, then P11, and so on. The first group on each day must come in early and be set up to go by 11:10. This means the anti-spam project and the bookstore project.

We will be having five groups each day. The timing is going to have to be very strict. If we do the math we see:

80 minutes/5 groups = 16 minutes per group.

If we assume it takes 5 minutes for one group to finish and the next to start then we have to assume there is time for only 11 minutes per group. Since small gliches happen we will reduce this to 10 minutes per group.

This means that if you talk for 10 minutes there is no time for questions. Therefore, your talk should really only be about 8 minutes long. It can be shorter if you want to have time for more questions. One group can continue to answer questions while the next is setting up.

It is imperative that you practice your presentation in advance and get the timing down perfectly. This time I will subtract serious points from your final project presentation if you go over. Dan is going to be holding the stopwatch so I can pay attention to the content.

Format

The following talk structure is recommended:

• An overview of the problem the interface addresses and the goals of the system.
• The goals of the pilot usability test and a high-level description of the experiment design.
• A tour through the final UI design:
  • Highlight what changes were/will be made in response to the user testing.
  • Mention what was the most surprising thing revealed by user testing
• One UI design or evaluation lesson to give to the class based on your experiences with this project.