events

Dear all, In this week’s reading club we want to take a closer look at the qualitative method of semi-structured interviews. The paper combines experiences from 12 software engineering studies and discusses particularly challenging areas: effort estimation, interview skills, good interaction and appropriate tools and artifacts. If you wanna know more: Join us on Friday, October the 23th, 13:00 - 14:00 on Zoom for the next SERG Reading Club 📖📚!:

Abstract: Test smells attempt to capture design issues in test code that reduce their maintainability. Previous work found such smells to be highly common in automatically generated test-cases, but based this result on specific static detection rules; although these are based on the original definition of “test smells”, a recent empirical study showed that developers perceive these as overly strict and non-representative of the maintainability and quality of test suites. This leads us to investigate how effective such test smell detection tools are on automatically generated test suites.

Monitoring software behaviour is being done in various ways. Log messages are being output by almost any kind of running software system. Therefore, learning how software behaves from doing analysis over log data can lead to new insights about the system. However, the number of log messages in a computer system grow fast, and analysing the log data by hand is a time-consuming job. The objective of this study is to propose and implement a scalable architecture for doing real-time log analysis.

Dear all, Join us on Friday, October the 16th, 13:00 - 14:00 on Zoom for the next SERG Reading Club 📖📚!: “Diversity in software engineering research” by Nagappan, M., Zimmermann, T., & Bird, C. The title could be a bit missleading, so let me include the abstract 😉: One of the goals of software engineering research is to achieve generality: Are the phenomena found in a few projects reflective of others?

Dear all, Join us on October the 9th, 13:00 - 14:00 on Zoom for the next SERG Reading Club 📖📚!: “The Nature of Theory in Information Systems” by Shirley Gregor (https://bit.ly/2GbWgdA) Wanna join & you are not part of our Mattermost? Send an email to c.e.brandt /at/ tudelft.nl to get the Zoom link 😊

Mistakes in binary conditions are a source of error in many software systems. They happen when developers use < or > instead of <= or >=. These boundary mistakes are hard to find for developers and pose a manual labor-intensive work. While researches have been proposing solutions to identify errors in boundary conditions, the problem remains a challenge. Therefore it is necessary to research and develop new techniques to cope with such errors.

Dear all, In next weeks' reading club we want to put all that theoretical theory discussion into practice by looking at a paper that actually proposes a theory in software engineering 📑📚 Join us on September the 18th, 13:00 - 14:00 on Zoom to discuss an internal paper proposing a theory 🙂

Web APIs can have constraints on parameters, such that not all parameters are either always required or always optional. Sometimes the presence or value of one parameter could cause another parameter to be required. Additionally, parameters could have restrictions on what kinds of values are valid. We refer to these as inter-parameter and single-parameter constraints respectively. Having a clear overview of the constraints can help API consumers to integrate without the need for additional support and with fewer integration faults.

Evolutionary-based crash reproduction techniques aid developers in their debugging practices by generating a test case that reproduces a crash given its stack trace. In these techniques, the search process is typically guided by a single search objective called Crash Distance. Previous studies have shown that current approaches could only reproduce a limited number of crashes due to a lack of diversity in the population during the search. In this talk, I will present our recent work on the redesign of the search-objectives for crash reproduction by (i) applying Multi-Objectivization using Helper-Objectives (MO-HO) on crash reproduction.

Quality of code structure often degrades while a codebase grows. Counteracting this process or remedying its effects by improving the structure takes lots of effort. Software Modularization is a research topic that has tried to reduce this effort, by developing approaches that can find change suggestions that improve the code structure from the perspective of certain metrics. This topic has been researched for around 25 years and many approaches have been introduced and applied.