Difference between revisions of "Team:UESTC Software/Medals.html"
| Line 26: | Line 26: | ||
<li><a href="https://2015.igem.org/Team:UESTC_Software/Design.html">Design</a></li> | <li><a href="https://2015.igem.org/Team:UESTC_Software/Design.html">Design</a></li> | ||
<li><a href="https://2015.igem.org/Team:UESTC_Software/Modeling.html">Modeling</a></li> | <li><a href="https://2015.igem.org/Team:UESTC_Software/Modeling.html">Modeling</a></li> | ||
| − | <li><a href="https://2015.igem.org/Team:UESTC_Software/ | + | <li><a href="https://2015.igem.org/Team:UESTC_Software/Validation.html">Validation</a></li> |
| − | <li><a href="https://2015.igem.org/Team:UESTC_Software/ | + | <li><a href="https://2015.igem.org/Team:UESTC_Software/Software.html">Software</a></li> |
</ul> | </ul> | ||
</li> | </li> | ||
| Line 53: | Line 53: | ||
<li><a href="https://2015.igem.org/Team:UESTC_Software/Medals.html">Medals</a></li> | <li><a href="https://2015.igem.org/Team:UESTC_Software/Medals.html">Medals</a></li> | ||
<li><a href="https://2015.igem.org/Team:UESTC_Software/Safety.html">Safety</a></li> | <li><a href="https://2015.igem.org/Team:UESTC_Software/Safety.html">Safety</a></li> | ||
| − | <li><a href="https://2015.igem.org/Team:UESTC_Software/Documentation.html">Documentation</a></li> | + | <li style="line-height:1.8rem;"><a href="https://2015.igem.org/Team:UESTC_Software/Documentation.html">API Documentation</a></li> |
</ul> | </ul> | ||
</li> | </li> | ||
Revision as of 11:26, 15 September 2015
MEDALS
GOLD
- 1. iGEM projects involve important questions beyond the bench, for example relating to (but not limited to) ethics, sustainability, social justice, safety, security, and intellectual property rights. We refer to these activities as Human Practices in iGEM. Demonstrate how your team has identified, investigated and addressed one or more of these issues in the context of your project.
Sustainability: We believe that this is one of the most important issue for software project. So we are starting with the following three aspects to address this key task: - 2. Address a problem that you would like to co-develop with a wetlab team. This should be a collaboration where the wetlab team posts a problem they are having and your team addresses the issue by creating an online software solution.
The iGEM team SCU_China wanted to study how to reuse the strong SD sequence, and they met two problems: how to find out SD sequence in DNA and analyze the strength of the SD sequence that affects translation issues. Then we developed an online software based on browser, which is named SD Finder, to address this issue. More details, please see collaboration page. -
3. Re-use and further develop a previous iGEM software project (or parts thereof) and demonstrate how future teams can continue this trend through good code documentation, use of open source materials and creation of great instructional materials.
In the analysis of metabolic pathway and call of KEGG, we reused the project of two previous team. USTC_Software (https://2014.igem.org/Team:USTC-Software) and Illinois-Tools (https://2009.igem.org/Team:Illinois-Tools). Thanks for their work! -
4. Demonstrate your software at the iGEM Giant Jamboree in the software demo suite. You should show a functional prototype that teams can use in following years. (Contact software AT igem DOT org for information about the software demo suite.)
We have developed a detailed API document. More details, please see documentation page.
SILVER
- 1. Provide a comprehensive, well-designed User Guide for your software and upload it to your wiki. Be creative! (An instructional video may work as well.)
We have already provide a User Guide. More details, please see Guide page. - 2. Develop a well documented library or API for other developers (rather than "only" a stand-alone app for end users.)
All of the core functionality of the software is made into the API, and we have prepared a complete set of documents. - 3.Demonstrate that you followed best practices 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, and documentation of releases and changes between releases.
We used unit testing and document generation tools to make the complete software documents. You can see the documentation of releases and documentation of test coverage in our Github.
BRONZE
- 1. Register the team, have a great summer, and have fun attending the Jamboree in Boston.
We registered our team in Mar, 2015. In this summer all of our team members develop our software together. We had a good time and learned how to take part in a team work. Also we will enjoy ourselves at the Jamboree in Boston. - 2. Complete the Judging Form.
We have completed the Judging Form. - 3. Create and share a Description of the team’s project using the iGEM wiki.
We have described our team’s project by iGEM wiki. - 4. Present a poster and a talk at the IGEM Jamboree.
We have designed a wonderful poster so that we can share with others at the IGEM Jamboree. - 5. Create a page on your team wiki with clear attribution of each aspect of your project. This page must clearly attribute work done by the students and distinguish it from work done by others, including host labs, advisors, instructors, sponsors, professional website designers, artists, and commercial services.
We have described our distribution clearly in wiki. More details, please see distribution page. - 6. Develop and make available, via the IGEM GitHub page, an open source software that supports Synthetic Biology based on Standard Parts or interacts with the Registry.
Our software is open source and can be acquired from Github. Besides, our software supports Synthetic Biology based on Standard Parts and interacts with the Registry. More details, please see design page.