CH391L/S13/FinalProjectRubric

From OpenWetWare

< CH391L/S13(Difference between revisions)
Jump to: navigation, search
m (Presentation)
Current revision (09:47, 24 April 2013) (view source)
(Written Proposal)
 
Line 40: Line 40:
The entire document should aim for 10-15 pages double spaced with 1" margins. Longer or shorter is fine if all of the objectives are met.
The entire document should aim for 10-15 pages double spaced with 1" margins. Longer or shorter is fine if all of the objectives are met.
-
Your group will be given an opportunity to respond to comments and revise the written part of the project after the final presentation.
+
== Grading ==
'''Group effort (200 pts)'''
'''Group effort (200 pts)'''

Current revision

Contents

Presentation

Your group should prepare a slide presentation covering the same material as the written report. Each person in a group is expected to present for roughly 5 minutes (max 20 min per group) with 10 minutes for questions afterward. Your peers will give you written comments at the end of class that point out areas in your proposal to improve for the written report.

Written Proposal

Please divide your final project into these areas:

  • Abstract (1 paragraph, 250 words max)
    • Overall summary of your project.
  • Motivation (1-3 paragraphs)
    • Describe the big picture technological, scientific, or societal impact of your project.
  • Background (4-6 paragraphs)
    • State of the art: What has been done to tackle this problem before?
    • Where did the biological parts you are using come from?
    • How have these parts been used before in synthetic biology?
  • Experimental Methods
    • What are you making? Describe this on two levels (see below).
      1. Circuit/metabolic pathway diagram explaining the overall logic and function
      2. Annotated DNA sequences of final constructs showing parts and genes
    • What are your sources for parts, genes, strains, and plasmids? Be specific. (Plasmid X from AddGene, part Y from the iGEM registry, etc.)
    • How would you construct your DNA sequences in lab?
      • Imagine a flowchart of PCR reactions, cloning reactions, etc., you would use.
      • Be specific, but there is no need to actually design primer sequences.
  • Computational Methods
    • If applicable, describe how you could simulate your system or use computational approaches to better understand your system and improve the chances of your project's success.
  • Expected Results
    • How will you test your constructs?
    • What are the expected results? What is a measure of success?
  • Troubleshooting (2-3 paragraphs)
    • What would you do if your design did not work?
    • How can you troubleshoot failed experiments or constructs that do not fully function?
    • Are there alternative approaches to the same final goal?
  • Author contributions (1 paragraph)
    • Describe what each project member contributed to the final written document.
    • What figures they created, what sections they wrote, what ideas they came up with.
    • You should all contribute to editing the final document.

The entire document should aim for 10-15 pages double spaced with 1" margins. Longer or shorter is fine if all of the objectives are met.

Grading

Group effort (200 pts) 80 pts for the presentation and 120 pts for the written report.

Individual effort (100 pts) 40 pts for the presentation and 60 pts for the written report.

Total (300 pts)

Describing your project's DNA sequences

For your project, you are required to create two representations of your synthetic biology constructs.

First, you need a high-level circuit/metabolic pathway diagram. I recommend using TinkerCell to create this image. Label standardized parts from the iGEM registry with their numbers. Indicate the sources of non-registry DNA sequences.

Example of a circuit drawn using TinkerCell
Example of a circuit drawn using TinkerCell

Second, you need a file showing the full DNA sequence of the construct. For creating the sequence file, I recommend using one of these software programs:

Personal tools