Abdullah Aldaeej

Dr. Abdullah Aldaeej


Research Focus & Metrics

Academic Career Length

5Years (2022-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
2 July 2022 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
SHSteffen Herbold
Steffen Herbold
ATAlexander Trautsch
Alexander Trautsch
BLBenjamin Ledel
Benjamin Ledel
AAAlireza Aghamohammadi
Alireza Aghamohammadi
TGTaher A. Ghaleb
Taher A. Ghaleb
JEJohannes Erbel
Johannes Erbel
Context: Tangled commits are changes to software that address multiple concerns at once. For researchers interested in bugs, tangled commits mean that they actually study not only bugs, but also other concerns irrelevant for the study of bugs. Objective: We want to improve our understanding of the prevalence of tangling and the types of changes that are tangled within bug fixing commits. Methods: We use a crowd sourcing approach for manual labeling to validate which changes contribute to bug fixes for each line in bug fixing commits. Each line is labeled by four participants. If at least three participants agree on the same label, we have consensus. Results: We estimate that between 17% and 32% of all changes in bug fixing commits modify the source code to fix the underlying problem. However, when we only consider changes to the production code files this ratio increases to 66% to 87%. We find that about 11% of lines are hard to label leading to active disagreements between participants. Due to confirmed tangling and the uncertainty in our data, we estimate that 3% to 47% of data is noisy without manual untangling, depending on the use case. Conclusion: Tangled commits have a high prevalence in bug fixes and can lead to a large amount of noise in the data. Prior research indicates that this noise may alter results. As researchers, we should be skeptics and assume that unvalidated data is likely very noisy, until proven otherwise.

13 December 2023 in Wireless Networks
Verified
Journal Article
Closed access
PDF file
IZIslam Zada
Islam Zada
Abdullah AlshammariAbdullah Alshammari
Abdullah Alshammari
AMAhmad Abdel Jabbar Mazhar
Ahmad Abdel Jabbar Mazhar
AAAbdullah Aldaeej
Abdullah Aldaeej
Sultan Noman QasemSultan Noman Qasem
Sultan Noman Qasem
JAJawad Alkhateeb
Jawad Alkhateeb

25 May 2023 in IEEE Access
Verified
Journal Article
Open access
HHHosna Hooshyar
Hosna Hooshyar
EGEduardo Guerra
Eduardo Guerra
JMJorge Melegati
Jorge Melegati
DKDron Khanna
Dron Khanna
AAAbdullah Aldaeej
Abdullah Aldaeej
ADAnh Nguyen Nguyen Duc
Anh Nguyen Nguyen Duc
The restrictions imposed by the COVID-19 pandemic required software development teams to adapt, being forced to work remotely and adjust the software engineering activities accordingly. In the studies evaluating these effects, a few have assessed the impact on software engineering activities from a broader perspective and after a period of time when teams had time to adjust to the changes. No studies have been found comparing software startups and established companies either. This paper aims to investigate the impacts of COVID-19 on software development activities after one year of the pandemic restrictions, comparing the results between startups and established companies. Our approach was to design a cross-sectional survey and distribute it online among software development companies worldwide. The participants were asked about their perception of COVID-19’s pandemic impact on different software engineering activities: requirements engineering, software architecture, user experience design, software implementation, and software quality assurance. The survey received 170 valid answers from 29 countries, and for all the software engineering activities, we found that most respondents did not observe a significant impact. The results also showed that software startups and established companies were affected differently since, in some activities, we found a negative impact in the former and a positive impact in the latter. Regarding the time spent on each software engineering activity, most of the answers reported no change, but on those that did, the result points to an increase in time. Thus, we cannot find any relation between the change in time of effort and the reported positive or negative impact.

27 December 2023 in Arabian Journal for Science and Engineering
Verified
Journal Article
Closed access
PDF file
AAAbdullah Aldaeej
Abdullah Aldaeej
MAMohammad Alshayeb
Mohammad Alshayeb

31 July 2024 in Information and Software Technology
Verified
Journal Article
Closed access
AAAbdullah Aldaeej
Abdullah Aldaeej
CSCarolyn Seaman
Carolyn Seaman

9 February 2024
Verified
Book Chapter
Open access
PDF file
DKDron Khanna
Dron Khanna
AAAbdullah Aldaeej
Abdullah Aldaeej
Establishing a psychologically safe work environment is crucial for leading a positive and practical agile retrospective. Emotions are closely intertwined concepts that come under the roof of psychology. Capturing them at the right time helps to detect harmful or favourable online behaviours, hinder or facilitate the software development cycle, and moralize or demoralize the team in a software company. This study aims to identify emotions that appear during the online agile retrospective. Our study asks the research question: How often are different emotions repeated during the online agile retrospective? We conducted a multiple case study with two software companies. We analyzed three recorded online retrospective sessions to seize various emotions. Our findings show that eighteen emotions appear on the agile retrospective. Some of the highest repeated emotions are approval, realization, excitement, relief, disappointment, confusion, optimism, and disapproval.