Zhiyuan Wan

Zhiyuan Wan

Auto-generated profile, based on publicly available information

Zhiyuan Wan

Zhejiang University, Hangzhou, 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
26 August 2019 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
ZWZhiyuan Wan
Zhiyuan Wan
XXXin Xia
Xin Xia
DLDavid Lo
David Lo
GMGail C. Murphy
Gail C. Murphy
Adding an ability for a system to learn inherently adds uncertainty into the system. Given the rising popularity of incorporating machine learning into systems, we wondered how the addition alters software development practices. We performed a mixture of qualitative and quantitative studies with 14 interviewees and 342 survey respondents from 26 countries across four continents to elicit significant differences between the development of machine learning systems and the development of non-machine-learning systems. Our study uncovers significant differences in various aspects of software engineering (e.g., requirements, design, testing, and process) and work characteristics (e.g., skill variety, problem solving and task identity). Based on our findings, we highlight future research directions and provide recommendations for practitioners.

23 October 2018 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
ZWZhiyuan Wan
Zhiyuan Wan
XXXin Xia
Xin Xia
AHAhmed E. Hassan
Ahmed E. Hassan
DLDavid Lo
David Lo
JYJianwei Yin
Jianwei Yin
XYXiaohu Yang
Xiaohu Yang
Defect prediction has been an active research area for over four decades. Despite numerous studies on defect prediction, the potential value of defect prediction in practice remains unclear. To address this issue, we performed a mixed qualitative and quantitative study to investigate what practitioners think, behave and expect in contrast to research findings when it comes to defect prediction. We collected hypotheses from open-ended interviews and a literature review of defect prediction papers that were published at ICSE, ESEC/FSE, ASE, TSE and TOSEM in the last 6 years (2012-2017). We then conducted a validation survey where the hypotheses became statements or options of our survey questions. We received 395 responses from practitioners from over 33 countries across five continents. Some of our key findings include: 1) Over 90 percent of respondents are willing to adopt defect prediction techniques. 2) There exists a disconnect between practitioners' perceptions and well supported research evidence regarding defect density distribution and the relationship between file size and defectiveness. 3) 7.2 percent of the respondents reveal an inconsistency between their behavior and perception regarding defect prediction. 4) Defect prediction at the feature level is the most preferred level of granularity by practitioners. 5) During bug fixing, more than 40 percent of the respondents acknowledged that they would make a “work-around” fix rather than correct the actual error-causing code. Through a qualitative analysis of free-form text responses, we identified reasons why practitioners are reluctant to adopt defect prediction tools. We also noted features that practitioners expect defect prediction tools to deliver. Based on our findings, we highlight future research directions and provide recommendations for practitioners.

24 April 2020 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
JHJunxiao Han
Junxiao Han
ESEmad Shihab
Emad Shihab
ZWZhiyuan Wan
Zhiyuan Wan
Shuguang DengShuguang Deng
Shuguang Deng
XXXin Xia
Xin Xia

6 June 2019 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
ZWZhiyuan Wan
Zhiyuan Wan
XXXin Xia
Xin Xia
AHAhmed E. Hassan
Ahmed E. Hassan
Blockchain-related discussions have become increasingly prevalent in programming Q\&A websites, such as Stack Overflow and other Stack Exchange communities. Analyzing and understanding those discussions could provide insights about the topics of interest to practitioners, and help the software development and research communities better understand the needs and challenges facing developers as they work in this new domain. Prior studies propose the use of LDA to study the Stack Exchange discussions. However, a simplistic use of LDA would capture the topics in discussions blindly without keeping in mind the variety of the dataset and domain-specific concepts. Specifically, LDA is biased towards larger sized corpora; LDA-derived topics are not linked to higher level domain-specific concepts. We propose an approach that combines balanced LDA (which ensures that the topics are balanced across the domain) with the reference architecture of a domain to capture and compare topics of discussions across the Stack Exchange communities. We make a number of interesting observations, including: (1) Bitcoin, Ethereum, Hyperledger Fabric and Corda are the four most commonly-discussed blockchain platforms on the Stack Exchange communities; (2) A broad range of topics are discussed at distinct layers in our derived reference architecture. The consensus layer topics are most commonly discussed; (3) We observe an overall growth in the absolute impact for all architectural layer topics. The application layer topics have the greatest absolute impact over time in comparison to other layer topics; (4) Application layer, API layer, consensus layer and network layer topics are commonly discussed across the studied blockchain platforms. Based on our findings, we highlight future directions and provide recommendations for practitioners and researchers.

30 November 2023
Verified
Conference Paper
Open access
ZWZhiyuan Wan
Zhiyuan Wan
YZYun Zhang
Yun Zhang
XXXin Xia
Xin Xia
YJYi Jiang
Yi Jiang
DLDavid Lo
David Lo
Software architecture has been an active research field for nearly four decades, in which previous studies make significant progress such as creating methods and techniques and building tools to support software architecture practice. Despite past efforts, we have little understanding of how practitioners perform software architecture related activities, and what challenges they face. Through interviews with 32 practitioners from 21 organizations across three continents, we identified challenges that practitioners face in software architecture practice during software development and maintenance. We reported on common software architecture activities at software requirements, design, construction and testing, and maintenance stages, as well as corresponding challenges. Our study uncovers that most of these challenges center around management, documentation, tooling and process, and collects recommendations to address these challenges.

21 December 2023 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
XZXiaoye Zheng
Xiaoye Zheng
ZWZhiyuan Wan
Zhiyuan Wan
YZYun Zhang
Yun Zhang
RCRui Chang
Rui Chang
DLDavid Lo
David Lo
Rust is an emerging programming language designed for the development of systems software. To facilitate the reuse of Rust code, crates.io , as a central package registry of the Rust ecosystem, hosts thousands of third-party Rust packages. The openness of crates.io enables the growth of the Rust ecosystem but comes with security risks by severe security advisories. Although Rust guarantees a software program to be safe via programming language features and strict compile-time checking, the unsafe keyword in Rust allows developers to bypass compiler safety checks for certain regions of code. Prior studies empirically investigate the memory safety and concurrency bugs in the Rust ecosystem, as well as the usage of unsafe keywords in practice. Nonetheless, the literature lacks a systematic investigation of the security risks in the Rust ecosystem. In this article, we perform a comprehensive investigation into the security risks present in the Rust ecosystem, asking “what are the characteristics of the vulnerabilities, what are the characteristics of the vulnerable packages, and how are the vulnerabilities fixed in practice?”. To facilitate the study, we first compile a dataset of 433 vulnerabilities, 300 vulnerable code repositories, and 218 vulnerability fix commits in the Rust ecosystem, spanning over 7 years. With the dataset, we characterize the types, life spans, and evolution of the disclosed vulnerabilities. We then characterize the popularity, categorization, and vulnerability density of the vulnerable Rust packages, as well as their versions and code regions affected by the disclosed vulnerabilities. Finally, we characterize the complexity of vulnerability fixes and localities of corresponding code changes, and inspect how practitioners fix vulnerabilities in Rust packages with various localities. We find that memory safety and concurrency issues account for nearly two thirds of the vulnerabilities in the Rust ecosystem. It takes over 2 years for the vulnerabilities to become publicly disclosed, and one-third of the vulnerabilities have no fixes committed before their disclosure. In terms of vulnerability density, we observe a continuous upward trend at the package level over time, but a decreasing trend at the code level since August 2020. In the vulnerable Rust packages, the vulnerable code tends to be localized at the file level, and contains statistically significantly more unsafe functions and blocks than the rest of the code. More popular packages tend to have more vulnerabilities, while the less popular packages suffer from vulnerabilities for more versions. The vulnerability fix commits tend to be localized to a limited number of lines of code. Developers tend to address vulnerable safe functions by adding safe functions or lines to them, vulnerable unsafe blocks by removing them, and vulnerable unsafe functions by modifying unsafe trait implementations. Based on our findings, we discuss implications, provide recommendations for software practitioners, and outline directions for future research.