Chen Yang

Chen Yang

Auto-generated profile, based on publicly available information

Chen Yang

School of Artificial Intelligence, Shenzhen Polytechnic University, China

Research Focus & Metrics

Academic Career Length

9Years (2018-Present)

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

Representative Publications

View All Publications
3 February 2022 in Knowledge-Based Systems
Verified
Journal Article
Closed access
HWHongrun Wu
Hongrun Wu
YMYutao Ma
Yutao Ma
ZXZhenglong Xiang
Zhenglong Xiang
CYChen Yang
Chen Yang
KHKeqing He
Keqing He

19 July 2018 in Journal of Systems and Software
Verified
Journal Article
Closed access
TBTingting Bi
Tingting Bi
PLPeng Liang
Peng Liang
ATAntony Tang
Antony Tang
CYChen Yang
Chen Yang

15 December 2025 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
XZXiyu Zhou
Xiyu Zhou
RLRuiyin Li
Ruiyin Li
PLPeng Liang
Peng Liang
BZBeiqi Zhang
Beiqi Zhang
MSMojtaba Shahin
Mojtaba Shahin
CYChen Yang
Chen Yang
Design Rationale (DR) for software architecture decisions refers to the reasoning underlying architectural choices, which provides valuable insights into the different phases of the architecting process throughout software development. However, in practice, DR is often inadequately documented due to a lack of motivation and effort from developers. With the recent advancements in Large Language Models (LLMs), their capabilities in text comprehension, reasoning, and generation may enable the generation and recovery of DR for architecture decisions. In this study, we evaluated the performance of LLMs in generating DR for architecture decisions. First, we collected 50 Stack Overflow (SO) posts, 25 GitHub issues, and 25 GitHub discussions related to architecture decisions to construct a dataset of 100 architecture-related problems. Then, we selected five LLMs to generate DR for the architecture decisions with three prompting strategies, including zero-shot, chain of thought (CoT), and LLM-based agents. With the DR provided by human experts as ground truth, the Precision of LLM-generated DR with the three prompting strategies ranges from 0.267 to 0.278, Recall from 0.627 to 0.715, and F1-score from 0.351 to 0.389. Besides, 64.45% to 69.42% of the arguments of DR not mentioned by human experts are also helpful, 4.12% to 4.87% of the arguments have uncertain correctness, and 1.59% to 3.24% of the arguments are potentially misleading. To further understand the trustworthiness and applicability of LLM-generated DR in practice, we conducted semi-structured interviews with six practitioners. Based on the experimental and interview results, we discussed the pros and cons of the three prompting strategies, the strengths and limitations of LLM-generated DR, and the implications for the practical use of LLM-generated DR.

1 September 2020
Verified
Conference Paper
Closed access
ZLZengyang Li
Zengyang Li
QYQinyi Yu
Qinyi Yu
PLPeng Liang
Peng Liang
RMRan Mo
Ran Mo
CYChen Yang
Chen Yang
Defect technical debt (defect debt) refers to known deferred bugs that have not been fixed. The interest of a defect debt item (i.e., bug) is the extra effort needed to fix the bug due to the delay of fixing. It is important to measure defect debt interest in a software system in order to be aware of how much the interest of certain bugs is and which bugs should be fixed first. Furthermore, it is valuable to understand the features of the bugs of high interest or no interest, so as to facilitate the identification of those kinds of bugs. In this work, we proposed three pairs of measures for quantifying defect debt interest at three granularities (i.e., lines of code, source file, and package) of software changes, and conducted an exploratory case study on 13,438 bugs collected from 59 non-trivial Apache open source software projects written mainly in Java. We have the following findings. (1) Each bug, with an average of 224 days delay of fixing, has interest of 660 to 845 lines of code, 0.57 to 1.05 source files, and 0.29 to 0.35 package on average in need for understanding or modifying when fixing the bug. (2) The average interest of a bug shows overall increasing trends over delayed time of bug fixing and bug priority levels from the lowest to highest. (3) Around 30% of the bugs under study did not incur interest at the granularity of lines of code, which means that the involved source files in the bug-fixing commits of such bugs were not modified at all during the delayed time of bug fixing. (4) The average code change size of bug-fixing commits of a bug without interest is much smaller than that of a bug with (high) interest; for a bug without interest at the granularity of lines of code, the source files involved in the bug-fixing commits of the bug were alternately modified by different committers much less frequently than those of the bug with (high) interest.