BIO systems project

Bioinformatics Project: Defining a System

 

This course gives you a broad overview of bioinformatics principles, with this project we strive to apply those principles towards a biological question.

 

For your term project I would like you to define a biological "system" - a set of genes that collaborate towards a shared purpose and sketch its architecture. We start from a biological process, represented in the Gene Ontology (GO). From there we can use methods of function-annotation to identify related processes, functions and cellular components and the genes that are associated with them. To define the "system" in which those genes collaborate, and to sketch its architecture requires both "bottom up" procedures of gene discovery, and "top down" reasoning about ancillary functions and roles such as substrate import, biosynthesis of cofactors, signalling, regulation, constructing scaffolds etc. that may not (yet) be represented in the list of genes, and to clearly identify, concepts such as purpose; boundaries (i.e. which genes from the list are actually part of the system, and which ones are associated with the process, but should be considered to be outside of its boundaries, in a supporting role, a shared role, or simply part of distinct but collaborating system.); interfaces and, the system's input and output.

It is your task to manage this from the perspective of a biological expert and try to define inclusion/exclusion criteria as best as you can. While your "list of genes" is going to be interesting, compiling such lists can be automated. Thus the most valuable outcome of your project is how you will address the task of defining the conceptual aspects of the system and attempting to organize this into an architectural sketch.

In practice you should

• choose a biological process you are interested in (I have provided a candidate list);
• collect all contributing genes as best you can, using bioinformatics tools and literature annotations;
• list the conceptual roles in your system;
• associate whatever genes you can with those roles and identify genes you were not able to associate with roles, and roles for which the associated genes are unknown;
• integrate these concepts in a sketch; and
• carefully document your efforts and results: the datasources and literature, what procedures have been applied, how the results been accessed, validated and interpreted...

First stage: process, genes and concepts(11 marks max.)

 

To define a system, we will start from a biological process in the GO biological process ontology. I have excerpted a table of processes to get you started, and explained the procedure in detail. You can find the documentation and the table through the links below.

• Notes on the table creation and recommendations how to choose a process.
• Table of GO terms - use this to choose and "adopt" a biological process to seed your system

Note that you are not constrained to start from a process in that table. If you are determined to work on a different human system because you have particular knowledge about it, you may suggest this to me and perhaps we can add it to the table. But you need to coordinate this with me.

Once you have chosen which system to work on:

• Create a subpage on your student wiki for your project;
• Copy the wikisource from the template page I have provided here and paste it into your project page. Save it;
• Start filling in the details and expanding.

 

Bottom up...

 

• At first, you will complete your picture of the system's components, while at the same time refining your concept of the system's purpose. In general, the purpose of the system is probably not going to be the same as the name of the GO term you started from. In order to find additional genes, you should consider the common bioinformatics strategies for function annotation. In general,there are four main sources of information to consider:

1. GO and GOA (via QuickGo), and the associated GONUTS pages which give you information on related terms and annotated proteins;
2. The UniProt page for your genes, with its wealth of detailed annotations and cross-references;
3. Obviously, (recent) literature that you find via crossreferences and PubMed searches; and
4. the STRING database for functional annotation, to which you can upload a set of genes all at once to discover functionally related genes.

In particular:

• your proteins may have domains that mediate functional interactions with other proteins;
• your proteins' structures may indicate requirements for ligands and/or co-factors that need to be synthesized, activated and incorporated;
• your GO terms may have protein annotations for other species that are not present for humans, so you can use BLAST to find their reciprocal-best-matches in humans;
• domain composition of your proteins may indicate related proteins;
• coexpression analysis at COXPRESSdb and GeneFriends may discover co-regulated genes;
• protein-protein interactions (via UniProt) may point to the participation in functional complexes;
• presence in annotated pathways (via UniProt) may point to collaborations.

 

... and Top Down

 

• Spend some thought on naming your "system" well. Focus on the purpose why the system exists, this will help you organize the components – ultimately, the components and architecture need to support that purpose. All of them. Be mindful: the GO terms are usually not suitable as they are to define the purpose of the system. Consider them a starting point.
• Write down your definition of the "purpose". Remember: we consider the purpose to be the benefit of the system for the fitness of the organism.
• Think about auxiliary roles that are part of your system: how it comes into existence, how it accepts substrates and/or information, how it transforms this input and how its output is generated. Consider that whatever is switched on, needs to be switched off again.
• Think about abstract roles like interfaces, set-points, feedback-control elements, signal integration, transmission, effectors ...

 

Second stage: Sketch the system architecture (11 marks max.)

 

The second stage of the project is for you to define an architecture that integrates the system components and the concepts you have defined. Refer to the "Function" script for an example (the yeast G1/S transition switch) how to go about this task. Draw out this architecture in a sketch and include it on your Student Wiki project page.

 

Final stage: Documentation (4 marks max.)

 

The documentation must fulfill two aspects.

• First, your documentation must make your data and results reproducible. You need to specify the premises you started from and how you came up with them, and you need to specify the procedure through which you arrived at your conclusions. Put yourselves into the mind of a reviewer: are you providing enough information so that your (computational) steps can be reproduced? Are your source IDs specified? Your resources and programs?

• Second, your documentation must explain the rationale behind your procedure and conclusions. This is not so much what you did but why you did this, what was the logic behind a certain process or decision.

• Form is important:

• structure your project clearly, include a brief introduction and definitely include a meaningful conclusion;
• avoid jargon;
• make it easy to copy data for further analysis (no screenshots unless you are illustrating a Web-site or GUI);
• write complete sentences;
• do not plagiarize, but reference judiciously;
• make sure your references are complete and take advantage of the <ref> ... </ref> tags and the {{#pmid:1234567}} template.

Ask(!) if you are not sure about Wiki markup or formatting to achieve a particular layout.

 

Organizational details

 

Evaluation

 

Marking will consider suitability and usefulness of the process for this project, how well you were able to abstract the procedures, and how well you succeeded to integrate the data into a meaningful description. For general Marking rubrics, follow this link.

 

Due dates

 

The project (like all class work) is due by the end of classes, December 6. 2016. If you need an extension you must contact me at least a day before the deadline. Please state briefly the requested duration of the extension. The extension request should not extend past the final exam date.

 

Late submissions

 

The time of submission is recorded with your edits on the Wiki and can be identified in the View history tab of a page: I will consider the last edit before the submission deadline for marking. There will be no "late deductions" applied - the deductions are implicit in the status of the project at the due date.

 

Resources

 

Links

• Documentation of the process table and instructions on how to choose a process to adopt
• Table of GO terms (on the Student Wiki)
• wiki-code for a project template page (on the Student Wiki)
• Marking rubrics

 

 

---