Published: Oct. 4, 2021
First and
Language: Английский
ACM Transactions on Software Engineering and Methodology, Journal Year: 2023, Volume and Issue: 32(4), P. 1 - 61
Published: Feb. 24, 2023
Background: Modern Code Review (MCR) is a lightweight alternative to traditional code inspections. While secondary studies on MCR exist, it unknown whether the research community has targeted themes that practitioners consider important. Objectives: The objectives are provide an overview of research, analyze practitioners' opinions importance investigate alignment between and practice, propose future avenues. Method: We conducted systematic mapping study survey state art until including 2021, employed Q-Methodology perception relevance analyzed primary studies' impact. Results: 244 studies, resulting in five themes. As result 1,300 data points, we found respondents positive about investigating impact product quality process properties. In contrast, they negative human factor- support systems-related research. Conclusion: These results indicate misalignment deemed important by most respondents. Researchers should focus solutions can improve practice. agenda potentially increase
Language: Английский
Citations
16
Information and Software Technology, Journal Year: 2022, Volume and Issue: 146, P. 106855 - 106855
Published: Feb. 5, 2022
Language: Английский
Citations
17
Empirical Software Engineering, Journal Year: 2025, Volume and Issue: 30(3)
Published: April 26, 2025
Language: Английский
Citations
0
Empirical Software Engineering, Journal Year: 2023, Volume and Issue: 29(1)
Published: Nov. 22, 2023
Language: Английский
Citations
9
Published: March 1, 2022
The phenomenon of architecture erosion can negatively impact the maintenance and evolution software systems, manifest in a variety symptoms during development. While is often considered rather late, its act as early warnings to developers, if detected time. In addition static source code analysis, reviews be detecting subsequently taking action. this study, we investigate discussed reviews, well their trends, actions taken by developers. Specifically, conducted an empirical study with two most active Open Source Software (OSS) projects OpenStack community (i.e., Nova Neutron). We manually checked 21,274 review comments retrieved keyword search random selection, identified 502 (from 472 discussion threads) that discuss erosion. Our findings show (1) proportion low, yet notable frequently are architectural violation, duplicate functionality, cyclic dependency; (2) declining trend OSS indicates tends stabilize over time; (3) identify have positive on removing symptoms, but few still remain ignored results suggest provides practical way reduce symptoms; analyzing help get insight about status avoid potential risk
Language: Английский
Citations
11
Empirical Software Engineering, Journal Year: 2022, Volume and Issue: 27(6)
Published: July 4, 2022
Language: Английский
Citations
9
Published: May 1, 2023
Method names are crucial to program comprehension and maintenance. Recently, many approaches have been proposed automatically recommend method detect inconsistent names. Despite promising, their results still suboptimal considering the three following drawbacks: 1) These models mostly trained from scratch, learning two different objectives simultaneously. The misalignment between will negatively affect training efficiency model performance. 2) enclosing class context is not fully exploited, making it difficult learn abstract functionality of method. 3) Current name consistency checking methods follow a generate-then-compare process, which restricts accuracy as they highly rely on quality generated face difficulty measuring semantic consistency.In this paper, we propose an approach named AUMENA AUtomate MEthod NAming tasks with context-aware prompt-tuning. Unlike existing deep based approaches, our first learns contextualized representation(i.e., attributes) programming language natural through pre-training model, then exploits capacity knowledge large prompt-tuning precisely more accurate To better identify semantically consistent names, task two-class classification problem, avoiding limitation previous approaches. Experiment reflect that scores 68.6%, 72.0%, 73.6%, 84.7% four datasets recommendation, surpassing state-of-the-art baseline by 8.5%, 18.4%, 11.0%, 12.0%, respectively. And 80.8% checking, reaching 5.5% outperformance. All data publicly available.
Language: Английский
Citations
4
Proceedings of the 37th ACM/SIGAPP Symposium on Applied Computing, Journal Year: 2024, Volume and Issue: unknown, P. 834 - 841
Published: April 8, 2024
Technical Debt (TD) 1 term in software systems was introduced over two decades ago and remains a critical concern development. It has the potential to evolve into liability that necessitates refactoring or rewriting code time. Regardless of its significance, there exists notable gap literature concerning comprehensive list technical debt indicators. The purpose this study is re-evaluate existing TD categorization extend indicators offer complete validated Type Indicator list. In study, we adopted qualitative research approach used mapping expert opinion techniques as approach. number extracted from formal 60 which extended 92 by reviewing gray literature. This then subjected review, with their feedback, grew an additional 21%. Consequently, present 10 distinct types, accompanied 120 would aid identification, resolution minimizing risks costs associated
Language: Английский
Citations
1
Empirical Software Engineering, Journal Year: 2024, Volume and Issue: 29(4)
Published: June 8, 2024
Abstract Identifying security issues early is encouraged to reduce the latent negative impacts on software systems. Code review a widely-used method that allows developers manually inspect modified code, catching during development cycle. However, existing code studies often focus known vulnerabilities, neglecting coding weaknesses, which can introduce real-world are more visible through review. The practices of reviews in identifying such weaknesses not yet fully investigated. To better understand this, we conducted an empirical case study two large open-source projects, OpenSSL and PHP. Based 135,560 comments, found reviewers raised concerns 35 out 40 weakness categories. Surprisingly, some related past as memory errors resource management, were discussed less than vulnerabilities. Developers attempted address many cases (39%-41%), but substantial portion was merely acknowledged (30%-36%), went unfixed due disagreements about solutions (18%-20%). This highlights slip even when identified. Our findings suggest identify various leading reviews. these results also reveal shortcomings current practices, indicating need for effective mechanisms or support increasing awareness issue management
Language: Английский
Citations
1
Published: July 10, 2024
Language: Английский
Citations
1