An empirical study on the impact of AspectJ on software evolvability

Abstract

Since its inception in 1996, aspect-oriented programming (AOP) has been believed to reduce the effort required to maintain software systems by replacing cross-cutting code with aspects. However, little convincing empirical evidence exists to support this claim, while several studies suggest that AOP brings new obstacles to maintainability. This paper discusses two controlled experiments conducted to evaluate the impact of AspectJ (the most mature and popular aspect-oriented programming language) versus Java on software evolvability. We consider evolvability as the ease with which a software system can be updated to fulfill new requirements. Since a minor language was compared to the mainstream, the experiments were designed so as to anticipate that the participants were much more experienced in one of the treatments. The first experiment was performed on 35 student subjects who were asked to comprehend either Java or AspectJ implementation of the same system, and perform the corresponding comprehension tasks. Participants of both groups achieved a high rate of correct answers without a statistically significant difference between the groups. Nevertheless, the Java group significantly outperformed the AspectJ group with respect to the average completion time. In the second experiment, 24 student subjects were asked to implement (in a noninvasive way) two extension scenarios to the system that they had already known. Each subject evolved either the Java version using Java or the AspectJ version using AspectJ. We found out that a typical AspectJ programmer needs significantly fewer atomic changes to implement the change scenarios than a typical Java programmer, but we did not observe a significant difference in completion time. The overall result indicates that AspectJ has a different effect on two sub-characteristics of the evolvability: understandability and changeability. While AspectJ decreases the former, it improves one aspect of the latter.Empir Software Eng

Playing the Sprint Retrospective

“…As future work, we want to measure in a quantitative experiment with settings similar to [Przybyłek, 2018] whether game-based retrospectives are more effective than standard retrospectives. Moreover, after collecting more data, we plan to build a recommender system [Karpus, 2019] that will help scrum teams to choose a retrospective game suitable for a given context.…”

Instructor Presence in Video Lectures: Preliminary Findings From an Online Experiment

“…To determine whether the observed differences were statistically significant, we followed the procedure presented in our prior research [46]. Since the box plots revealed that neither variable was normally distributed in both groups, we utilized a non-parametric Mann-Whitney U test.…”

“…Several issues must be considered before choosing the appropriate experimental design [46]. As for our experiment, we chose a between-subjects design to avoid the learning effect.…”

Fun Retrospectives in Intel Technology Poland

“…The only exception is 360° Appreciation, which, in fact, cannot be considered as a standalone retrospective. Nevertheless, we intend to further investigate the effect of anonymity in a controlled experiment with settings similar to [3,14,20,26].…”