Team:HFUT CHINA/Medal.html

From 2014.igem.org

(Difference between revisions)

Latest revision as of 03:50, 18 October 2014

HFUT_CHINA | meetup

Medal

Bronze Medal:
	Register the team, have a great summer, and have fun attending the Giant Jamboree.
	Create and share a description of the team's project via the iGEM wiki.
	Present a Poster and Talk at the Giant Jamboree.
	Develop and make available via The Registry of Software Tools, an open source software tool that supports Synthetic Biology based on Standard Parts. read more
Silver Medal:
	Demonstrate the relevance of your development for Synthetic Biology based on standard Parts. read more
	Provide a comprehensive and well-designed User Guide. (Be creative! An instructional video may work as well.) read more
	Provide detailed API documentation, preferably, automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc). The detailed API documents could be downloaded from here.
	Demonstrate that you followed best practises in software development so that other developers can modify, use and reuse your code. Provide more than one realistic test case. Examples of best practices are automated unit testing and documentation of test coverage, bug tracking facilities, documentation of releases and changes between releases. read more
Gold Medal:
	Provide a convincing validation, testing the performance of the development -- experimentally (can be outsourced) or by other teams and users. Note, even if the algorithm or tool turns out not to work that well, the Gold requirement is fulfilled if the test is good and the analysis convincing. Validation may include: preferably experiments, informatics analysis (complexity, run time) of an algorithm, or user studies. read more
	Make your software interact / interface with the Registry. read more
	Re-use and further develop previous iGEM software projects (or parts thereof) or use and/or improvement of existing synthetic biology tools or frameworks.
	Develop a well documented library or API for other developers (rather than only a stand-alone app for end users.) read more The detailed API documents could be downloaded from here.
	Support and use the SBOL and / or SBOLv standard. > Since we need to visualize the device chains, we use SBOLv symbols to represent different types of biobricks.
	iGEM projects involve important questions beyond the bench, for example relating to (but not limited to) ethics, sustainability, social justice, safety, security, or intellectual property rights. Describe an approach that your team used to address at least one of these questions. Evaluate your approach, including whether it allowed you to answer your question(s), how it influenced the team's scientific project, and how it might be adapted for others to use (within and beyond iGEM). We encourage thoughtful and creative approaches, and those that draw on past Policy & Practice (formerly Human Practices) activities. read more

@@ Line 49: / Line 49: @@
                      <ul>
                          <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Devblogs.html">Devblogs</a></li>
-                         <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Database&Algorithm.html">Database & Algorithm</a></li>
+                         <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Database&Algorithm.html">Algorithm</a></li>
-                         <li><a href="https://2014.igem.org/Team:HFUT_CHINA/Tutorial.html">Tutorial</a></li>
+                         <li><a href="https://2014.igem.org/Team:HFUT_CHINA/user_guide.html">Tutorial</a></li>
@@ Line 145: / Line 145: @@
              <td width="916"><p align="justify">Develop and make available via The Registry of Software    Tools, an open source software tool that supports Synthetic Biology based on    Standard Parts.</p>
 <br>
-  <p><a href="https://github.com/igemsoftware/HFUT_CHINA_2014">read more</a></p>
+  <p><a href="https://2014.igem.org/Team:HFUT_CHINA/readme">read more</a></p>
                <p align="justify">&nbsp;</p></td>
@@ Line 157: / Line 157: @@
              <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td>
              <td width="916"><p align="justify">Demonstrate the relevance of your development for    Synthetic Biology based on standard Parts. </p>
+ <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Judging_Form.html#a">read more</a></p>
                <p align="justify">&nbsp; </p>              </td>
            </tr>
@@ Line 162: / Line 164: @@
              <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td>
              <td width="916"><p align="justify">Provide a comprehensive and well-designed User Guide.    (Be creative! An instructional video may work as well.)</p>
+<p><a href="https://2014.igem.org/Team:HFUT_CHINA/user_guide.html">read more</a></p>
                <p align="justify">&nbsp;</p></td>
            </tr>
            <tr>
              <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td>
-             <td width="916"><p align="justify">Provide detailed API documentation, preferably,    automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc).</p>
+             <td width="916"><p align="justify">Provide detailed API documentation, preferably,    automatically built from source code documentation (use tools like doxygen, yard, rdoc, naturaldocs, etc).</p><a name="1"></a>
-<a href="https://static.igem.org/mediawiki/2014/1/14/Hfut-APIhtml.zip">download api doc</a>
+The detailed API documents could be downloaded from <a href="https://static.igem.org/mediawiki/2014/6/6f/HFUTFFUTAPI.zip
+">here.</a>
                <p align="justify">&nbsp;</p></td>
            </tr>
@@ Line 174: / Line 178: @@
              <td width="916"><p align="justify">Demonstrate that you followed best practises in    software development so that other developers can modify, use and reuse your    code. Provide more than one realistic test case. Examples of best practices    are automated unit testing and documentation of test coverage, bug tracking    facilities, documentation of releases and changes between releases.</p>
 <br>
-  <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Overview.html">read more</a></p>  </td>
+  <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Unit_Test_Result.html">read more</a></p>  </td>
            </tr>
            <tr>
@@ Line 184: / Line 188: @@
              <td width="184" valign="top"><div align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></div></td>
              <td width="916"><p align="justify">Provide a convincing validation, testing the    performance of the development -- experimentally (can be outsourced) or by    other teams and users. Note, even if the algorithm or tool turns out not to    work that well, the Gold requirement is fulfilled if the test is good and the    analysis convincing. Validation may include: preferably experiments,    informatics analysis (complexity, run time) of an algorithm, or user studies.</p>
+<p><a href="https://2014.igem.org/Team:HFUT_CHINA/Examples.html">read more</a></p>
                <p align="justify">&nbsp;</p></td>
            </tr>
@@ Line 189: / Line 194: @@
              <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td>
              <td width="916"><p align="justify">Make your software interact / interface with the    Registry.</p>
+<p><a href="https://2014.igem.org/Team:HFUT_CHINA/Judging_Form.html#c">read more</a></p>
                <p align="justify">&nbsp;</p></td>
            </tr>
@@ Line 199: / Line 205: @@
              <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td>
              <td width="916"><p align="justify">Develop a well documented library or API for other    developers (rather than only a stand-alone app for end users.)</p>
+<p><a href="https://2014.igem.org/Team:HFUT_CHINA/API.html">read more
+</a>The detailed API documents could be downloaded from<a href="https://static.igem.org/mediawiki/2014/6/6f/HFUTFFUTAPI.zip "> here.
+</a></p>
                <p align="justify">&nbsp;</p></td>
            </tr>
@@ Line 204: / Line 213: @@
              <td width="184" valign="top"><p align="center"><img src="https://static.igem.org/mediawiki/2014/c/c1/Hfut-A.png" width="18" height="18"></p></td>
              <td width="916"><p align="justify">Support and use the SBOL and / or SBOLv standard.</p>
-              <p align="justify">&nbsp;</p></td>
+ <p align="justify">&nbsp;</p>
+ <p align="justify"> > Since we need to visualize the device chains, we use SBOLv symbols to represent different types of biobricks.
+</p>
+ <p align="justify">&nbsp;</p>
+              <p align="justify">&nbsp;</p>
            </tr>
            <tr>
@@ Line 210: / Line 223: @@
              <td width="916"><p align="justify">iGEM projects involve important questions beyond the    bench, for example relating to (but not limited to) ethics, sustainability,    social justice, safety, security, or intellectual property rights. Describe    an approach that your team used to address at least one of these questions.    Evaluate your approach, including whether it allowed you to answer your    question(s), how it influenced the team's scientific project, and how it    might be adapted for others to use (within and beyond iGEM). We encourage    thoughtful and creative approaches, and those that draw on past Policy &amp;    Practice (formerly Human Practices) activities.</p>
 <br>
-  <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Overview.html">read more</a></p>  </td>
+  <p><a href="https://2014.igem.org/Team:HFUT_CHINA/Judging_Form.html#b">read more</a></p>
+  </td>
            </tr>
          </table>