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.

<MCE:STYLE></MCE:STYLE><STYLE mce_bogus="1"><!--
.pagetree2 a

Unknown macro: {font-size}

--></STYLE>

Unknown macro: {pagetree2}

Click on a page above for a specific section.

Computer Prototyping

Platform and Software Requirements

Our prototype can run on any modern browser and any operating system. We have tested our code on several browsers and it seems to work best on Chrome.

Instructions

Accessing the Prototype

Our software is accessible at the following URL: http://rytaft.scripts.mit.edu/6.831/GR4/src/biomate_login.html.

Tasks to Evaluate

The following tasks can be helpful during the evaluation process:

  1. Log in as a lab-bench biologist using the following login credentials (the canned data corresponds to what a lab-bench biologist might see):
    • username: alpha
    • password: beta
  2. Use "Monte Carlo" script.
  3. Use "Monte Carlo" script from history.
  4. Browse your notes and look at your notes on "Monte Carlo".
  5. Log in as a computational biologist using the following login credentials (the canned data corresponds to what a computational biologist might see):
    • username: gamma
    • password: delta
  6. Create a new script.
  7. Edit "Monte Carlo" script from history.

You might play with the interface. We have implemented enough of the functionality so that you should be able to see all of the screens we have designed. All buttons on the home screen should link to the correct screens (notes, history, add/edit a script, use a script), and buttons on these screens should show popups and tooltips with canned data. Selecting scripts other than "Monte Carlo" should not cause the interface to crash; you may not see any output or the output you see might not make sense.

Prototype information

Canned Elements
  • You can login with only two username-password pairs as mentioned in the instructions.
  • You can use only "Monte Carlo" script since we have created all of our screens with canned data corresponding to the "Monte Carlo" script which was used in our paper prototype scenario.
  • The notes, instructions and parameters associated with "Monte Carlo" script are all canned.
  • Clicking "Edit" for any script in the "History" popup shows an image of the "Create/Edit Script" screen with some items filled in, and is therefore not interactive.
Incompletely Implemented Elements
  • Home/Login screen:
    • We did not implement the "create account" feature and the "login" functionality is incomplete in the sense that it uses canned data.
  • Create/Edit a Script screen:
    • The "Delete" and "Edit" buttons do not allow you to delete or edit any parameter or static text.
    • The "View/Edit" buttons in the parameters table do not work.
    • Changing the "Alias" or "Prefix/Flag" in the parameters table does not update the draggable chunks.
    • Setting input type to "Flag" does not disable the "Required" checkbox.
    • We do not check for invalid or blank parameters.
  • Use a Script screen:
    • From the "Generate Command" popup, Save to Notes and Copy to Clipboard do not work.
  • General:
    • When you click buttons that would require mostly back-end work such as Save, Share, etc., nothing will be saved, even if feedback is displayed on the UI confirming the action.
    • When you click "Send" to send an email, nothing will be sent.
  • No labels

5 Comments

  1. Unknown User (ryfeus@mit.edu)

    HW2.pdf

  2. Unknown User (joor2992@mit.edu)

    Hope this is helpful. Best of luck. HW 2.pdf

  3. Unknown User (apagan@mit.edu)

    heuristic-evaluation.pdf

  4. Unknown User (jks@mit.edu)

    • Wiki presentation: Great task instructions and description of prototype depth
    • Fidelity: 
      • Beautiful computer prototype, with high fidelity in both look (great use of bootstrap, very true to your paper prototypes) and breadth (creating, editing, using scripts, along with other features like history and note-taking).
    • Usability: 
      • Nav bar could include global navigation to create/use scripts, history and notes.
      • Great animated overlays throughout your site (e.g. on Copy to Clipboard) to reduce unnecessary page navigation. Great feedback on actions (saving parameters and notes)
      • Use Script:
        • Consider displaying instructions and my notes inline, just like caveats. Good to keep things simple, but these important pieces of information might go unnoticed.
        • Load parameters should be more prominent, in case users just keep re-filling settings manually.
        • Great help popups for parameters.
        • Is there a way to integrate a script's run history into the 'Use Script' page? Might be a more natural place to seek out a script's run history.
      • Create/Edit script:
        • Good autocomplete for script name, and great flow in general for specifying a command.
        • Can potentially put the help text from 'More Information' button into a help popup, like in the Use Script page.
        • Unclear sometimes if static text / warnings / tooltip need input surrounded by quotation marks.
      • Graphic design:
        • Gridding on Use Script page could be better.
        • More prominent title/logo in nav bar.
        • Home page is cool with good icons, but you should improve information scent with text labels.
        • Also, not clear what the blue symbol is...might want to think of a logo or some kind of metaphor that has something to do with comp. bio/terminals/scripts/something.

  5. Unknown User (adorne@mit.edu)

    Here's my evaluation. Sorry its a little concise but I hope it helps! Please let me know if you have any questions! adorne@mit.edu

    HW2.pdf