Difference between revisions of "Final Project"

From LMU BioDB 2024
Jump to navigation Jump to search
(Group Deliverables: uploading presentation)
(removing presentation link)
 
Line 11: Line 11:
 
== Group Deliverables ==
 
== Group Deliverables ==
  
* You will give a final group [[Final Project Deliverables#PowerPoint_Presentation | PowerPoint presentation]] in class during the final exam period on '''Thursday, May 2, 11:00 AM'''. [[Media: ~$Yeast Beasts Presentation (1).pptx.zip]]
+
* You will give a final group [[Final Project Deliverables#PowerPoint_Presentation | PowerPoint presentation]] in class during the final exam period on '''Thursday, May 2, 11:00 AM'''.  
 
* Final due date for all other deliverables is no later than '''Friday, May 3, 12:00 noon'''.
 
* Final due date for all other deliverables is no later than '''Friday, May 3, 12:00 noon'''.
 
* The deliverables should be uploaded and organized onto one group wiki page.   
 
* The deliverables should be uploaded and organized onto one group wiki page.   

Latest revision as of 10:08, 2 May 2024

Final Project Links
Overview Deliverables Guilds Project Manager Quality Assurance Data Analysis Coder/Designer
Team Yeast Beasts

Overall Project Goal

  1. To create a Microsoft Access database that contains microarray data and gene regulatory network data from published datasets that will be incorporated into the GRNsight gene expression database.
  2. To analyze the published microarray data and model candidate gene regulatory networks with GRNmap to gain new insights.
  3. To perform quality assurance of current GRNsight databases and the one created in this class.

The class will work as a team to achieve these goals. Each member of the team will have a specific role (in a guild), detailed below. Even though team members have a specific role, you are also expected to work with each other as a whole team, in order to keep each component of the project coordinated and consistent.

Group Deliverables

  • You will give a final group PowerPoint presentation in class during the final exam period on Thursday, May 2, 11:00 AM.
  • Final due date for all other deliverables is no later than Friday, May 3, 12:00 noon.
  • The deliverables should be uploaded and organized onto one group wiki page.
  • Detailed specifications, particularly for the group report and individual assessment and reflection, are given on the Final Project Deliverables page.
  • There are group and individual components to the grade for this project. For the group component, each member of the group receives the same grade. The individual component will be assessed based on individual effort and contributions.
  • The Group Report is worth 30 points.
  • The Group PowerPoint presentation is worth 60 points.
  • All other deliverables listed on the Deliverables page, together, are worth 60 points.

Individual Deliverable

The individual deliverable is an assessment and reflection on the process submitted via email to Dr. Dahlquist by the deadline (10 points):

  • Statement of work
  • Assessment of the work done, including justification for the group and individual components of the grade
  • What was learned

Team Journal Entries

  • Each team will write a combined journal entry for each week with contributions from all members.
  • Week 12 Prepare for journal club presentation, reflections
  • Week 13 Creation of team page, executive summaries of progress, reflections
  • Week 14 Executive summaries of progress, reflections
  • Week 15 Organized deliverables page, prepare for final presentation

The project roles are:

  • Team Name: Yeast Beasts
    • Project Manager: Hailey
    • Quality Assurance: Hailey & Natalija
    • Data Analysis: Charlotte & Katie
    • Coder/Designer: Andrew & Dean

Roles (Guilds)

As the project moves forward, we will use class time for team meetings/work sessions. Each student has been assigned a primary role in the project by the instructors (see above).

Project Manager (PM)

The project manager makes sure that individuals are fulfilling their roles and performing the tasks on time.

Quality Assurance (QA)

The QA team member is the link between the Coder/Designers and the Data Analysts. He or she needs to know the details of the microarray dataset being analyzed so that the database being designed and populated by the Coder/Designer is correct and useful for the Data Analysts. The QA will also perform checks on the GRNsight database.

Data Analysis (DA)

The role of the Data Analyst will be to apply the data analysis pipeline that you learned by analyzing the Dahlquist Lab microarray dataset to complete the analysis of a different published yeast timecourse microarray dataset. The Data Analysts are the end-users of the project, ultimately determining whether the work of the coder/designer and quality assurance members is useful to them.

Coder/Designer (CD)

The Coder/Designer is responsible for creating the Microsoft Access database based on the microarray data from the Data Analysts which will eventually be made available on the GRNsight website. The Coder/Designer is also the resident expert on the technology being used—assorted software, file management, version control, and troubleshooting. He or she coordinates with the QA to make sure that the database is accurate.

Project Milestones

Specific project milestones are found on the individual guild pages.

Final Project Links
Overview Deliverables Guilds Project Manager Quality Assurance Data Analysis Coder/Designer
Team Yeast Beasts