IGEM:IMPERIAL/Methodology: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
<div class="tabs-blue">
<ul>
<li id="current">[[IGEM:IMPERIAL/Methodology|Overview]]</li>
<li>[[IGEM:IMPERIAL/Methodology/Specifications|Specifications]]</li>
<li>[[IGEM:IMPERIAL/Methodology/Design|Design]]</li>
<li>[[IGEM:IMPERIAL/Methodology/Modelling|Modelling]]</li>
<li>[[IGEM:IMPERIAL/Methodology/Implementation|Implementation]]</li>
<li>[[IGEM:IMPERIAL/Methodology/TestingValidation|Testing/Validation]]</li>
</ul>
</div>
<br style="clear:both">
==Imperial College first steps in iGEM==


==From a brilliant idea to a glowing bacteria==


{| style="width:90%; height:80px" border="0" align="right"
{| style="width:90%; height:80px" border="0" align="right"
Line 7: Line 18:
*This section intends to illustrate the framework used by the Imperial College iGEM Team in 2006.  Over the summer 2006, for our first participation to iGEM, we wanted to explore how far we could push the '''traditional engineering approach''' in order to deal with a '''Synthetic Biology project'''.
*This section intends to illustrate the framework used by the Imperial College iGEM Team in 2006.  Over the summer 2006, for our first participation to iGEM, we wanted to explore how far we could push the '''traditional engineering approach''' in order to deal with a '''Synthetic Biology project'''.


*Without constraining the student to a particular system, we wanted them to follow an engineering development cycle. As it is true for traditional engineering project management, it was thought to promote '''collaborative work''', '''traceability''' and '''quality control''' throughout the all project.
*Without constraining the students to a particular system, we wanted them to follow an engineering development cycle. As it is true for traditional engineering project management, it was thought to promote '''collaborative work''', '''traceability''' and '''quality control''' throughout the all project.
*The engineering development cycle was based on 5 steps : '''Specifications''', '''Design''', '''Modelling''', '''Implementation''' and '''Testing/Validation'''
*The engineering development cycle was based on 5 steps : '''Specifications''', '''Design''', '''Modelling''', '''Implementation''' and '''Testing/Validation'''


Line 13: Line 24:
|-
|-
|colspan="2"|
|colspan="2"|
*In the following sections we will discuss the different steps of the methodology, illustrating them with documents produced by the students. We will also point out some tools that we used to accomplish each task. Finally, we will give feedbacks from our experience.
*In the following sections we will discuss the different steps of the methodology, illustrating them with documents produced by the students. We will also point out some tools that we used to accomplish each task. Finally, we will give [[IGEM:IMPERIAL/2006/Instructors_Feedbacks | feedbacks from our first experience]].
**[[IGEM:IMPERIAL/Methodology/Specifications | '''SPECIFICATIONS''']]
**[[IGEM:IMPERIAL/Methodology/Design | '''DESIGN''']]
**[[IGEM:IMPERIAL/Methodology/Modelling | '''MODELLING''']]
**[[IGEM:IMPERIAL/Methodology/Implementation | '''IMPLEMENTATION''']]
**[[IGEM:IMPERIAL/Methodology/TestingValidation | '''TESTING and VALIDATION''']]
|}
|}

Latest revision as of 07:30, 6 October 2006


Imperial College first steps in iGEM

  • This section intends to illustrate the framework used by the Imperial College iGEM Team in 2006. Over the summer 2006, for our first participation to iGEM, we wanted to explore how far we could push the traditional engineering approach in order to deal with a Synthetic Biology project.
  • Without constraining the students to a particular system, we wanted them to follow an engineering development cycle. As it is true for traditional engineering project management, it was thought to promote collaborative work, traceability and quality control throughout the all project.
  • The engineering development cycle was based on 5 steps : Specifications, Design, Modelling, Implementation and Testing/Validation
  • In the following sections we will discuss the different steps of the methodology, illustrating them with documents produced by the students. We will also point out some tools that we used to accomplish each task. Finally, we will give feedbacks from our first experience.