<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>P320 - Software Engineering 2022</title>
<link href="http://dl.gi.de/handle/20.500.12116/37960" rel="alternate"/>
<subtitle/>
<id>http://dl.gi.de/handle/20.500.12116/37960</id>
<updated>2026-07-21T13:38:50Z</updated>
<dc:date>2026-07-21T13:38:50Z</dc:date>
<entry>
<title>A Survey on the Relevance of the Performance of Model Transformations</title>
<link href="http://dl.gi.de/handle/20.500.12116/37997" rel="alternate"/>
<author>
<name>Groner, Raffaela</name>
</author>
<author>
<name>Juhnke, Katharina</name>
</author>
<author>
<name>Höppner, Stefan</name>
</author>
<author>
<name>Tichy, Matthias</name>
</author>
<author>
<name>Becker, Steffen</name>
</author>
<author>
<name>Vijayshree, Vijayshree</name>
</author>
<author>
<name>Frank, Sebastian</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/37997</id>
<updated>2022-01-19T12:56:58Z</updated>
<published>2022-01-01T00:00:00Z</published>
<summary type="text">A Survey on the Relevance of the Performance of Model Transformations
Groner, Raffaela; Juhnke, Katharina; Höppner, Stefan; Tichy, Matthias; Becker, Steffen; Vijayshree, Vijayshree; Frank, Sebastian
Grunske, Lars; Siegmund, Janet; Vogelsang, Andreas
When we are confronted with performance issues in a general-purpose language, like Java, it is a given to us that we have various tools and techniques at our disposal to help us. But is such support also needed when using model transformation languages? To address this question, we conducted a quantitative online survey as part of a mixed methods study with 84 respondents to our questionnaire. Our results show that a certain performance is desired but not always achieved. The developers would like to improve the performance, but they lack insights on how a transformation is performed. As a first step to mitigate this issue, we compiled a list of information regarding the models used, the transformations applied and their execution deemed to be helpful by the participants. Additionally, we used hypotheses tests to investigate possible influencing factors that cause participants to try to improve the performance of transformations. The main relevant factors found in our study are the satisfaction with the execution time, the size of the models used, the relevance of whether a certain execution time is not exceeded in the average case, and the knowledge of how a transformation engine executes a transformation.
</summary>
<dc:date>2022-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>An Empirical Study of Flaky Tests in Python</title>
<link href="http://dl.gi.de/handle/20.500.12116/37998" rel="alternate"/>
<author>
<name>Gruber, Martin</name>
</author>
<author>
<name>Lukasczyk, Stephan</name>
</author>
<author>
<name>Kroiß, Florian</name>
</author>
<author>
<name>Fraser, Gordon</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/37998</id>
<updated>2022-01-19T12:56:58Z</updated>
<published>2022-01-01T00:00:00Z</published>
<summary type="text">An Empirical Study of Flaky Tests in Python
Gruber, Martin; Lukasczyk, Stephan; Kroiß, Florian; Fraser, Gordon
Grunske, Lars; Siegmund, Janet; Vogelsang, Andreas
This is a summary of our work presented at the International Conference on Software Testing 2021 [Gr21b]. Tests that cause spurious failures without code changes, i.e., flaky tests, hamper regression testing and decrease trust in tests. While the prevalence and importance of flakiness is well established, prior research focused on Java projects, raising questions about generalizability. To provide a better understanding of flakiness, we empirically study the prevalence, causes, and degree of flakiness within 22 352 Python projects containing 876 186 tests. We found flakiness to be equally prevalent in Python as in Java. The reasons, however, are different: Order dependency is a dominant problem, causing 59% of the 7 571 flaky tests we found. Another 28% were caused by test infrastructure problems, a previously less considered cause of flakiness. The remaining 13% can mostly be attributed to the use of network and randomness APIs. Unveiling flaky tests also requires more runs than often assumed: A 95% confidence that a passing test is not flaky on average would require 170 reruns. Additionally, through our investigations, we created a large dataset of flaky tests that other researchers already started building on [MM21; Ni21].
</summary>
<dc:date>2022-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Three Major Instructional Approaches for Requirements Engineering</title>
<link href="http://dl.gi.de/handle/20.500.12116/37993" rel="alternate"/>
<author>
<name>Daun, Marian</name>
</author>
<author>
<name>Grubb, Alicia M.</name>
</author>
<author>
<name>Tenbergen, Bastian</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/37993</id>
<updated>2022-01-19T12:56:57Z</updated>
<published>2022-01-01T00:00:00Z</published>
<summary type="text">Three Major Instructional Approaches for Requirements Engineering
Daun, Marian; Grubb, Alicia M.; Tenbergen, Bastian
Grunske, Lars; Siegmund, Janet; Vogelsang, Andreas
In this talk, we report on our findings from the paper A Survey of Instructional Approaches in the Requirements Engineering Education Literature, which has been accepted at and published in the proceedings of the 2021 IEEE International Conference on Requirements Engineering. The paper reports the findings of a systematic literature review to define and investigate the current state of research on requirements engineering education.
</summary>
<dc:date>2022-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Identifying Domain-Based Cyclic Dependencies in Microservice APIs Using Source Code Detectors</title>
<link href="http://dl.gi.de/handle/20.500.12116/37995" rel="alternate"/>
<author>
<name>Genfer, Patric</name>
</author>
<author>
<name>Zdun, Uwe</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/37995</id>
<updated>2022-01-19T12:56:57Z</updated>
<published>2022-01-01T00:00:00Z</published>
<summary type="text">Identifying Domain-Based Cyclic Dependencies in Microservice APIs Using Source Code Detectors
Genfer, Patric; Zdun, Uwe
Grunske, Lars; Siegmund, Janet; Vogelsang, Andreas
Isolation, autonomy, and loose coupling are critical success factors of microservice architectures, but unfortunately, systems tend to become strongly coupled over time and sometimes even exhibiting cyclic communication chains. These cycles can even manifest on a conceptual or domain level, making them hard to track for algorithms that rely solely on static analysis. Accordingly, previous attempts to detect cycles either focused on synchronous communication or had to collect additional runtime data, which can be costly and time-consuming. We suggest a novel approach for identifying and evaluating domain-based cyclic dependencies in microservice systems based on modular, reusable source code detectors. Based on the architecture model reconstructed by our detectors, we derived a set of architectural metrics for identifying and classifying domain-based cyclical dependencies. By conducting two case studies on open-source microservice architectures, we validated the feasibility and applicability of our approach.
</summary>
<dc:date>2022-01-01T00:00:00Z</dc:date>
</entry>
</feed>
