We are happy to announce that our paper “Using (Bio)Metrics to Predict Code Quality Online”, written by Sebastian Müller and Thomas Fritz, was one of the most downloaded software engineering articles in June and July 2016. With 1709 downloads in 6 weeks, it scored the second place of all ACM software engineering articles. According to ACM, this is the first time that any paper was downloaded more than 1000 times.
The paper investigates the use of biometrics, such as heart rate variability (HRV) or electro-dermal activity (EDA) to determine the difficulty that developers experience while working on real world change tasks and automatically identify code quality concerns while a developer is making a change to the code. It can be accessed here.
We are excited to announce that Joel Scheuner has received a University of Zurich semester award in the fall semester 2014 for his excellent bachelor thesis Cloud WorkBench – A Web-Based Framework for Benchmarking Cloud Services.
We are excited to announce that out paper “Discovering Loners and Phantoms in Commit and Issue Data” has been accepted for the 23rd IEEE International Conference on Program Comprehension (ICPC 2015) in Florence, Italy.
The interlinking of commit and issue data has become a de-facto standard in software development. Modern issue tracking systems, such as JIRA, automatically interlink commits and issues by the extraction of identifiers (e.g., issue key) from commit messages. However, the conventions for the use of interlinking methodologies vary between software projects. For example, some projects enforce the use of identifiers for every commit while others have less restrictive conventions. In this work, we introduce a model called PaLiMod (Partial Linking Model) to enable the analysis of interlinking characteristics in commit and issue data. We surveyed 15 Apache projects to investigate differences and commonalities between linked and non-linked commits and issues (RQ1). Based on the gathered information, we created a set of heuristics to interlink the residual of non-linked commits and issues (RQ2).
We observed that in the majority of the analyzed projects, the number of commits linked to issues is higher than the number of commits without link. On average, 74% of commits are linked to issues and 50% of the issues have associated commits. Based on the survey data, we identified two interlinking characteristics which we call Loners (one commit, one issue) and Phantoms (multiple commits, one issue). For these two characteristics, we proposed heuristics to automatically interlink non-linked commit and issue data. The evaluation results showed that our approach can achieve an overall precision of 96% with a recall of 92% in case of the Loner heuristic and an overall precision of 73% with a recall of 53% in case of the Phantom heuristic.
The results of our evaluation indicate that the proposed PaLiMod model and heuristics enable an automatic interlinking and can indeed reduce the residual of non-linked commits and issues in software projects.
Our paper “Would Static Analysis Tools Help Developers with Code Reviews?” has been accepted as full research paper for the 2015 IEEE International Conference on Software Analysis, Evolution, and Reengineering in Montreal, Canada.
Our paper “SQA-Profiles: Rule-based Activity Profiles for Continuous Integration Environments” has has been accepted as full research paper for the 2015 IEEE International Conference on Software Analysis, Evolution, and Reengineering in Montreal, Canada.
We are currently attending the FSE’14 conference in Hong Kong where we presented our paper on software developers’ perceptions of productivity in front of a great audience in the Charles K. Kao Auditorium (i.e. the golden egg) in the Hong Kong Science park. We were also very happy to learn that our paper was nominated for the “Distinguished Paper Award” – we will know more tonight 😉
In the meantime, if you want to read the paper, you may find it here.
The better the software development community becomes at creating software, the more software the world seems to demand. Although there is a large body of research about measuring and investigating productivity from an organizational point of view, there is a paucity of research about how software developers, those at the front-line of software construction, think about, assess and try to improve their productivity. To investigate software developers’ perceptions of software development productivity, we conducted two studies: a survey with 379 professional software developers to help elicit themes and an observational study with 11 professional software developers to investigate emergent themes in more detail. In both studies, we found that developers perceive their days as productive when they complete many or big tasks without significant interruptions or context switches. Yet, the observational data we collected shows our participants performed significant task and activity switching while still feeling productive. We analyze such apparent contradictions in our findings and use the analysis to propose ways to better support developers in a retrospection and improvement of their productivity through the development of new tools and a sharing of best practices.
You may find the pre-print here.
You can find the survey and interview questions and the visualization of the observational data here. Please contact us if you have any questions.
Innovation Snacks are technology talks about research and development activities, technologies, and tools. It is a joint event series of s.e.a.l. and adesso, in which researchers and practitioners meet for breakfast and technical talks about the current state and future of software engineering. Today, my colleagues (Florian Stucki & Philipp Nützi) and I had the chance to present our information fragments tool, a prototype we developed in the past semester (HS13). The idea of the tool is that it aggregates data from various project data sources (from code, to work items, to people information) and visualizes the combination of the data to answer different stakeholders’ (developers, testers, managers, customers) questions in an intuitive web interface by visualizing the data in various ways. The tool can easily be extended with any other repository (that offers its data via web service), such as requirements, use cases, etc. For more information, please refer to the files here.