From: "Corey L. Carlson" <corey@itlabs.umn.edu>
Message-Id: <199802220055.SAA04277@trout.itlabs.umn.edu>
Subject: Testing.
To: calvin-ui98@dagobah.stwing.upenn.edu (ui 98)
Date: Sat, 21 Feb 1998 18:55:30 -0600 (CST)
Has anyone heard back from the other group? Is it tomorrow or Monday?
Here is the results from fleshing out the scenario 4 walkthrough.
Since some of these may disappear with the next level of pared down
functionality I don't know how useful this will be.
---- Beging cog walk ---
Questions to be answered in the walkthrough.
Q1. Will users be trying to produce whatever effect the action has?
Q2. Will users see the control (button, menu, switch, etc.) for the
action?
Q3. Once users find the control, will they recognize that it produces
the effect they want?
Q4. After the action is taken, will users understand the feedback they
get, so they can go on to the next action with confidence?
Q5. Is there another control that user might select instead of the
correct one?
User is given the task #4
4) create an archive in the /web/fun directory from three mail boxes
john, mark, sue in the /project/mailboxes directory.
1. Open Mailbox Archive program by typing "mac.tcl".
The first thing to do is to get the software running. To do this
requires typing:
wish8.0 mac.tcl
at the prompt. This is learned and not part of the interface but is
required to get the program running.
2. Click on "Are there multiple input mailboxes for one ouput archive?" radio
button.
Q1. 10% yes
In the first screen I'm afraid the user will skip the text,
kind of like a README file. Why read the instructions? If they go on
from there they will likely not have all of the options they need turned
on. (Perhaps force them to check something before they continue?)
Q2. 100% yes
Q3. 10% yes
The tabs become active, but as a user I may not "want" to filter. Like
not wanting to scroll to see the rest of the document I may not "want"
to filter messages. I just want to prevent messages with subject X from
going into the archive. (I cannot think of a good way around this.)
Q4. 25% yes
It's kind of a guess where to proceed from here. Maybe after you check a
box you get a message somewhere on screen that says "After selecting all
that apply continue with the mailboxes tab." or something to that
effect.
Q5. yes. It is possible to choose another tab or just set the working
directory and move on. In this scenario it would be an error to do so,
but for another scenario the default would be correct.
3. Click on Mailboxes tab.
Q1. 75% - left to right mapping helps keep the user moving to the next
pertinent tab.
Q2. 100% yes
Q3. 75% yes - It is still the same question as Q1. Will the user select
the appropriate tab?
Q4. 100% yes
Q5. user may click on a different tab or chose to try other controls in
the previous window.
4. Click on browse.
Q1. 100% yes
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. The user may choose to explore other tabs instead of exercising the
necessary controls in the current tab.
Assuming the user made it to this window there is not much else
here. Perhaps a relabeling "add mailbox" to "add path to mailbox" or
something that more distinctly says "I'm looking for the path to the
mailbox" rather than a name for a mailbox.
5. Navigate to /project/mailboxes/john
Q1. 100% yes
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. No, file selection dialogs are standard and people are comfortable
with them if they have even a small amount of computer experience. When
all else fails use a standard.
6. Click Add.
Q1. 90% yes
A few users may think that the browsing has selected it for them,
perhaps automatically adding a non-null file path should be automatic
and not require the add button.
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. No, unless the user would choose to leave the tab before adding the
second mailbox
7. Click on browse. (same as step 4)
Q1. 100% yes
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. The user may choose to explore other tabs instead of exercising the
necessary controls in the current tab.
8. Navigate to /project/mailboxes/mark
Q1. 100% yes
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. No, file selection dialogs are standard and people are comfortable
with them if they have even a small amount of computer experience.
9. Click Add.
Q1. 100% yes
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. No, unless the user would choose to leave the tab before adding the
third mailbox
10. Click on browse. (same as step 4 & 7)
Q1. 100% yes
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. The user may choose to explore other tabs instead of exercising the
necessary controls in the current tab.
11. Navigate to /project/mailboxes/sue
Q1. 100% yes
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. No, file selection dialogs are standard and people are comfortable
with them if they have even a small amount of computer experience.
12. Click Add.
Q1. 100% yes
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. Probably not. The user has already added 2 mailboxes it is likely that
the user would click add for the third before proceeding to the next tab.
13. Click on the archives tab.
Q1. 75% - left to right mapping helps. (Perhaps some prompting that
archives would be a good choice for their next action?)
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. user may click on a different tab or chose to try other controls in
the previous window.
14. Type an archive name in the New archive box.
Q1. 50% yes
The person may not realize that an archive name is required. The only
thing they really understand on this page is where to put the
output. Otherwise you shouldn't be able to specify an output directory
if you haven't given the archive a name.
Q2. 100% yes
Q3. 100% yes
Q4. 50% yes
The user may not realize that they have simply entered a name and not
the path to the output directory. The user may feel like she is entering
the path twice.
Q5. Yes, the user may bypass the naming stage and go on to more
understandable things like the output directory. If you specify the
lower stuff first it gets overwritten with defaults.
14. Type in /web/fun for the output directory.
Q1. 100% yes
Q2. 100% yes
Q3. 90% yes Feedback is a little lacking, but possibly unavoidable.
Q4. 100% yes
Q5. The user may choose to explore other tabs instead of exercising the
necessary controls in the current tab.
15. Click on the generate tab.
Q1. 75% yes In this case the user may select the processing tab for
which the defaults are sufficient. Perhaps it should still be grey?
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. yes, they may pick the processing tab instead of generate.
16. Click on generate.
Q1. 90% yes
When all of the necessary conditions are met what is the signal? Should
something say "OK to generate" or highlight the button once necessary
conditions are met?
Q2. 100% yes
Q3. 100% yes
Q4. 100% yes
Q5. no, save switching to another tab, but if they got this far they
shouldn't want to go back.