Team:Wellesley Desyne/Human Practices

From 2013.igem.org

(Difference between revisions)
 
(90 intermediate revisions not shown)
Line 1: Line 1:
 +
{{Team:Wellesley_Desyne/css/wp_app.css}}
<html>
<html>
<head>
<head>
-
<title>Wellesley HCI iGEM Team: Human Practices</title>  
+
<title>Wellesley HCI iGEM Team: Welcome</title>
-
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-
<meta charset="utf-8">
+
<meta charset="utf-8">
-
<meta name="viewport" content="width=device-width">
+
<meta name="viewport" content="width=device-width">
-
 
+
<link href='http://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet' type='text/css'>
-
<style type="text/css">
+
-
 
+
-
/* Hiding predefined html elements */
+
-
/***********************************/
+
-
#contentSub, #search-controls, #catlinks, #p-logo, .firstHeading {
+
-
display:none;
+
-
padding:0px;
+
-
margin:0px;
+
-
}
+
-
#bodyContent {border:none;}
+
-
#content {width: 100%; padding:0px; border-left: 0px; border-right: 0px;}
+
-
#globalWrapper {width: 100%; font-size: 100%; position: static;}
+
-
#top-section {width: 100%; height:10px; border:none;}
+
-
#p-logo {display:none;}
+
-
#search-controls {display:none;}
+
-
#menubar a {color:#000000; background-color:transparent;}
+
-
#menubar a:hover{text-decoration:none; color:#0090FF; background-color:transparent;}
+
-
.left-menu a:hover{background-color:transparent; margin:5px 0px 0px 0px; padding:0; background: transparent;}
+
-
.left-menu li a:hover{background-color:transparent; margin:0; padding:0; background: transparent;}
+
-
.right-menu ul li a {background-color:transparent; background: transparent;}
+
-
.printfooter {display:none; background-color:transparent;}
+
-
a:hover {text-decoration: none;}
+
-
#footer-box {border:none; background-color:transparent;}
+
-
#catlinks {display:none; background-color:transparent;}
+
-
.firstHeading {display:none; background-color:transparent;}
+
-
#content {width: 100%; border:none; background-color:transparent;}
+
-
h1, h2, h3, h4, h5, h6 {
+
-
font-size: 100%;
+
-
padding-top: 0;
+
-
padding-bottom: 0;
+
-
border-bottom: 0px;
+
-
}
+
-
 
+
-
html {margin: 0;}
+
-
ul {
+
-
list-style-type: none;
+
-
list-style-image: none;
+
-
}
+
-
 
+
-
</style>
+
-
 
+
-
<link rel="stylesheet" href="http://cs.wellesley.edu/~hcilab/igem2013/whci_app.css">
+
-
<link href='http://fonts.googleapis.com/css?family=Roboto' rel='stylesheet' type='text/css'>
+
-
<link href='http://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet' type='text/css'>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_jquery.js"></script>
+
-
 
+
<body>
<body>
<nav class="top-bar">
<nav class="top-bar">
Line 57: Line 12:
<!-- Title Area -->
<!-- Title Area -->
<li class="name">
<li class="name">
-
<h1><a href="#">WHCI</a></h1>
+
<h1><a href="https://2013.igem.org/Team:Wellesley_Desyne">WHCI</a></h1>
</li>
</li>
<!-- Remove the class "menu-icon" to get rid of menu icon. Take out "Menu" to just have icon alone -->
<!-- Remove the class "menu-icon" to get rid of menu icon. Take out "Menu" to just have icon alone -->
Line 80: Line 35:
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/Project_Overview">Overview</a></li>
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/Project_Overview">Overview</a></li>
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/Eugenie">Eugenie</a></li>
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/Eugenie">Eugenie</a></li>
-
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/zMol_zTree">zTree & zMol</a></li>
+
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/zTree">zTree</a></li>
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/BAC">Bac to the Future</a></li>
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/BAC">Bac to the Future</a></li>
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/Downloads_Tutorials">Downloads & Tutorials</a></li>
<li><a href="https://2013.igem.org/Team:Wellesley_Desyne/Downloads_Tutorials">Downloads & Tutorials</a></li>
Line 110: Line 65:
<div class="row">
<div class="row">
<div class="large-12 columns">
<div class="large-12 columns">
-
<h2><img src="https://static.igem.org/mediawiki/2013/0/03/Wellesley_logo.png">Wellesley HCI iGEM 2013</h2>
+
<a href="https://2013.igem.org/Team:Wellesley_Desyne" class="header-link"><h2><img src="https://static.igem.org/mediawiki/2013/0/03/Wellesley_logo.png">Wellesley HCI iGEM 2013</h2></a>
</div>
</div>
</div>
</div>
</div>
</div>
</header>
</header>
-
 
-
<!--End NavBar--> 
 
<div class="row">
<div class="row">
<div class="large-12 columns">
<div class="large-12 columns">
Line 125: Line 78:
<h3>User Research</h3>
<h3>User Research</h3>
-
<br>
+
 
-
<h4>OVERVIEW</h4>
+
<h4>Overview</h4>
-
<p>This summer, the Wellesley College iGem team worked with many potential users of our projects to create tools that improved synthetic biology education or improved efficiency and collaboration in the context of synthetic biology research. We spoke to many potential users, from researchers heading labs in synthetic biology research to users in industry and college students studying biological sciences. We conducted user studies of our programs with volunteer subjects from the <a href="https://2013.igem.org/Team:MIT">MIT</a> and <a href="https://2013.igem.org/Team:BostonU">BU</a> iGEM teams as well as students from Wellesley College who had a range of knowledge and exposure to synthetic biology. Receiving feedback from both target and non-target users during the design process is a vital part of the project design process, especially since we are focused on a user-centered design (UCD) process. We valued all input from the people we collaborated or interacted with during user testing.  
+
<p>This summer, the Wellesley College iGEM team worked extensively with users to create a suite of software tools that improve synthetic biology education, as well as efficiency and collaboration in the context of synthetic biology research. We spoke to many potential users, from researchers heading labs in synthetic biology research, to users in the industry, to college students studying biological sciences. We conducted user studies of our programs with volunteer subjects from the <a href="https://2013.igem.org/Team:MIT">MIT</a> and <a href="https://2013.igem.org/Team:BostonU">BU</a> iGEM teams as well as students from Wellesley College who had a range of knowledge and exposure to synthetic biology. Receiving feedback from future scientists is a vital part of the user-centered design (<a href="https://2013.igem.org/Team:Wellesley_Desyne/Methodology">UCD</a>) process. We valued all input from the people we collaborated and interacted with during user testing.
</p>
</p>
-
<br><br>
 
-
<h4>BASIC WET-LAB TRAINING WITH NATALIE KULDELL AT MIT</h4>
+
<h4>Basic Wet-Lab Training via <a href="http://www.biobuilder.org/">BioBuilder</a> at MIT</h4>
-
<img src = "https://static.igem.org/mediawiki/2013/7/7e/BioBuilder_wetlab.jpg" alt = "MIT BioBuilder Lab" width = "200px" style = "float: right">
+
 
-
<p>At the beginning of the summer, the Wellesley Desyne team received an introduction to synthetic biology and wet-lab training by Professor Natalie Kuldell at MIT. After reviewing the core concepts of synthetic biology, we also discussed in detail the safety concerns of working in this multi-disciplinary field. During the wet-lab training, we were able to participate first hand on well-known and highly regarded experiments such as <a href="http://www.echromi.com/">E.chromi</a>. Through this experience, our team realized that several factors could strongly affect the success or failure of a synthetic biology experiment: labeling equipment properly, meticulously following clearly written instructions, and communicating with other team members. In addition, we discovered that there are many technical difficulties of working in a laboratory environment, especially for those who are nonscientists. Most importantly, there are many safety concerns that are not understood or well known to the public because of synthetic biology’s recent emergence as a leading field. Thus, we realized the importance of educating the public, especially the next generation of synthetic biologists, on the safety concerns of working in a wet-lab environment, and put those considerations into many of our projects.</p>
+
<div class="panel" style = "float:left; width:275px; margin:10px;">
-
<br><br>
+
<img src="https://static.igem.org/mediawiki/2013/7/7e/BioBuilder_wetlab.jpg" >
 +
<p class="caption">Working in the wet lab</p></div>
 +
 
 +
<p>At the beginning of the summer, the Wellesley iGEM team received an introduction to synthetic biology and basic wet-lab training by Professor Natalie Kuldell at MIT. After reviewing the core concepts of synthetic biology, we discussed in detail the safety concerns of working in a wet-lab environment. During the wet-lab training, we were also able to conduct well-known and highly regarded experiments such as <a href="http://www.echromi.com/">E.chromi</a> and <a href="https://2006.igem.org/wiki/index.php/MIT_2006">Eau d'E coli</a>. Thus, through this experience, our team realized that several factors could strongly affect the success or failure of a synthetic biology experiment: labeling equipment properly, meticulously following clearly written instructions, and communicating with other team members.  
 +
 
 +
<p>In addition, we discovered that there are many technical difficulties when working in a laboratory environment, especially for future scientists. Most importantly, there are many safety concerns that are not understood or well known to the public because of synthetic biology’s recent emergence as a leading field. Thus, we realized the importance of educating the public, especially the next generation of synthetic biologists, on the safety concerns of working in a wet-lab environment. The Wellesley iGEM team considered these observations carefully when designing our three projects.</p>
 +
 
 +
 
 +
<h4>Brainstorming and Collaboration with BU</h4>
 +
<div class="panel" style = "float:right; width:310px; margin:10px;">
 +
<img src= "https://static.igem.org/mediawiki/2013/8/8e/100_1441.JPG" width = "300px">
 +
<p class="caption">BU Brainstorm session </center></p> </div>
-
<h4>BRAINSTORMING AND COLLABORATION WITH BU</h4>
+
<p>We continued our tradition of collaborating with the <a href="https://2013.igem.org/Team:BostonU">BU iGEM team</a>. We had a major brainstorming session with <a href="https://2013.igem.org/Team:BostonU">BU</a> at the beginning of the summer where the teams introduced their projects to each other. We received basic feedback and brainstormed the initial goals for our three projects: <a href="https://2013.igem.org/Team:Wellesley_Desyne/Eugenie">Eugenie</a>, <a href="https://2013.igem.org/Team:Wellesley_Desyne/zMol_zTree">zTree</a>, and <a href="https://2013.igem.org/Team:Wellesley_Desyne/BAC">Bac To The Future</a>. Eugenie in particular benefited immensely from the initial brainstorming because we needed to learn more about the programming language, <a href="http://www.eugenecad.org/">Eugene</a>, that was developed to aid synthetic biologists in designing novel genetic circuits. Once we spent time developing several solid ideas for each of our three projects, we invited the <a href="https://2013.igem.org/Team:BostonU">BU iGEM</a> team to Wellesley to present our ideas to them and to receive feedback on which versions of the projects to pursue further. Throughout the summer, we kept in contact with the <a href="https://2013.igem.org/Team:BostonU">BU iGEM</a> team for information and feedback during project development. As part of our <a href="https://2013.igem.org/Team:Wellesley_Desyne/Methodology">UCD</a> process, we tested our software with members of the <a href="https://2013.igem.org/Team:BostonU">BU iGEM</a> team, and their feedback and responses helped to shape further development of our projects.  
-
<img src = "https://static.igem.org/mediawiki/2013/8/8e/100_1441.JPG" alt = "BU Brainstorm session" width = "400px" style = "float: left, margin-right: 5px">
+
-
<p>We continued our tradition of collaborating with the <a href="https://2013.igem.org/Team:BostonU">BU iGem team</a>. We had a major brainstorming session with BU at the beginning of the summer where the teams introduced their projects to each other. We received basic feedback and brainstormed for initial goals for our three projects: <a href="https://2013.igem.org/Team:Wellesley_Desyne/Eugenie">Eugenie</a>, <a href="https://2013.igem.org/Team:Wellesley_Desyne/zMol_zTree">zMol_zTree</a>, and <a href="https://2013.igem.org/Team:Wellesley_Desyne/BAC">Bac To The Future</a>. Eugenie in particular benefitted immensely from the initial brainstorming because we needed to learn more about the programming language, <a href="http://www.eugenecad.org/">Eugene</a>, that was developed to aid synthetic biologists in designing novel genetic circuits. Once we spent time developing several solid ideas for each of our three projects, we invited the BU iGem team to Wellesley to present our ideas to them and get feedback so we could decide which versions of the projects to pursue further. Throughout the summer, we kept up communication with the BU iGem team for information and feedback during project development. As part of our UCD process, we tested developed software with members of the team, and their feedback and responses helped to shape further development of our projects in the direction that we wanted to take them.  
+
</p>
</p>
-
<br><br>
+
<div class="panel" style = "float:left; width:310px; margin:10px;">
 +
<img src= "https://static.igem.org/mediawiki/2013/f/ff/BUUsers.jpg" width = "300px">
 +
<p class="caption">BU testing Eugenie </center></p> </div>
-
<h4>SITTING IN ON BU LAB MEETINGS</h4>
+
<h4>Observing BU Lab Meetings</h4>
-
<p>A few times this summer, members of the <a href="https://2013.igem.org/Team:Wellesley_Desyne/Eugenie">Eugenie</a> project sat in on BU iGem lab meetings to observe how members of their research group collaborated while developing novel genetic circuits for their summer research projects. The meetings were informative and helpful in guiding us in the development of software tools that would assist in the novel genetic circuit design process. From observing these meetings, we considered how our programs could help foster collaboration and wet lab research work. Some of the things we thought about included how work could be shared and edited between students and PIs, and how our programs would fit in with other tools that were currently used.     
+
<p>A few times this summer, members of the <a href="https://2013.igem.org/Team:Wellesley_Desyne/Eugenie">Eugenie</a> project sat in on <a href="https://2013.igem.org/Team:BostonU">BU iGEM</a> lab meetings to observe how members of their research group collaborated while developing novel genetic circuits for their summer research projects. The meetings were informative and crucial in guiding us in the development of software tools that would assist in the novel genetic circuit design process. From observing these meetings, we considered how our programs could help foster collaboration in wet lab research. Some of topics we considered included: how work could be shared and edited between students and PIs, and how our programs would fit in with other the tools that are already being used.     
</p>
</p>
-
<br><br>
 
-
<h4>GETTING SOME INITIAL FEEDBACK FROM WELLESLEY COLLEGE STUDENTS</h4>
+
 
-
<p>As part of our desire to get feedback about the design and useability of our programs from students that had a range of exposure to synthetic biology, we tested our programs initially on our fellow Wellesley College students. Observing our users as they used our programs to accomplish assigned tasks helped us refine our programs so that the software tools we had created were not themselves hurdles for users working in synthetic biology research. We also collected both verbal and written feedback, as well as videotaped the user studies for later analysis.
+
<h4>Eliciting Feedback from Users</h4>
 +
 
 +
<div class="panel" style = "float:right; width:310px; margin:10px">
 +
<img src= "https://static.igem.org/mediawiki/2013/8/8f/Eugenie_chart.png" width="300px">
 +
<p class="caption">Eugenie user testing results </p></div>
 +
 
 +
<p>As part of our desire to receive feedback concerning the design and usability of our programs from students that have a wide range of exposure to synthetic biology, we tested our programs with BU, MIT and Wellesley students. By observing our users as they used our programs to accomplish the assigned tasks, we were able to refine our applications so that the software tools we had created were not hurdles themselves for the users working in synthetic biology research. We also collected both verbal and written feedback, as well as videotaped user studies for further analysis.
</p>
</p>
-
<br><br>
 
-
<h4>NEXT STEPS TO TAKE IN THE UCD PROCESS</h4>
 
-
<p>While we made progress in great leaps and bounds this summer, we are aware that there is still work to be done to continue to develop our projects past the scope of iGem. We hope to continue receiving user feedback from other members of the Wellesley College community, BU iGem, and MIT iGem. The <a href="https://2013.igem.org/Team:Wellesley_Desyne/Eugenie">Eugenie</a> team will need to do more user testing to make sure that our program is robust enough that synthetic biologists can use it to design any genetic circuit they can think of.
 
-
<a href="https://2013.igem.org/Team:Wellesley_Desyne/zMol_zTree">zMol_zTree</a>'s goals are?
+
<h4>Future Work</h4>
-
<a href="https://2013.igem.org/Team:Wellesley_Desyne/BAC">Bac To The Future</a>'s goals are?
+
<p>While our progress made great leaps and bounds this summer, there is still much work to be done to continue developing our projects beyond the scope of iGEM. We hope to continue receiving user feedback from other members of the synthetic biology community, specifically the <a href="https://2013.igem.org/Team:BostonU">BU</a> and <a href="https://2013.igem.org/Team:MIT">MIT</a> iGEM teams. The <a href="https://2013.igem.org/Team:Wellesley_Desyne/Eugenie">Eugenie</a> team plans to conduct more user testing to ensure that the program is robust enough that any genetic circuit can be designed.
 +
 
 +
<a href="https://2013.igem.org/Team:Wellesley_Desyne/zMol_zTree">zTree</a>'s goals are to animate carousels on and off the screen, rather than simply appearing and disappearing. Additionally, we would like to integrate a search feature that will allow users to search for specific parts at any point in their tree traversal. Finally,
 +
<a href="https://2013.igem.org/Team:Wellesley_Desyne/BAC">Bac To The Future</a>'s goals are also to perform more user testing, to create a gesture-based, interactive tool, and to iterate and improve the usability of the application as well as to maximize its potential for educational purposes.
</p>
</p>
 +
<div class="row">
 +
<hr>
 +
<img src="https://static.igem.org/mediawiki/2013/6/62/Whci_sponsor_logos.png">
 +
</div>
 +
</div>
</div>
</div>
<!--End content-->
<!--End content-->
-
<html>
+
<script src="http://eastmaninteractive.com/igem/whci_zepto.js"></script>
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.js"></script>
+
<script src="http://eastmaninteractive.com/igem/whci_foundation.js"></script>
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.abide.js"></script>
+
<script src="http://eastmaninteractive.com/igem/whci_foundation.dropdown.js"></script>
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.alerts.js"></script>
+
<script src="http://eastmaninteractive.com/igem/whci_foundation.topbar.js"></script>
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.clearing.js"></script>
+
<script>
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.cookie.js"></script>
+
$(document).foundation();
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.dropdown.js"></script>
+
</script>
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.forms.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.interchange.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.joyride.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.magellan.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.orbit.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.placeholder.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.reveal.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.section.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.tooltips.js"></script>
+
-
<script src="http://cs.wellesley.edu/~hcilab/igem2013/whci_foundation.topbar.js"></script>
+
-
  <script>
+
-
    $(document).foundation();
+
-
  </script>
+
</html>
</html>

Latest revision as of 03:31, 28 September 2013

Wellesley HCI iGEM Team: Welcome

User Research

Overview

This summer, the Wellesley College iGEM team worked extensively with users to create a suite of software tools that improve synthetic biology education, as well as efficiency and collaboration in the context of synthetic biology research. We spoke to many potential users, from researchers heading labs in synthetic biology research, to users in the industry, to college students studying biological sciences. We conducted user studies of our programs with volunteer subjects from the MIT and BU iGEM teams as well as students from Wellesley College who had a range of knowledge and exposure to synthetic biology. Receiving feedback from future scientists is a vital part of the user-centered design (UCD) process. We valued all input from the people we collaborated and interacted with during user testing.

Basic Wet-Lab Training via BioBuilder at MIT

Working in the wet lab

At the beginning of the summer, the Wellesley iGEM team received an introduction to synthetic biology and basic wet-lab training by Professor Natalie Kuldell at MIT. After reviewing the core concepts of synthetic biology, we discussed in detail the safety concerns of working in a wet-lab environment. During the wet-lab training, we were also able to conduct well-known and highly regarded experiments such as E.chromi and Eau d'E coli. Thus, through this experience, our team realized that several factors could strongly affect the success or failure of a synthetic biology experiment: labeling equipment properly, meticulously following clearly written instructions, and communicating with other team members.

In addition, we discovered that there are many technical difficulties when working in a laboratory environment, especially for future scientists. Most importantly, there are many safety concerns that are not understood or well known to the public because of synthetic biology’s recent emergence as a leading field. Thus, we realized the importance of educating the public, especially the next generation of synthetic biologists, on the safety concerns of working in a wet-lab environment. The Wellesley iGEM team considered these observations carefully when designing our three projects.

Brainstorming and Collaboration with BU

BU Brainstorm session

We continued our tradition of collaborating with the BU iGEM team. We had a major brainstorming session with BU at the beginning of the summer where the teams introduced their projects to each other. We received basic feedback and brainstormed the initial goals for our three projects: Eugenie, zTree, and Bac To The Future. Eugenie in particular benefited immensely from the initial brainstorming because we needed to learn more about the programming language, Eugene, that was developed to aid synthetic biologists in designing novel genetic circuits. Once we spent time developing several solid ideas for each of our three projects, we invited the BU iGEM team to Wellesley to present our ideas to them and to receive feedback on which versions of the projects to pursue further. Throughout the summer, we kept in contact with the BU iGEM team for information and feedback during project development. As part of our UCD process, we tested our software with members of the BU iGEM team, and their feedback and responses helped to shape further development of our projects.

BU testing Eugenie

Observing BU Lab Meetings

A few times this summer, members of the Eugenie project sat in on BU iGEM lab meetings to observe how members of their research group collaborated while developing novel genetic circuits for their summer research projects. The meetings were informative and crucial in guiding us in the development of software tools that would assist in the novel genetic circuit design process. From observing these meetings, we considered how our programs could help foster collaboration in wet lab research. Some of topics we considered included: how work could be shared and edited between students and PIs, and how our programs would fit in with other the tools that are already being used.

Eliciting Feedback from Users

Eugenie user testing results

As part of our desire to receive feedback concerning the design and usability of our programs from students that have a wide range of exposure to synthetic biology, we tested our programs with BU, MIT and Wellesley students. By observing our users as they used our programs to accomplish the assigned tasks, we were able to refine our applications so that the software tools we had created were not hurdles themselves for the users working in synthetic biology research. We also collected both verbal and written feedback, as well as videotaped user studies for further analysis.

Future Work

While our progress made great leaps and bounds this summer, there is still much work to be done to continue developing our projects beyond the scope of iGEM. We hope to continue receiving user feedback from other members of the synthetic biology community, specifically the BU and MIT iGEM teams. The Eugenie team plans to conduct more user testing to ensure that the program is robust enough that any genetic circuit can be designed. zTree's goals are to animate carousels on and off the screen, rather than simply appearing and disappearing. Additionally, we would like to integrate a search feature that will allow users to search for specific parts at any point in their tree traversal. Finally, Bac To The Future's goals are also to perform more user testing, to create a gesture-based, interactive tool, and to iterate and improve the usability of the application as well as to maximize its potential for educational purposes.