You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

BioMate

Lab-bench biologists find it difficult to use many existing tools for their data analysis. These tools are generally command-line computer programs written by computational biologists. Computational biologists do not have time to create user-friendly interfaces for their programs, and often find themselves spending a lot of time helping lab-bench biologists run their programs. This creates a burden for all involved: lab-bench biologists cannot move forward with their data analysis, and computational biologists cannot move forward with their research.

html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list.

<STYLE>
.pagetree2 a

Unknown macro: {font-size}

</STYLE>

Unknown macro: {pagetree2}

Click on a page above for a specific section.

Paper Prototyping

Prototype Photos


This is the login screen that both computational biologists and lab-bench biologists see. Our first high-level task was for computational biologists to add a new script, so they clicked "Add/Edit Script".

 
This is the screen that computational biologists see after clicking "Add/Edit Script". By clicking "Add text" and "Add parameters", they can construct the command structure that lab-bench biologists will use to run their script. They can also enter caveats and user instructions for the lab-bench biologist, then save or share the script.


This is the popup that a computational biologist sees when clicking "Add text" from the "Add/Edit script" screen. This is where they enter static text in the command such as "perl montecarlo.pl" or "| less".


This is the popup that a computational biologist sees when clicking "Add parameter" from the "Add/Edit script" screen. This is where they enter information about each of the parameters that the lab-bench biologist will have the option of setting when running the script.


This is the popup that a computational biologist sees when clicking "Share" from the "Add/Edit script" screen. Here they have the option of sharing the script with their existing contacts in BioMate or entering an email address.


This is the login screen that both computational biologists and lab-bench biologists see. Our second high-level task was for lab-bench biologists to run a script, so they clicked "Run Script".


This is the screen that lab-bench biologists see after clicking "Run Script". By clicking "My Notes on Monte Carlo", they can view any notes they have previously created on the Monte Carlo script. By clicking "Instructions", they can view any caveats or instructions written by the programmer. Then the lab-bench biologist can enter the parameters and generate the command.


This is the popup that a lab-bench biologist sees when clicking on "Instructions" from the "Run script" screen. It shows both caveats and instructions shared by the computational biologist.


This is the popup that a lab-bench biologist sees when clicking "Generate Command" after entering the required and optional parameters. Here they can copy the command and paste it into a terminal to run. They also have the option of saving the command to their notes.


This is the popup that a lab-bench biologist sees when adding a note on a particular script. They can see all previous notes on this script as well as previous versions of the command they have saved to their notes.


This is the popup a lab-bench biologist sees when clicking on "Save Parameters" from the "Run Script" screen. This allows them to save all the parameters for a particular run with a unique name.


This is the popup that a lab-bench biologist sees when clicking on "Load Parameters" from the "Run Script" screen. This allows them to load parameter that they have previously saved for the given script.

Briefing

Scenario Tasks

Observations: Monday's User Testing Session (Round 1)

User Testing Descriptions

Changes for Round 2

Observations: User Testing on People From B Lab (Round 2)

User Testing Descriptions

Issues to Consider/Resolve

  • No labels