IGEM:IMPERIAL/Methodology: Difference between revisions
From OpenWetWare
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 5: | Line 5: | ||
{| style="width:90%; height:80px" border="0" align="right" | {| style="width:90%; height:80px" border="0" align="right" | ||
| | | | ||
*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 | *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. | ||
* | *The engineering development cycle was based on 5 steps : '''Specifications''', '''Design''', '''Modelling''', '''Implementation''' and '''Testing/Validation''' | ||
|[[Image:iGEM_IMPERIAL_Methodology.png|right|350px]] | |[[Image:iGEM_IMPERIAL_Methodology.png|right|350px]] |
Revision as of 07:36, 11 September 2006
From a brilliant idea to a glowing bacteria
|
|
|