CS124: Investigation 8

Pen-Based Interfaces

Due (officially) Friday, December 14, 5pm
(unofficially) Monday, December 17, 5:30pm
on Sakai

This is a pair investigation.   You can work with anyone you want on this investigation.

A note on extensions: You may not use extensions beyond the Monday, December 17 unofficial deadline.  That is, all assignments are due Monday, December 17 at 5:30pm.

Goals

The goals of this Investigation are:

Before you Begin

Assuming you have done the reading for Monday, Dec 3, you are ready to get started.

Assignment

This assignment asks you to design and prototype a sketch-based user interface. You will use the SketchWizard tool to prototype your interface, and then you will critique the SketchWizard tool from a UI perspective.

Part 0: Handling Tablet Logistics

Everyone will need to use a Tablet PC for this assignment.  You will need two tablets per pair so that you can have one tablet for the Wizard and one for the user.  You will receive these Tablets in class on Monday.  You must return the tablet to me by the assignment deadline.  

Once you have your tablets, install and set up SketchWizard on both computers.

Part 1: Choose your domain

Choose a task set/domain for which you will develop a pen-based interface.  You can choose any domain you like.  You can copy an existing interface, as in the study in the SketchWizard paper (e.g., DENIM, Journal, MathPad^2, a tool for circuit design, etc), or you can choose a new domain.  It's up to you, but don't spend too much time thinking about this part (it's not the point of the assignment).  You should develop two tasks that your interface will support (like we did in previous assignments).  Try to choose a domain where the task analysis is already done.

Part 2: Design your interface

Based on some sort of task analysis (either a quick one that you do, or a task analysis based on an existing interface), design a lo-fi prototype of your interface on paper.  As when we did paper prototyping, make sure your prototype is broad enough to handle two (not three, this time) specific tasks that you will ask your users to perform.

Part 3: Prepare to test your interface using SketchWizard
Now, prepare to test your itnerface (on your two designated tasks that you identified above) using SketchWizard.  This will involve learning to use SketchWizard and praticing... ALOT.  You need to practice until you are completely confortable using SketchWizard.  You should get to the point that users will not (obviously) know that it's a human operating the intetrface.  Each of you should become expert wizards.  You will demonstrate your expertise in class on Wednesday, December 12.

Part 4: User Testing

Test your interface with at least 4 users using SketchWizard.  For two tests, one of you will be the wizard and the other will run the study.  Then you will switch roles for the other two users.  

Use the same testing methodology as you did in your paper prototyping investigation, only this time one of you really will be the "computer".  You should develop and introductory script and written tasks just like you did before (you will hand these in).  For this study, we will not inform the user that a human is operating the interface.  The wizard should be out of sight from the user.  You can tell your subjects that the interface is an early, slow prototype, running over a network connection (which is all true).  You should debrief the user about what was actually going on after the study is complete.

As usual, the facilitator should take notes about any usability problems you discover during the process, but the wizard should also keep in mind what was difficult for her or him.  Immediately after each subject, the wizard should make notes about what was easy or difficult to use with the interface.

Part 5: Analysis

Write a short critique that addresses the following:
  1. Your interface: Identify a few (at least 2 significant, or 3-4 minor) issues with your original interface that your testing revealed.  For each issue, clearly state:
    1. The users' behaviors or comments that led you to believe this is indeed a problem with your interface
    2.  A suggestion for how to change your interface in response to address the problem.
  2. SketchWizard as an interface testing environment:  As usual, focus on the specific UI issues we have discussed in class.  At the same time consider: Specifically based on your experience, what advantages does SketchWizard provide over prototyping on paper?  What do you think that you might have been able to do better with a strictly paper prototype?  What does it do well?  What could it do better?  Make sure you justify all of your claims with specific obeservations and experiences from your own use.
What I mean by "short" is long enough to fully address all the points above, but just long enough to do so.  Probably around 2 pages, single spaced, but this is flexible.  Again, the focus is on content, not quantity of text.

What to Hand In

Back to CS124 Investigations Page