






SPEW Usability Test Results
Below is a list of tasks we asked our customer to try, and their evaluation of the ease/intuitiveness of carrying out the task.
ODIN application.
- Run ODIN (randomwalksim) and capture the events to a log for visualization.
- Evalation: Very easy.
Preproccessor.
- Run the preprocessor on the log to generate the ONA file.
- [The customer found the preprocessor easy to run, but we had a critical bug where there was no output, which we've now fixed.]
Graphviewer.
- Launch the application.
- Evaluation: Very easy.
- Choose an input file for the application.
- Evaluation: Very easy.
- Go to 2.0.0.255.
- Evaluation: Very easy.
- Display IP Addresses.
- Evaluation: Very easy.
- Hide IP Addresses.
- Evaluation: Very easy.
- Add breakpoint to next query.
- Evaluation: Very easy.
- Step through each event after a breakpoint.
- Evaluation: Very easy.
- Is the information displayed on the screen useful?
- Evaluation: Very useful.
- Resume Simulation.
- Evaluation: Very easy.
- Remove breakpoint from next query.
- Evaluation: uneasy (4 on a scale of 10) - it's unintuitive
- Identify links with most traffic.
- Evaluation: Very easy.
- Show all links.
- Evaluation: Very easy.
- Switch to viewing another file.
- Evaluation: Very easy.
- Restart simulation from the beginning.
- Evaluation: Very easy.
- Should program pause playback when the user enters a timestamp?
- Evaluation: Yes - this is what the program does so it's intuitive.
- Possible Bug: The paused line should be >= entered timestamp. Not so when tested with 1,000,000 milliseconds.
Link to this Page
- Team SPEW last edited on 27 April 2006 at 9:26 pm by r69h15.res.gatech.edu