MRI-based breast volumetry-evaluation of three different software solutions

As lipofilling of the female breast is becoming more popular in plastic surgery, the use of MRI to assess breast volume has been employed to control postoperative results. Therefore, we sought to evaluate the accuracy of magnetic resonance imaging (MRI)-based breast volumetry software tools by comparing the measurements of silicone implant augmented breasts with the actual implant volume specified by the manufacturer. MRI-based volume analysis was performed in eight bilaterally augmented patients (46 ± 9 years) with three different software programs (Brainlab© I plan 2.6 neuronavigation software; mass analysis, version 5.3, Medis©; and OsiriX© v.3.0.2. 32-bit). The implant volumes analysed by the BrainLab© software had a mean deviation of 2.2 ± 1.7% (r?=?0.99) relative to the implanted prosthesis. OsiriX© software analysis resulted in a mean deviation of 2.8 ± 3.0% (r?=?0.99) and the Medis© software had a mean deviation of 3.1 ± 3.0% (r?=?0.99). Overall, the volumes of all analysed breast implants correlated very well with the real implant volumes. Processing time was 10 min per breast with each system and 30 s (OsiriX©) to 5 min (BrainLab© and Medis©) per silicone implant. MRI-based volumetry is a powerful tool to calculate both native breast and silicone implant volume in situ. All software solutions performed well and the measurements were close to the actual implant sizes. The use of MRI breast volumetry may be helpful in: (1) planning reconstructive and aesthetic surgery of asymmetric breasts, (2) calculating implant size in patients with missing documentation of a previously implanted device and (3) assessing post-operative results objectively.

Explora: Infrastructure for Scaling Up Software Visualisation to Corpora

Visualisation provides good support for software analysis. It copes with the intangible nature of software by providing concrete representations of it. By reducing the complexity of software, visualisations are especially useful when dealing with large amounts of code. One domain that usually deals with large amounts of source code data is empirical analysis. Although there are many tools for analysis and visualisation, they do not cope well software corpora. In this paper we present Explora, an infrastructure that is specifically targeted at visualising corpora. We report on early results when conducting a sample analysis on Smalltalk and Java corpora.

Embedding Moose Facilities Directly in IDEs

Moose is a powerful reverse engineering platform, but its facilities and means to analyze software are separated from the tools developers typically use to develop and maintain their software systems: development environments such as Eclipse, VisualWorks, or Squeak. In practice, this requires developers to work with two distinct environments, one to actually develop the software, and another one (e.g., Moose) to analyze it. We worked on several different techniques, using both dynamic and static analyzes to provide software analysis capabilities to developers directly in the IDE. The immediate availability of analysis tools in an IDE significantly increases the likelihood that developers integrate software analysis in their daily work, as we discovered by conducting user studies with developers. Finally, we identified several important aspect of integrating software analysis in IDEs that need to be addressed in the future to increase the adoption of these techniques by developers.

NGS Nominated CELA1, HSPG2, and KCNK5 as Candidate Genes for Predisposition to Balkan Endemic Nephropathy

Balkan endemic nephropathy (BEN) is a familial chronic tubulointerstitial disease with insidious onset and slow progression leading to terminal renal failure. The results of molecular biological investigations propose that BEN is a multifactorial disease with genetic predisposition to environmental risk agents. Exome sequencing of 22 000 genes with Illumina Nextera Exome Enrichment Kit was performed on 22 DNA samples (11 Bulgarian patients and 11 Serbian patients). Software analysis was performed via NextGene, Provean, and PolyPhen. The frequency of all annotated genetic variants with deleterious/damaging effect was compared with those of European populations. Then we focused on nonannotated variants (with no data available about them and not found in healthy Bulgarian controls). There is no statistically significant difference between annotated variants in BEN patients and European populations. From nonannotated variants with more than 40% frequency in both patients' groups, we nominated 3 genes with possible deleterious/damaging variants-CELA1, HSPG2, and KCNK5. Mutant genes (CELA1, HSPG2, and KCNK5) in BEN patients encode proteins involved in basement membrane/extracellular matrix and vascular tone, tightly connected to process of angiogenesis. We suggest that an abnormal process of angiogenesis plays a key role in the molecular pathogenesis of BEN.

Resource-allocation capabilities of commercial project management software. An experimental analysis

When project managers determine schedules for resource-constrained projects, they commonly use commercial project management software packages. Which resource-allocation methods are implemented in these packages is proprietary information. The resource-allocation problem is in general computationally difficult to solve to optimality. Hence, the question arises if and how various project management software packages differ in quality with respect to their resource-allocation capabilities. None of the few existing papers on this subject uses a sizeable data set and recent versions of common software packages. We experimentally analyze the resource-allocation capabilities of Acos Plus.1, AdeptTracker Professional, CS Project Professional, Microsoft Office Project 2007, Primavera P6, Sciforma PS8, and Turbo Project Professional. Our analysis is based on 1560 instances of the precedence- and resource-constrained project scheduling problem RCPSP. The experiment shows that using the resource-allocation feature of these packages may lead to a project duration increase of almost 115% above the best known feasible schedule. The increase gets larger with increasing resource scarcity and with increasing number of activities. We investigate the impact of different complexity scenarios and priority rules on the project duration obtained by the software packages. We provide a decision table to support managers in selecting a software package and a priority rule.

Comparative Analysis of Evolving Software Systems Using the Gini Coefficient

Software metrics offer us the promise of distilling useful information from vast amounts of software in order to track development progress, to gain insights into the nature of the software, and to identify potential problems. Unfortunately, however, many software metrics exhibit highly skewed, non-Gaussian distributions. As a consequence, usual ways of interpreting these metrics --- for example, in terms of "average" values --- can be highly misleading. Many metrics, it turns out, are distributed like wealth --- with high concentrations of values in selected locations. We propose to analyze software metrics using the Gini coefficient, a higher-order statistic widely used in economics to study the distribution of wealth. Our approach allows us not only to observe changes in software systems efficiently, but also to assess project risks and monitor the development process itself. We apply the Gini coefficient to numerous metrics over a range of software projects, and we show that many metrics not only display remarkably high Gini values, but that these values are remarkably consistent as a project evolves over time.

A Quantitative Analysis of Developer Information Needs in Software Ecosystems

We present the results of an investigation into the nature of information needs of software developers who work in projects that are part of larger ecosystems. This work is based on a quantitative survey of 75 professional software developers. We corroborate the results identified in the sur- vey with needs and motivations proposed in a previous sur- vey and discover that tool support for developers working in an ecosystem context is even more meager than we thought: mailing lists and internet search are the most popular tools developers use to satisfy their ecosystem-related information needs.

Explora: A Visualisation Tool for Metric Analysis of Software Corpora

When analysing software metrics, users find that visualisation tools lack support for (1) the detection of patterns within metrics; and (2) enabling analysis of software corpora. In this paper we present Explora, a visualisation tool designed for the simultaneous analysis of multiple metrics of systems in software corpora. Explora incorporates a novel lightweight visualisation technique called PolyGrid that promotes the detection of graphical patterns. We present an example where we analyse the relation of subtype polymorphism with inheritance and invocation in corpora of Smalltalk and Java systems and find that (1) subtype polymorphism is more likely to be found in large hierarchies; (2) as class hierarchies grow horizontally, they also do so vertically; and (3) in polymorphic hierarchies the length of the name of the classes is orthogonal to the cardinality of the call sites.

3D bloodstain pattern analysis: ballistic reconstruction of the trajectories of blood drops and determination of the centres of origin of the bloodstains

For crime scene investigation in cases of homicide, the pattern of bloodstains at the incident site is of critical importance. The morphology of the bloodstain pattern serves to determine the approximate blood source locations, the minimum number of blows and the positioning of the victim. In the present work, the benefits of the three-dimensional bloodstain pattern analysis, including the ballistic approximation of the trajectories of the blood drops, will be demonstrated using two illustrative cases. The crime scenes were documented in 3D, using the non-contact methods digital photogrammetry, tachymetry and laser scanning. Accurate, true-to-scale 3D models of the crime scenes, including the bloodstain pattern and the traces, were created. For the determination of the areas of origin of the bloodstain pattern, the trajectories of up to 200 well-defined bloodstains were analysed in CAD and photogrammetry software. The ballistic determination of the trajectories was performed using ballistics software. The advantages of this method are the short preparation time on site, the non-contact measurement of the bloodstains and the high accuracy of the bloodstain analysis. It should be expected that this method delivers accurate results regarding the number and position of the areas of origin of bloodstains, in particular the vertical component is determined more precisely than using conventional methods. In both cases relevant forensic conclusions regarding the course of events were enabled by the ballistic bloodstain pattern analysis.

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.