Software Engineering Domain Research Articles

How do software practitioners perceive human-centric defects?

Context:Human-centric software design and development prioritises the way users prefer to complete their jobs, rather than expecting users to adapt to the software. Software users can have different genders, ages, cultures, languages, disabilities, socioeconomic statuses, and educational backgrounds, among many other differences. Due to the inherently varied nature of these differences and their impact on software usage, preferences and issues of users can vary, resulting in user-specific defects that we term as ‘human-centric defects’ (HCDs). Objective:This research aims to understand the perception and current management practices of such HCDs by software practitioners, identify key challenges in reporting, understanding and fixing them, and provide recommendations to improve HCDs management in software engineering. Methods:We conducted a survey and interviews with software engineering practitioners to gauge their knowledge and experience on HCDs and the defect tracking process. Results:We analysed fifty (50) survey- and ten (10) interview-responses from SE practitioners and identified that there are multiple gaps in the current management of HCDs in software engineering practice. There is a lack of awareness regarding human-centric aspects, causing them to be lost or under-appreciated during software development. Our results revealed that handling HCDs could be improved by following a better feedback process with end-users, a more descriptive taxonomy, and suitable automation. Conclusion:HCDs, given their diverse end-user base, present a major challenge to software practitioners. In the software engineering domain, research on HCDs has been limited and requires effort from research and practice communities to create awareness and support for human-centric aspects.

Navigating the Complexity of Generative AI Adoption in Software Engineering

This article explores the adoption of Generative Artificial Intelligence (AI) tools within the domain of software engineering, focusing on the influencing factors at the individual, technological, and social levels. We applied a convergent mixed-methods approach to offer a comprehensive understanding of AI adoption dynamics. We initially conducted a questionnaire survey with 100 software engineers, drawing upon the Technology Acceptance Model, the Diffusion of Innovation Theory, and the Social Cognitive Theory as guiding theoretical frameworks. Employing the Gioia methodology, we derived a theoretical model of AI adoption in software engineering: the Human-AI Collaboration and Adaptation Framework. This model was then validated using Partial Least Squares–Structural Equation Modeling based on data from 183 software engineers. Findings indicate that at this early stage of AI integration, the compatibility of AI tools within existing development workflows predominantly drives their adoption, challenging conventional technology acceptance theories. The impact of perceived usefulness, social factors, and personal innovativeness seems less pronounced than expected. The study provides crucial insights for future AI tool design and offers a framework for developing effective organizational implementation strategies.

Agile, continuous building energy modeling and simulation

Digital twins have emerged as highly valuable tools for model-based planning, simulation and optimization over the last couple of years, thereby demonstrating considerable potential for application within the construction industry. The introduction of building information modeling (BIM) has effectively established a standardized approach to representing building models. However, in practice, many of these models currently exhibit limitations as to their quality, specifically concerning the level of detail they encompass. In addition, BIM models too often are locked inside a specific vendor’s tool which readily implies a lack of platform independence, or interoperability, which, however, is essential for facilitating single and regressive, i.e., after a design change, model-based building performance simulations. Model-based engineering has effectively addressed comparable challenges within the domain of software engineering over the past decades by facilitating the integration and interoperability of models from various origins, by capitalizing on model-based tool integration. Prompted by these advantages, this study introduces a model-based tool environment that addresses the aforesaid challenges concerning BIM model quality and interoperability. Taking advantage of our proposed model-based tool environment, we implement an agile, continuous planning process for regressive, model-based building performance simulations, thereby enhancing building energy efficiency planning.

Fuzzy ensemble of fined tuned BERT models for domain-specific sentiment analysis of software engineering dataset.

Software engineers post their opinions about various topics on social media that can be collectively mined using Sentiment Analysis. Analyzing this opinion is useful because it can provide insight into developers' feedback about various tools and topics. General-purpose sentiment analysis tools do not work well in the software domain because most of these tools are trained on movies and review datasets. Therefore, efforts are underway to develop domain-specific sentiment analysis tools for the Software Engineering (SE) domain. However, existing domain-specific tools for SE struggle to compute negative and neutral sentiments and can not be used on all SE datasets. This work uses a hybrid technique based on deep learning and a fine-tuned BERT model, i.e., Bert-Base, Bert-Large, Bert-LSTM, Bert-GRU, and Bert-CNN presented that is adapted as a domain-specific sentiment analysis tool for Community Question Answering datasets (named as Fuzzy Ensemble). Five different variants of fine-tuned BERT on the SE dataset are developed, and an ensemble of these fine-tuned models is taken using fuzzy logic. The trained model is evaluated on four publicly available benchmark datasets, i.e., Stack Overflow, JavaLib, Jira, and Code Review, using various evaluation metrics. The fuzzy Ensemble model is also compared with the state-of-the-art sentiment analysis tools for the software engineering domain, i.e., SentiStrength-SE, Senti4SD, SentiCR, and Generative Pre-Training Transformer (GPT). GPT mode is fine-tuned by the authors for domain-specific sentiment analysis. The Fuzzy Ensemble model covers the limitation of existing tools and improve accuracy to predict neutral sentiments even on diverse dataset. The fuzzy Ensemble model performs superior to state-of-the-art tools by achieving a maximum F1-score of 0.883.

ScrumSpiral: An Improved Hybrid Software Development Model

In the lightning-quick world of software development, it is essential to find the most effective and efficient development methodology. This thesis represents "Scrum Spiral" which is an improved hybrid software development model that combines the features of Scrum and Spiral approach to enhance the software development process. This thesis aims to identify the usefulness of "ScrumSpiral" methodology and compare it with other hybrid software development models to encourage its use in software development projects. To develop this hybrid model, we did extensive research on the software engineering domain and decided to create a hybrid model by using Scrum and Spiral, named "Scrum Spiral" which is suitable for complicated projects and also for those projects whose requirements are not fixed. Traditional software development models face numerous challenges in rapidly changing markets. By developing this kind of hybrid model, we want to overcome these kinds of limitations and present the software development community with a novel concept for better project results. Final outcome of this thesis was that we developed a model that should be able to complete the project according to the expected schedule, satisfy customer requirements, and obtain productivity through team coordination. The significance of the hybrid model "Scrum Spiral" is reflected in its ability to offer flexibility towards various size projects, proactive risk management to identify all risks before developing the system, and result in higher-quality outcomes for those projects whose requirements are not properly described initially in the project.

Forum Text Processing and Summarization

Frequently Asked Questions (FAQs) are extensively studied in general domains like the medical field, but such frameworks are lacking in domains such as software engineering and open-source communities. This research aims to bridge this gap by establishing the foundations of an automated FAQ Generation and Retrieval framework specifically tailored to the software engineering domain. The framework involves analyzing, ranking, performing sentiment analysis, and summarization techniques on open forums like StackOverflow and GitHub issues. A corpus of Stack Overflow post data is collected to evaluate the proposed framework and the selected models. Integrating state-of-the-art models of string-matching models, sentiment analysis models, summarization models, and the proprietary ranking formula proposed in this paper forms a robust Automatic FAQ Generation and Retrieval framework to facilitate developers' work. String matching, sentiment analysis, and summarization models are evaluated, and F1 scores of 71.31%, 74.90%, and 53.4% were achieved. Given the subjective nature of evaluations in this context, a human review is used to further validate the effectiveness of the overall framework, with assessments made on relevancy, preferred ranking, and preferred summarization. Future work includes improving summarization models by incorporating text classification and summarizing them individually (Kou et al, 2023), as well as proposing feedback loop systems based on human reinforcement learning. Furthermore, efforts will be made to optimize the framework by utilizing knowledge graphs for dimension reduction, enabling it to handle larger corpora effectively

Adversarial Robustness of Deep Neural Networks: A Survey from a Formal Verification Perspective

Neural networks have been widely applied in security applications such as spam and phishing detection, intrusion prevention, and malware detection. This black-box method, however, often has uncertainty and poor explainability in applications. Furthermore, neural networks themselves are often vulnerable to adversarial attacks. For those reasons, there is a high demand for trustworthy and rigorous methods to verify the robustness of neural network models. Adversarial robustness, which concerns the reliability of a neural network when dealing with maliciously manipulated inputs, is one of the hottest topics in security and machine learning. In this work, we survey existing literature in adversarial robustness verification for neural networks and collect 39 diversified research works across machine learning, security, and software engineering domains. We systematically analyze their approaches, including how robustness is formulated, what verification techniques are used, and the strengths and limitations of each technique. We provide a taxonomy from a formal verification perspective for a comprehensive understanding of this topic. We classify the existing techniques based on property specification, problem reduction, and reasoning strategies. We also demonstrate representative techniques that have been applied in existing studies with a sample model. Finally, we discuss open questions for future research.

Barriers of Agile Requirements Engineering in the Public Sector: A Systematic Literature Review

Aim/Purpose: The objective of this study is to summarize the challenges of Agile Requirements Engineering (Agile RE) in the public sector in republican and constitutional monarchy nations. Additionally, it offers recommendations to address these challenges. Background: Failure of IT projects in the public sector results in financial losses for the state and loss of public trust, often attributed to issues in requirements engineering such as prioritization of user needs and excessive scope of requirements. IT projects can have a higher success rate with Agile RE, but there are also drawbacks. Therefore, this study holds significance by presenting a thorough framework designed to pinpoint and overcome the challenges associated with Agile RE to increase the success rate of IT projects. Methodology: This study employs a Systematic Literature Review (SLR) protocol in the field of software engineering or related domains, which consists of three main phases: planning the review, conducting the review with a snowballing approach, and reporting the review. Furthermore, the authors perform open coding to categorize challenges based on the Agile methodologies adoption factor model and axial coding to map potential solutions. Contribution: The authors assert that this research enriches the existing literature on Agile RE, specifically within the public sector context, by mapping out challenges and possible solutions that contribute to creating a foundation for future studies to conduct a more in-depth analysis of Agile adoption in the public sector. Furthermore, it compares the barriers of Agile RE in the public sector with the general context, leading to the discovery of new theories specifically for this field. Findings: Most challenges related to Agile RE in the public sector are found in the people and process aspects. Project and organizational-related are subsequent aspects. Therefore, handling people and processes proficiently is imperative within Agile RE to prevent project failure. Recommendations for Practitioners: Our findings offer a comprehensive view of Agile RE in the public sector in republican and constitutional monarchy nations. This study maps the challenges encountered by the public sector and provides potential solutions. The authors encourage practitioners to consider our findings as a foundation for adopting Agile methodology in the public sector. Furthermore, this study can assist practitioners in identifying existing barriers related to Agile RE, pinpointing elements that contribute to overcoming those challenges, and developing strategies based on the specific needs of the organizations. Recommendation for Researchers: Researchers have the potential to expand the scope of this study by conducting research in other countries, especially African countries, as this study has not yet encompassed this geographic region. Additionally, they can strengthen the evidence linking Agile RE challenges to the risk of Agile project failure by performing empirical validation in a specific country. Impact on Society: This research conducts a comprehensive exploration of Agile RE within the public sector, serving as a foundation for the successful adoption of Agile methodology by overcoming obstacles related to Agile RE. This study highlights the importance of managing people, processes, projects, and organizational elements to increase the success of Agile adoption in the public sector. Future Research: In the future, researchers should work towards resolving the limitations identified in this study. This study has not provided a clear prioritization of challenges and solutions according to their significance. Therefore, future researchers can perform a Fuzzy Analytical Hierarchical Process (F-AHP) to prioritize the proposed solutions.

Summary of the 1st Interpretability and Robustness in Neural Software Engineering (InteNSE 2023)

InteNSE is an interdisciplinary workshop for research at the intersection of Machine Learning (ML) and Software Engineering (SE) and would be a pioneer in emphasizing the implicit properties of neural software engineering and analysis. Due to recent computational advancements, ML has become an inseparable part of the SE research community. ML can indeed improve and revolutionize many SE tasks. However, most research in the AI and SE communities consider ML as a closed box, i.e., only considering the final performance of the developed models as an evaluation metric. Ignoring the implicit properties of neural models, such as interpretability and robustness, one cannot validate the model's actual performance, generalizability, and whether it is learning what it is supposed to do. Specifically, in the domain of SE, where the result of ML4SE tools is code synthesis, bug finding, or repair, interpretability and robustness are crucial to ensure the reliability of the products.

Building Domain-Specific Machine Learning Workflows: A Conceptual Framework for the State-of-the-Practice

Domain experts are increasingly employing machine learning to solve their domain-specific problems. This article presents to software engineering researchers the six key challenges that a domain expert faces in addressing their problem with a computational workflow, and the underlying executable implementation. These challenges arise out of our conceptual framework which presents the “route” of transformations that a domain expert may choose to take while developing their solution. To ground our conceptual framework in the state-of-the-practice, this article discusses a selection of available textual and graphical workflow systems and their support for the transformations described in our framework. Example studies from the literature in various domains are also examined to highlight the tools used by the domain experts as well as a classification of the domain-specificity and machine learning usage of their problem, workflow, and implementation. The state-of-the-practice informs our discussion of the six key challenges, where we identify which challenges and transformations are not sufficiently addressed by available tools. We also suggest possible research directions for software engineering researchers to increase the automation of these tools and disseminate best-practice techniques between software engineering and various scientific domains.

Current Insights From Task Area 1 in NFDI4Energy: Building and Serving the Energy Research Community

Energy system research has become increasingly reliant on modeling and simulation approaches. These endeavors are enabled by continuously improving tools and methods for developing, maintaining and sharing models and data. Knowledge of how to better conduct, share and archive one’s research has become increasingly complex and hard to manage for individual researchers or single research groups. Identifying and including relevant scientists from energy research, social sciences, and further disciplines is sometimes difficult. Furthermore, a plethora of best practices and guidelines exist on how to prepare data, models and results in ways that make them easier to discover, verify and build upon. To present a sustainable, problem-solving, technical solution for the energy research community, NFDI4Energy develops in Task Area 1 (TA1) two services of the NFDI4Energy platform. Consequentially, the intention of this abstract within the disciplinary track “Engineering” is to provide an overview of the development process with a special focus on Competence and Best Practices. In addition, it discusses interconnections with other Task Areas as well as the chances and challenges that are associated with those connections. The academic audience, e.g., from the Information Systems and (Software) Engineering domain at CoRDI 2023, can observe and discuss our proposed procedure with other community members. Furthermore, we expect interested individuals to compare the proposed procedures with their own, which can lead to meaningful discussions and knowledge-sharing situations within the Engineering domain.

Exploring knowledge management from a software engineering perspective

Context: The knowledge domain of software engineering (SE) gradually expands due to fast emerging technologies and complex organisational processes. The software industry represents a special focus of interest from a Knowledge Management (KM) perspective, as it is characterized by high employee turnover, a high level of outsourced projects, and an accelerated pace of technology innovations. Knowledge management can substantially influence SE knowledge's life cycle, contributing to better structuring of organisational processes of knowledge creation, knowledge transfer, and knowledge sharing. Reflecting on the trends for SE automation with artificial intelligence tools, KM approaches can enable companies and professionals to reconsider the future of SE work. Purpose: The present research aims to identify and investigate how implementing knowledge management principles and processes within the software engineering domain can facilitate the future transformation of software-related jobs. Based on a conceptual model, built upon the literature review, the paper analyses the quantitative data, collected from 91 software experts. Evaluating the impact of both organizational and domain types of SE knowledge, the discussion evaluates the unique value-adding SE processes along with models of how to explore AI applications to automate the SE domain. Results: The outcomes of the analysis identify the models of structuring knowledge management processes in SE both within the technological domain and organisational layers. The discussion section establishes suitable KM methods and approaches for supporting SE job transformation. It identifies the main knowledge management integration practices, demonstrating how combining KM with AI-based innovations may change the SE knowledge flow, improving substantially SE activities like onboarding new team members, monitoring software documentation, version control, and error tracking.

Towards Causal Analysis of Empirical Software Engineering Data: The Impact of Programming Languages on Coding Competitions

There is abundant observational data in the software engineering domain, whereas running large-scale controlled experiments is often practically impossible. Thus, most empirical studies can only report statistical correlations —instead of potentially more insightful and robust causal relations. To support analyzing purely observational data for causal relations, and to assess any differences between purely predictive and causal models of the same data, this paper discusses some novel techniques based on structural causal models (such as directed acyclic graphs of causal Bayesian networks). Using these techniques, one can rigorously express, and partially validate, causal hypotheses; and then use the causal information to guide the construction of a statistical model that captures genuine causal relations—such that correlation does imply causation. We apply these ideas to analyzing public data about programmer performance in Code Jam, a large world-wide coding contest organized by Google every year. Specifically, we look at the impact of different programming languages on a participant’s performance in the contest. While the overall effect associated with programming languages is weak compared to other variables—regardless of whether we consider correlational or causal links—we found considerable differences between a purely associational and a causal analysis of the very same data. The takeaway message is that even an imperfect causal analysis of observational data can help answer the salient research questions more precisely and more robustly than with just purely predictive techniques—where genuine causal effects may be confounded.

Automated Identification of Toxic Code Reviews Using ToxiCR

Toxic conversations during software development interactions may have serious repercussions on a Free and Open Source Software (FOSS) development project. For example, victims of toxic conversations may become afraid to express themselves, therefore get demotivated, and may eventually leave the project. Automated filtering of toxic conversations may help a FOSS community maintain healthy interactions among its members. However, off-the-shelf toxicity detectors perform poorly on a software engineering dataset, such as one curated from code review comments. To counter this challenge, we present ToxiCR , a supervised learning based toxicity identification tool for code review interactions. ToxiCR includes a choice to select one of the 10 supervised learning algorithms, an option to select text vectorization techniques, eight preprocessing steps, and a large-scale labeled dataset of 19,651 code review comments. Two out of those eight preprocessing steps are software engineering domain specific. With our rigorous evaluation of the models with various combinations of preprocessing steps and vectorization techniques, we have identified the best combination for our dataset that boosts 95.8% accuracy and an 88.9% F1-score in identifying toxic texts. ToxiCR significantly outperforms existing toxicity detectors on our dataset. We have released our dataset, pre-trained models, evaluation results, and source code publicly, which is available at https://github.com/WSU-SEAL/ToxiCR .

Learning environments in software testing education: An overview

AbstractNowadays, we heavily depend on software, as we utilize it daily. Bugs in the software can cause significant damage, loss of private data and money, and even loss of human lives. Software testing and quality assurance discipline, which belongs to the software engineering domain, aims to ensure that the software is good enough before its release to the market. Therefore, it is vital to ensure that software engineers are highly trained in this domain. Unfortunately, this discipline is frequently neglected throughout software engineering courses. Students are mostly taught just the theoretical principles of software testing and gain little practical experience. Additionally, the software testing lectures are considered to be dull, especially if they are not followed by practical tasks where the students could apply learned techniques and gain hands‐on experience. Several tools, games, and collaborative learning environments have been proposed to make the lectures more interesting and increase student engagement. The main goal of this article is to provide a systematic survey of such environments, where each environment was evaluated in terms of major software testing topics covered and the approach used to engage the students.

Context-Based Support to Enhance Developers’ Learning of Software Security

Software security is an ongoing problem, largely due to a lack of security knowledge among software developers from diverse backgrounds. To counter this, security experts are attempting to offer a broad range of knowledge resources to enlighten developers about increasing cybersecurity threats. Unfortunately, the abundance of knowledge resources does not seem to have much of an impact on reducing the issue of software security. The ineffective teaching and learning approaches for software security have created difficulties for developers in learning security knowledge. This research employs a four-cycle of Design Science Research Methodology (DSRM) to integrate necessary elements in the development of a context-based learning system for security education and learning. The final artifact is an ontology-based web application that facilitates a contextualized learning process by providing security knowledge through contextual software cases. Through evaluation in pedagogical and software development environments, it is proven to contribute a viable solution to the problem domain. While these results are positive, the innovative context-based artifact benefits not only the domain of software engineering but also other educational fields, such as information security and computer security.

Prioritizing tasks in software development: A systematic literature review.

Task prioritization is one of the most researched areas in software development. Given the huge number of papers written on the topic, it might be challenging for IT practitioners-software developers, and IT project managers-to find the most appropriate tools or methods developed to date to deal with this important issue. The main goal of this work is therefore to review the current state of research and practice on task prioritization in the Software Engineering domain and to individuate the most effective ranking tools and techniques used in the industry. For this purpose, we conducted a systematic literature review guided and inspired by the Preferred Reporting Items for Systematic Reviews and Meta-Analyses, otherwise known as the PRISMA statement. Based on our analysis, we can make a number of important observations for the field. Firstly, we found that most of the task prioritization approaches developed to date involve a specific type of prioritization strategy-bug prioritization. Secondly, the most recent works we review investigate task prioritization in terms of "pull request prioritization" and "issue prioritization," (and we speculate that the number of such works will significantly increase due to the explosion of version control and issue management software systems). Thirdly, we remark that the most frequently used metrics for measuring the quality of a prioritization model are f-score, precision, recall, and accuracy.

On the Validity of Pre-Trained Transformers for Natural Language Processing in the Software Engineering Domain

Transformers are the current state-of-the-art of natural language processing in many domains and are using traction within software engineering research as well. Such models are pre-trained on large amounts of data, usually from the general domain. However, we only have a limited understanding regarding the validity of transformers within the software engineering domain, i.e., how good such models are at understanding words and sentences within a software engineering context and how this improves the state-of-the-art. Within this article, we shed light on this complex, but crucial issue. We compare BERT transformer models trained with software engineering data with transformers based on general domain data in multiple dimensions: their vocabulary, their ability to understand which words are missing, and their performance in classification tasks. Our results show that for tasks that require understanding of the software engineering context, pre-training with software engineering data is valuable, while general domain models are sufficient for general language understanding, also within the software engineering domain.

Avoidance of the term agile in software engineering: Necessary and possible

AbstractThe term agile is frequently used in IT especially in the area of software engineering. The broad pervasiveness of the term agile is astonishing, because it is not well defined in the area of software engineering. The fuzziness of the term agile comes with the danger of ill‐founded decisions and ideological discussions. Both slow down the gain in knowledge in the domain of software engineering. The term agile should therefore not be used either in science nor in the industry.This article provides a critical discussion of the term agile. By using a three‐layered abstraction concept for software development processes, the use of the term agile can be avoided.

Classification framework for faulty-software using enhanced exploratory whale optimizer-based feature selection scheme and random forest ensemble learning.

Software Fault Prediction (SFP) is an important process to detect the faulty components of the software to detect faulty classes or faulty modules early in the software development life cycle. In this paper, a machine learning framework is proposed for SFP. Initially, pre-processing and re-sampling techniques are applied to make the SFP datasets ready to be used by ML techniques. Thereafter seven classifiers are compared, namely K-Nearest Neighbors (KNN), Naive Bayes (NB), Linear Discriminant Analysis (LDA), Linear Regression (LR), Decision Tree (DT), Support Vector Machine (SVM), and Random Forest (RF). The RF classifier outperforms all other classifiers in terms of eliminating irrelevant/redundant features. The performance of RF is improved further using a dimensionality reduction method called binary whale optimization algorithm (BWOA) to eliminate the irrelevant/redundant features. Finally, the performance of BWOA is enhanced by hybridizing the exploration strategies of the grey wolf optimizer (GWO) and harris hawks optimization (HHO) algorithms. The proposed method is called SBEWOA. The SFP datasets utilized are selected from the PROMISE repository using sixteen datasets for software projects with different sizes and complexity. The comparative evaluation against nine well-established feature selection methods proves that the proposed SBEWOA is able to significantly produce competitively superior results for several instances of the evaluated dataset. The algorithms' performance is compared in terms of accuracy, the number of features, and fitness function. This is also proved by the 2-tailed P-values of the Wilcoxon signed ranks statistical test used. In conclusion, the proposed method is an efficient alternative ML method for SFP that can be used for similar problems in the software engineering domain.