Software Engineering Projects Research Articles

Software Process Improvement by Managing Situational Method Engineering Knowledge

Organizational processes have been recognized as valuable knowledge assets. Situational Method Engineering (SME) processes are particularly valuable as they are used for engineering other processes: SME processes help construct bespoke Software Development Methodologies (SDMs) for specific software-engineering project situations. Every SDM has a Software Development Process (SDP) at its heart, which specifies the activities that should be performed throughout the project, the products that should be produced, and the people that should be involved. Existing SME methods suffer from certain weaknesses that are rooted in loss of knowledge within their processes; for instance, the method engineers' experience, which is a kind of tacit knowledge, is not properly captured and utilized in these processes. Managing SME process knowledge helps alleviate these weaknesses through reusing the software developers' experience and maintaining the method engineers' knowledge. We propose an evaluation framework that can be used for assessing an SME method's ability to manage process knowledge. We also provide a model that guides the improvement of existing SME methods in their support for Knowledge Management (KM), and also helps engineer new SME methods that provide adequate KM support. We have assessed the applicability of the proposed evaluation framework and improvement model by using them to enhance eight prominent SME methods, and also by applying them to four industrial case studies.

Gamifying software engineering subject to enhance the quality of knowledge

AbstractGamification has been widely used in education in recent years. Gamification has been proven to be a useful tool for students, as it motivates them and helps them to learn. The lack of motivation on the part of the students and their poor perception of the importance of software engineering has led to the definition of SESGA. This game has been designed and carried out on third year students of the computer science degree. SESGA has been designed for students to improve their knowledge of static code analysis, unit testing and Git. A software engineering project was carried out in groups, in which each of the students had to perform common software development tasks. The evaluation has measured the accomplishment, challenge, competence, guidance, immersion, playfulness and social involvement of SESGA obtaining remarkable results. It has also shown that SESGA has allowed students to have better academic results and the number of failures has decreased.

The nexus of project management approaches in sustainable development: innovative behaviors as a mechanism in the Polish financial industry

PurposeBased on the social exchange theory, the aim of the present study is to examine the effects, both direct and indirect (through sustainability-oriented innovative behaviors [SIBs]), of sustainable project leadership (SPL) on sustainable project performance (SPP). Project management approaches (PMAs) (traditional, hybrid and agile) were examined as conditional factors in the “SPL–SIBs” relationship.Design/methodology/approachThe study employs structural equation modeling based on data collected from 197 software engineering project team members working in the financial industry in Poland.FindingsThe study revealed that SPL significantly, positively affected SPP. It also provided evidence for the significant mediating impact of SIBs in the relationship between SPL and SPP and the conditional effect of agile and hybrid PMAs on the “SPL–SIBs” relationship.Originality/valueThe novelty of this work lies in introducing sustainable leadership into project management research, proposing and testing a unique and complex research framework, designing valid scales for measuring SPL and SPP, and suggesting many theoretical and empirical implications.

Review of method name recommendation

In software engineering projects, method name recommendation is a critical task aimed at assisting developers in selecting appropriate method names to enhance code readability and maintainability. Given the significance of method name recommendation, numerous researchers have delved into improving the quality of method names. In this paper, we systematically review the existing method name recommendation techniques and conduct a comprehensive analysis of their principles, characteristics, and performance. Furthermore, we summarize the comparisons and evaluations among various methods to aid researchers in choosing method name recommendation techniques that suit their specific requirements. Lastly, we highlight the future research directions in this field. Through this review, readers will gain a clearer understanding of the current state of method name recommendation, providing valuable guidance for further research and development.

A KNOWLEDGE MANAGEMENT GUIDELINE: IDENTIFYING AND QUANTIFYING THE KNOWLEDGE LEVEL OF A TEAM THAT WORKS FOR A SOFTWARE ENGINEERING PROJECT

This scientific paper aims to explore the identification and quantification of the knowledge level within a team working on a software engineering project. The knowledge level of a team plays a crucial role in the success and efficiency of project outcomes. To achieve this objective, a comprehensive review of existing literature on knowledge management, team dynamics, and software engineering practices was conducted. This article reveals insights into the knowledge dynamics within software engineering teams. The research methodology consists of different quantitative and qualitative methods for data collection and analysis. The identified knowledge gaps and strengths can inform strategies for improving team performance, such as targeted training programs or knowledge sharing initiatives. Furthermore, the quantification of knowledge levels can serve as a benchmark for future projects, allowing for better resource allocation and team composition. Overall, this research is bringing benefits to the field of software engineering by providing a systematic approach to identify and quantify the knowledge level of teams, enabling organizations to optimize their team structures and enhance project outcomes.

Students’ Communication Self-efficacy and Its Impact on the Enhancement of Communication Skills in Software Engineering Project Courses

Developing the communication skills of software engineering graduates to meet industry requirements is a challenge for educators. This study presents a project-based learning framework that promotes students’ communication skills in a software engineering project course. The questionnaire on self-efficacy for software development (CSESD) was designed for students’ self-assessment of their confidence in communication skills. Findings indicate that students’ CSESD increased significantly after the course ended. Educators can apply the designed framework to software development-related project courses. The CSESD questionnaire can be used to assess students' confidence in their communication skills and assist educators in preparing students’ readiness before graduation.

THE PLACE AND ROLE OF KNOWLEDGE MANAGEMENT IN A SUSTAINABLE ORGANIZATION FROM THE SOFTWARE ENGINEERING BRANCH

The tremendous growth of both market and customer requirements determines the projects in the software engineering branch to be characterized by complexity, dynamic and agility. As the significant results of the projects lead further to the sustainability of the organization, an important indicator of evolution is represented by how knowledge is treated within the organization and further transferred to the outside. There are multiple ways to operate projects from the software engineering branch and most of them are based on documented academical approaches as Agile Methodology or Waterfall Model, which present a different set of characteristics. However, this article studies, in an exploratory framework, how knowledge is gathered based on the approach of the project. This investigation might come at hand for those professionals that are willing to improve the project management framework by addressing those areas where a deep analysis of each process could help building a more efficient knowledge management in the organization. In addition to the contributions of understanding what’s happening with the knowledge in software engineering projects, this investigation can be used, as well, for researches about an organization’s sustainability.

Undergraduate research in software engineering. An experience and evaluation report  

The purpose of this paper is to present an undergraduate research experience process model and the evaluation of seven years of its application in an undergraduate research program in software engineering. Undergraduate students who participated in research projects between 2015 and 2022 were surveyed to find out a) their motivations for participating in research projects in software engineering, b) the skills they consider they have acquired or improved by participating in those projects, and c) their perception of benefits and utility for their future work and professional activities. Results reveal that participation in real research projects in software engineering is highly valued by undergraduate students, who perceive benefits in the development of research and soft skills, and for their future professional activity. In addition, these undergraduate research projects and the process followed show that it is feasible to make original contributions to the body of knowledge of software engineering.

An industry survey on approaches, success factors, and barriers for technology transfer in software engineering

AbstractOne central aspect of software engineering research is the transfer of the proposed approaches into industrial practice. In the past, a number of technology transfer approaches and experiences from technology transfer projects in software engineering have already been reported. However, many researchers still struggle to get their research results noticed by practitioners. To investigate what is important to practitioners, we conducted a mixed‐methods study that provides us with reliable quantitative data as well as deeper insights from qualitative data. Our results show that there is a mismatch between industry professionals' needs and commonly proposed technology transfer approaches in the software engineering field. For instance, collaboration between industry and academia as well as participation in empirical evaluations is not deemed important from an industry point of view. In contrast, industry professionals emphasize the use of company‐specific pilot projects conducted by industry and the need for experts to be available in every phase of technology transfer.

Research on the application of data mining technology in software engineering

The role of data mining in software engineering is obvious, but there is a lack of mining depth. In the past, engineering layout and function distribution problems in software development, and the framework construction was unreasonable. Therefore, this paper proposes a software system based on data mining technology. First, the software engineering project is divided, and the software engineering project design is carried out according to the interactive requirements to realize the preprocessing of software engineering. Then, according to the design criteria, the design collection of software engineering is formed, and the information system is analyzed in depth. MATLAB simulation shows that the design interactivity and accuracy of data mining are superior to traditional design methods under the condition that software engineering requirements are consistent.

Risk Management in Software Development Projects: A Systematic Literature Review

Risk Management is an integral part of every project. Risk management must estimate the risks’ significance, especially in the SDLC process, and mitigate those risks. Since 2016, many papers and journals have researched planning, design, and risk control in software development projects over the last five years. This study aims to find the most exciting topics for researchers in risk management, especially in software engineering projects. This paper takes a systematic approach to reviewing articles containing risk management in software development projects. This study collects papers and journals included in the international online library database, then summarizes them according to the stages of the PICOC methodology. This paper results in the focus of research in the last five years on Agile methods. The current issue is that many researchers are trying to explicitly integrate risk management into the Agile development process by creating a comprehensive risk management framework. This SLR helps future research get a theoretical basis to solve the studied problem. The SLR explains the focuses of previous research, analysis of research results, and the weaknesses of the investigation. For further study, take one of the topic papers, do a critical review, and find research gaps.

Performance Evolution of Software Engineering Development and Project Management: A Critical Evolution Software Engineering Process

Among the many pressing concerns in the realm of computers, software project development is among the highest. System development life cycle is a part of this (SDLC). A key goal of the software development life cycle (SDLC) is to reduce the likelihood of errors while improving the quality of the final result. Without a well-defined set of steps, the software development process is a pretty complicated affair. Method established to standardize and streamline software development. The introduction of the SDLC (Software Development Life Cycle) existence. What we have here is a methodical and organized approach to the process of creating software. Using the SDLC as a guide, entails a wide variety of steps and processes that must be completed before the final programmer is released. Software comes in many forms. Types of software development life cycles, each with their own benefits and drawbacks, are commonly employed in the software development process. Disadvantages Five of these software development life cycle (SDLC) models, including the waterfall model, the v-shaped model, and the prototype model, are presented in this study. Existing models are compared using a spiral and an iterative structure.

A Three-Year Study on Peer Evaluation in a Software Engineering Project Course

<italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">Background:</i> Peer evaluation in software engineering (SE) project courses enhances the learning experience of students. It also helps instructors monitor and assess both teams and individual students. Peer evaluations might influence the way individual students and teams work; therefore, the quality of the peer evaluations should be tracked through the project course. <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">Contribution:</i> In this article, we analyzed the quality and scoring behavior of students in peer evaluation in an undergraduate SE project course over three years. <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">Research Questions:</i> RQ1: What is the quality of peer evaluation of undergraduate students in a SE project course? RQ2: How do undergraduate students in an SE project course score each other? <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">Methodology:</i> The quality of peer evaluation (length, level of detail, etc.) and scoring of peers based on various aspects of peer evaluations of third-year students in a year-long SE project course were studied. Taking into account the grade students received at the end of the course (A, B, C, and F-calibers), peer evaluations were categorized, analyzed over time, and compared between students calibers. <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">Findings:</i> After analyzing 6854 peer evaluations from 193 students, it was found that the quality of peer evaluations across students was mostly consistent throughout the course. Also, it was observed that quantitative aspects of the peer evaluation were scored similarly across student calibers. However, the qualitative aspects of the peer evaluation were impacted by the caliber of students. These findings suggest that weaker students (i.e., C-caliber students) generally receive better quality peer evaluations than stronger students (i.e., A-caliber students). Finally, a preliminary analysis showed a positive connotation of emotions and sentiments found in the textual feedback delivered by students.

Summary of the Third International Workshop on Bots in Software Engineering (BotSE 2021)

Bots automate tasks in software engineering projects and interact with software developers. Bots have been proposed, for example, for testing, maintenance, and automating bug fixes. The research community has been discussing these bots in the International Workshop on Bots in Software Engineering (BotSE), collocated with ICSE (the International Conference on Software Engineering). The workshop participants share experiences and challenges, discuss new usages of bots, and map out future directions. In this paper, we present a summary of the 3rd edition of the workshop, which comprised nine papers, one journal-first presentation, and two keynotes, followed by extensive discussion. More details can be found at http://botse.org/

Assessing individual contributions to software engineering projects: a replication study

ABSTRACT Background and Context Assessing team members’ indivdiual contributions to software development projects poses a key problem for computing instructors. While instructors typically rely on subjective assessments, objective assessments could provide a more robust picture. To explore this possibility, In a 2020 paper, Buffardi presented a correlational analysis of objective metrics and subjective metrics in an advanced software engineering project course (n= 41 students and 10 teams), finding only two significant correlations. Objective To explore the robustness of Buffardi’s findings and gain further insight, we conducted a larger scale replication of the Buffardi study (n = 118 students and 25 teams) in three courses at three institutions. Method We collected the same data as in the Buffardi study and computed the same measures from those data. We replicated Buffardi’s exploratory, correlational and regression analyses of objective and subjective measures. Findings While replicating four of Buffardi’s five significant correlational findings and partially replicating the findings of Buffardi’s regression analyses, our results go beyond those of Buffardi by identifying eight additional significant correlations. Implications In contrast to Buffardi’s study, our larger scale study suggests that subjective and objective measures of individual performance in team software development projects can be fruitfully combined to provide consistent and complementary assessments of individual performance.

A comparative study of modeling and solution approaches for the multi-mode resource-constrained discrete time–cost trade-off problem: Case study of an ERP implementation project

Most knowledge-intensive industries, especially companies developing software engineering projects such as Enterprise Resource Planning (ERP) implementation projects, generally necessitate finding the optimal trade-off between the project duration and total usage cost of the renewable resource costs (e.g., human resource expertise costs). Therefore, the MRC-DTCTP, which integrates classical multi-mode resource-constrained project scheduling (MRCPSP) and discrete time–cost trade-off problems (DTCTP), can be seen as a more applicable problem since it better reflects the objectives and requirements of today’s real-life software project applications. The MRC-DTCTP is a much more complex variant of the MRCPSP since it aims to minimize total direct/indirect costs of the resources simultaneously under a pre-specified project deadline. Based on this motivation, a new explicit integer-linear programming (ILP) model of the MRC-DTCTP was first developed based on the implicit non-linear programming model of Wuliang and Chengen (2009). Due to its NP-hard nature, we also proposed a constraint programming (CP) model that includes several search strategies to solve large-sized problem instances within reasonable computation time. In addition, a genetic algorithm (GA) approach in combination with a Modified Serial Schedule Generation scheme (SSGS) is implemented to make further comparisons on several benchmark instances, which are generated based on the existing MRCPSP data sets taken from the project scheduling problem library (PSPLIB) by considering additional problem characteristics. A comprehensive experimental study has shown that the proposed CP model and GA approach can provide superior results in shorter run times for large-sized benchmark instances. Finally, an international Enterprise Resource Planning (ERP) Software Company’s real-life application is presented. The ERP projects generally necessitate finding the optimal trade-off between project makespan and human resource costs, making the MRC-DTCTP much more difficult than classical MRCPSPs & DTCTPs. For further analysis, time–cost trade-off curves under different human resource availabilities and project deadlines are drawn to provide managerial insights to ERP project managers.

A benchmarking program to support software process improvement adaptation in a developing country, a Pakistan case.

BackgroundStandardization of software development processes using the software process improvement (SPI) frameworks like capability maturity model integration (CMMI) or the International Organization for Standardization (ISO) are vital for better performance and defect-free delivery of software engineering projects.ProblemThe studies from developing countries show that the organizations are unable to get the desired SPI benefits during early adaptation due to lack of benchmarking initiatives. These initiative needed bridging of the gap between major software engineering fields such as project performance, productivity, and SPI measurement metrics like effort, schedule, cost, productivity, quality, and customer satisfaction.MethodThis research quantifies SPI benefits by bridging the existing gaps and identifying a commonly defined set of 44 significant base metrics related to ESCPQC and applies a conceptual framework over the collected data of 62 projects from three leading software organizations.ResultThe results have quantified the “the introduction of change effect” and showed that the adaptation of SPI has shown SPI benefits like improved quality, customer satisfaction, and effort. In contrast, schedule metrics showed a high reduction at level 3 and again increased at high maturity levels values. The last benefits are communicated following a trustable mechanism.

Using Model-to-Model Transformations for Web Software Architecture Simulation

The development of evaluation methods that allow improving the capture of quality data regarding software architectures is a topic of interest in Software Engineering. However, the dynamic of the traditional methods used for architecture evaluation is not enough to deal with the architectural complexity exhibit in new types of software products (such as cloud and web applications). In this paper, we present a model-to-model mapping based on modeling and simulation techniques that can be used as a complement of the traditional evaluation methods to improve the architecture design of complex systems. Using the set of elements that compose the architecture design of web applications, an abstraction model is designed with the aim to define the basic structure for the equivalent simulation model. Such a simulation model is detailed using two discrete-event formalisms: Discrete Event System Specification and Routed DEVS. In each case, a mapping is proposed to capture the full structure of the architecture with all its complexity. We compare both solutions to judge their applicability. Hence, the main advantages and disadvantages of both approaches are analyzed with the aim to evaluate their use in the architecture design stage of Software Engineering projects related to web applications.

Developers’ need for the rationale of code commits: An in-breadth and in-depth study

Communicating the rationale behind decisions is essential for the success of software engineering projects. In particular, understanding the rationale of code commits is an important and often difficult task. Although the software engineering community recognizes rationale need and importance, there is a lack of in-depth study of rationale for commits. To bridge this gap, we apply a mixed-methods approach, interviewing software developers and distributing two surveys, to study their perspective of rationale for code commits. We found that software developers need to investigate code commits to understand their rationale when working on diverse tasks. We also found that developers decompose the rationale of code commits into 15 components, each is differently needed, found, and recorded. Furthermore, we explored software developers’ experiences with rationale need, finding, and recording. We discovered factors leading software developers to give up their search for rationale of code commits. Our findings provide a better understanding of the need for rationale of code commits. In light of our findings, we discuss and present our vision about rationale of code commits practitioners’ documentation, tools support, and documentation automation. In addition, we discuss the benefits of analyzes that could arise from good documentation of rationale for code commits.

Industry–Academia Research Collaboration and Knowledge Co-creation: Patterns and Anti-patterns

Increasing the impact of software engineering research in the software industry and the society at large has long been a concern of high priority for the software engineering community. The problem of two cultures, research conducted in a vacuum (disconnected from the real world), or misaligned time horizons are just some of the many complex challenges standing in the way of successful industry–academia collaborations. This article reports on the experience of research collaboration and knowledge co-creation between industry and academia in software engineering as a way to bridge the research–practice collaboration gap. Our experience spans 14 years of collaboration between researchers in software engineering and the European and Norwegian software and IT industry. Using the participant observation and interview methods, we have collected and afterwards analyzed an extensive record of qualitative data. Drawing upon the findings made and the experience gained, we provide a set of 14 patterns and 14 anti-patterns for industry–academia collaborations, aimed to support other researchers and practitioners in establishing and running research collaboration projects in software engineering.