Visualization of contributions to open-source projects

We analyze visually, to what extend team members and external developers contribute to open-source projects to have a high-level impression about collaboration in that projects. For that, we record the provenance of the development process and draw the resulting property graph. Our graph drawings show, which developers are jointly changed the same files what we apply to Germany's COVID-19 exposure notification app 'Corona-Warn-App'

Modelling Knowledge about Software Processes using Provenance Graphs and its Application to Git-based Version Control Systems

Using the W3C PROV data model, we present a general provenance model for software development processes and, as an example, specialized models for git services, for which we generate provenance graphs. Provenance graphs are knowledge graphs, since they have defined semantics, and can be analyzed with graph algorithms or semantic reasoning to get insights into processes

The novel mTOR inhibitor RAD001 (Everolimus) induces antiproliferative effects in human pancreatic neuroendocrine tumor cells

Background/Aim: Tumors exhibiting constitutively activated PI(3) K/Akt/mTOR signaling are hypersensitive to mTOR inhibitors such as RAD001 (everolimus) which is presently being investigated in clinical phase II trials in various tumor entities, including neuroendocrine tumors (NETs). However, no preclinical data about the effects of RAD001 on NET cells have been published. In this study, we aimed to evaluate the effects of RAD001 on BON cells, a human pancreatic NET cell line that exhibits constitutively activated PI(3) K/Akt/mTOR signaling. Methods: BON cells were treated with different concentrations of RAD001 to analyze its effect on cell growth using proliferation assays. Apoptosis was examined by Western blot analysis of caspase-3/PARP cleavage and by FACS analysis of DNA fragmentation. Results: RAD001 potently inhibited BON cell growth in a dose-dependent manner which was dependent on the serum concentration in the medium. RAD001-induced growth inhibition involved G0/G1-phase arrest as well as induction of apoptosis. Conclusion: In summary, our data demonstrate antiproliferative and apoptotic effects of RAD001 in NET cells in vitro supporting its clinical use in current phase II trials in NET patients. Copyright (c) 2007 S. Karger AG, Basel

The (cost-)effectiveness of a lifestyle physical activity intervention in addition to a work style intervention on the recovery from neck and upper limb symptoms in computer workers

BACKGROUND: Neck and upper limb symptoms are frequently reported by computer workers. Work style interventions are most commonly used to reduce work-related neck and upper limb symptoms but lifestyle physical activity interventions are becoming more popular to enhance workers health and reduce work-related symptoms. A combined approach targeting work style and lifestyle physical activity seems promising, but little is known on the effectiveness of such combined interventions. METHODS/DESIGN: The RSI@Work study is a randomised controlled trial that aims to assess the added value of a lifestyle physical activity intervention in addition to a work style intervention to reduce neck and upper limb symptoms in computer workers. Computer workers from seven Dutch companies with frequent or long-term neck and upper limb symptoms in the preceding six months and/or the last two weeks are randomised into three groups: (1) work style group, (2) work style and physical activity group, or (3) control group. The work style intervention consists of six group meetings in a six month period that take place at the workplace, during work time, and under the supervision of a specially trained counsellor. The goal of this intervention is to stimulate workplace adjustment and to improve body posture, the number and quality of breaks and coping behaviour with regard to high work demands. In the combined (work style and physical activity) intervention the additional goal is to increase moderate to heavy physical activity. The control group receives usual care. Primary outcome measures are degree of recovery, pain intensity, disability, number of days with neck and upper limb symptoms, and number of months without neck and upper limb symptoms. Outcome measures will be assessed at baseline and six and 12 months after randomisation. Cost-effectiveness of the group meetings will be assessed using an employer's perspective. DISCUSSION: This study will be one of the first to assess the added value of a lifestyle physical activity intervention in addition to a work style intervention in reducing neck and upper limb symptoms of computer workers. The results of the study are expected in 2007

Using Provenance to Trace Software Development Processes

Today's software development processes are complex in their nature. Simple development process models, such as the waterfall model, have been replaced by iterative methods, such as the Rational Unied Process (RUP), or more exible agile approaches. Furthermore many tools are used in these processes, such as version control systems, issue trackers or continuous integration frameworks. In all phases of the software development, from planning to the implementation and nal delivery, numerous interactions occur between developers, the tools they use while developing and automatically between dierent tools. Examples of these interactions include: i) discussion about a feature request, ii) entering or changing requirements in an issue tracking system iii) automatic code style checks during a check-in. Information about these processes is, if available, distributed over the dierent tools being used. Version control systems feature a history of all les and their editors, issue tracking systems a list of all comments for an issue. Still, the missing link between these dierent tools makes it either impossible to draw conclusions from these data, or very time-consuming, considering the immense amount of available data. Many questions appearing on a daily basis cannot be answered, e.g., "To which requirement does this commit belong?" or "Who is responsible for a failing unit-test?". This master thesis aims at making it possible to follow and reproduce the entire process of developing a software product, being able to easily answer the above questions at any point in the development process. An example process is selected and transformed into a specic model, holding all required data. As this data should not be inserted manually into the model by developers, but recorded automatically, the model must be integrated into a distributed software engineering tool suite (version control system, bug tracking, integrated development environment, etc.). Furthermore, it must be possible to perform automatic audits and analysis on the collected data. The foundations of this thesis have been established in the research area of provenance. Provenance is dened as the origin or history of data. General models to describe and store data, query the data for information and methods for adapting processes to the model have been developed and are used as a basis

Provenance of Software Development Processes

"Why does the build fail currently?" - This and similar ques- tions arise on a daily basis in software development processes (SDP). There is no easy way to answer these questions, the required information is stored throughout different tools, the version control and continuous integration systems in this example. The tools mainly live in isolated worlds and no direct connection between their data exists. This paper proposes a solution to such problems, based on provenance technologies. After outlining the complexity of a SDP, the questions arising on a daily basis are categorized. Finally an approach to make the SDP provenance- aware is proposed based on PRiME, the Open Provenance Model and a SOA architecture using Neo4j to store the data, Gremlin to query it and REST webservices as connection to the tools

Concurrent Systems Engineering in Aerospace: From Excel-based to Model Driven Design

Concurrent engineering is a modern and very effective discipline of systems engineering. In the European space domain, the European Space Agency is the pioneer in this area and has performed early design studies for 10 years now. The Integrated Design Model (IDM) is still the state of the art in concurrent engineering software environments. It is based on Microsoft Excel, which induces several benefits and drawbacks related to concurrent engineering. The German Aerospace Center has used the IDM for several design studies and has identified two promising approaches to further increase the effectiveness of the concurrent engineering software environment by using modern model driven software technologies. Both concepts were implemented, and in this paper they are compared to each other and opposed to the IDM