Team:UCSD Software/SoftwareAchievements

From 2014.igem.org

(Difference between revisions)
Line 437: Line 437:
           <h1>iGEM Gold Medal requirements</h1>
           <h1>iGEM Gold Medal requirements</h1>
<ul>
<ul>
-
<li>We did some modeling and complexity analysis work of our project. You can find details <a href = "">here.</a></li>
+
<li>We did some modeling and complexity analysis work of our project. You can find details <a href = "">here</a>.</li>
<li>We re-used and improved an existing database, & developed on it (Linh's paper). We also made use of SBOL visual (decribed in further detail under the "Web Application" section of the <a href = "">Project</a> page).</li>
<li>We re-used and improved an existing database, & developed on it (Linh's paper). We also made use of SBOL visual (decribed in further detail under the "Web Application" section of the <a href = "">Project</a> page).</li>
<li>We created an API (Joaquin & Kwat's API/Python module pydoc/Github Documentation code) that other developers can use to build on our project or use it in novel ways for their own projects.</li>
<li>We created an API (Joaquin & Kwat's API/Python module pydoc/Github Documentation code) that other developers can use to build on our project or use it in novel ways for their own projects.</li>
Line 460: Line 460:
           <h1>iGEM Silver Medal requirements</h1>
           <h1>iGEM Silver Medal requirements</h1>
           <ul>
           <ul>
-
           <li>Read about our project and its relevance to Synthetic Biology <a href = "">here.</a></li>
+
           <li>We've demonstrated the relevance of our project to Synthetic Biology <a href = "">here</a>.</li>
-
           <li>We have also included comprehensive code documentation for outside developers.</li>
+
           <li>We have a comprehensive and well-designed <a href = "">Tutorial</a> for using our app.</li>
-
           <li>We also used git versioning from the start of our project so that the commit history will be available on github.             </li>
+
           <li>We created an API (Joaquin & Kwat's API/Python module pydoc/Github Documentation code) that other developers can use to build on our project or use it in novel ways for their own projects.</li>
-
           <li>Use of SBOL and other standards. (Use and/or improvement of existing synthetic biology tools or frameworks; cite other iGEM teams).</li>
+
           <li>We used QUnit, a JavaScript unit testing framework, for some of our work during the summer.</li>
           </ul>
           </ul>
         </div>     
         </div>     

Revision as of 01:53, 16 October 2014


iGEM Gold Medal requirements

  • We did some modeling and complexity analysis work of our project. You can find details here.
  • We re-used and improved an existing database, & developed on it (Linh's paper). We also made use of SBOL visual (decribed in further detail under the "Web Application" section of the Project page).
  • We created an API (Joaquin & Kwat's API/Python module pydoc/Github Documentation code) that other developers can use to build on our project or use it in novel ways for their own projects.
  • As mentioned earlier, we made use of SBOLv standard.

iGEM Silver Medal requirements

  • We've demonstrated the relevance of our project to Synthetic Biology here.
  • We have a comprehensive and well-designed Tutorial for using our app.
  • We created an API (Joaquin & Kwat's API/Python module pydoc/Github Documentation code) that other developers can use to build on our project or use it in novel ways for their own projects.
  • We used QUnit, a JavaScript unit testing framework, for some of our work during the summer.

iGEM Bronze Medal requirements

  • This (provide link or info directly) is how our project is relevant to Synthetic Biology.
  • We have also devised an experimental test for our program/algorithm/workflow (demonstrate/display here).
  • In the early stages of our project, we had planned on and worked with testing frameworks such as QUnit, which is a JavaScript Unit Testing Framework.
  • Although we ended up not using it eventually, it was something that a lot of our team members had worked on and/or considered using.