The CFTR frameshift mutation 3905insT and its effect at transcript and protein level

Cystic fibrosis (CF) is one of the most common genetic diseases in the Caucasian population and is characterized by chronic obstructive pulmonary disease, exocrine pancreatic insufficiency, and elevation of sodium and chloride concentrations in the sweat and infertility in men. The disease is caused by mutations in the CF transmembrane conductance regulator (CFTR) gene, which encodes a protein that functions as chloride channel at the apical membrane of different epithelia. Owing to the high genotypic and phenotypic disease heterogeneity, effects and consequences of the majority of the CFTR mutations have not yet been studied. Recently, the frameshift mutation 3905insT was identified as the second most frequent mutation in the Swiss population and found to be associated with a severe phenotype. The frameshift mutation produces a premature termination codon (PTC) in exon 20, and transcripts bearing this PTC are potential targets for degradation through nonsense-mediated mRNA decay (NMD) and/or for exon skipping through nonsense-associated alternative splicing (NAS). Using RT-PCR analysis in lymphocytes and different tissue types from patients carrying the mutation, we showed that the PTC introduced by the mutation does neither elicit a degradation of the mRNA through NMD nor an alternative splicing through NAS. Moreover, immunocytochemical analysis in nasal epithelial cells revealed a significantly reduced amount of CFTR at the apical membrane providing a possible molecular explanation for the more severe phenotype observed in F508del/3905insT compound heterozygotes compared with F508del homozygotes. However, further experiments are needed to elucidate the fate of the 3905insT CFTR in the cell after its biosynthesis.

The Small Project Observatory: Visualizing Software Ecosystems

Software evolution research has focused mostly on analyzing the evolution of single software systems. However, it is rarely the case that a project exists as standalone, independent of others. Rather, projects exist in parallel within larger contexts in companies, research groups or even the open-source communities. We call these contexts software ecosystems, and on this paper we present The Small Project Observatory, a prototype tool which aims to support the analysis of project ecosystems through interactive visualization and exploration. We present a case-study of exploring an ecosystem using our tool, we describe about the architecture of the tool, and we distill the lessons learned during the tool-building experience.

Replaying past changes in multi-developer projects

What was I working on before the weekend? and What were the members of my team working on during the last week? are common questions that are frequently asked by a developer. They can be answered if one keeps track of who changes what in the source code. In this work, we present Replay, a tool that allows one to replay past changes as they happened at a fine-grained level, where a developer can watch what she has done or understand what her colleagues have done in past development sessions. With this tool, developers are able to not only understand what sequence of changes brought the system to a certain state (e.g., the introduction of a defect), but also deduce reasons for why her colleagues performed those changes. One of the applications of such a tool is also discovering the changes that broke the code of a developer.