Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Zixuan Tan

dblp:264/7702 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
2since 2021 · last 2025
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author · 1 since 2021Human-computer interaction and ubiquitous computing · 1 · 1 since 2021

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Network and information security
1 paper
Systems and software security · 100%
Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 100%
Human-computer interaction and pervasive computing
1 paper
Health and well-being technologies · 77% Design research and methods · 23%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Systems and software security › vulnerability discovery › software vulnerability detection
recurring vulnerability detection
0.912025
Similar but Patched Code Considered Harmful: The Impact of Similar but Patched Code on Recurring Vulnerability Detection and How to Remove Them · ICSE 2025
Systems and software security
vulnerability discovery
0.912025
Similar but Patched Code Considered Harmful: The Impact of Similar but Patched Code on Recurring Vulnerability Detection and How to Remove Them · ICSE 2025
Software maintenance and evolution › code clone management
code clone analysis
0.912025
Similar but Patched Code Considered Harmful: The Impact of Similar but Patched Code on Recurring Vulnerability Detection and How to Remove Them · ICSE 2025
Health and well-being technologies
telemedicine
0.612022
A Scenario-Based Study of Doctors and Patients on Video Conferencing Appointments from Home · ACM Trans. Comput. Hum. Interact. 2022
Design research and methods › design process
scenario-based design
0.212022
A Scenario-Based Study of Doctors and Patients on Video Conferencing Appointments from Home · ACM Trans. Comput. Hum. Interact. 2022

Methods — techniques the papers use, named apart from their topics

code change history analysis · 1.7clone detection · 1.7scenario-based design · 0.6contextual interviews · 0.6
YearPublicationVenuePosition
2025 Similar but Patched Code Considered Harmful: The Impact of Similar but Patched Code on Recurring Vulnerability Detection and How to Remove Them
abstract
Identifying recurring vulnerabilities is crucial for ensuring software security. Clone-based techniques, while widely used, often generate many false alarms due to the existence of similar but patched (SBP) code, which is similar to vulnerable code but is not vulnerable due to having been patched. Although the SBP code poses a great challenge to the effectiveness of existing approaches, it has not yet been well explored. In this paper, we propose a programming language agnostic framework, Fixed Vulnerability Filter (FVF), to identify and filter such SBP instances in vulnerability detection. Different from existing studies that leverage function signatures, our approach analyzes code change histories to precisely pinpoint SBPs and consequently reduce false alarms. Evaluation under practical scenarios confirms the effectiveness and precision of our approach. Remarkably, FVF identifies and filters 65.1 % of false alarms from four vulnerability detection tools (i.e., ReDeBug, VUDDY, MVP, and an elementary hash-based approach) without yielding false positives. We further apply FVF to 1,081 real-world software projects and construct a real-world SBP dataset containing 6,827 SBP functions. Due to the SBP nature, the dataset can act as a strict benchmark to test the sensitivity of the vulnerability detection approach in distinguishing real vulnerabilities and SBPs. Using this dataset, we demonstrate the ineffectiveness of four state-of-the-art deep learning-based vulnerability detection approaches. Our dataset can help developers make a more realistic evaluation of vulnerability detection approaches and also paves the way for further exploration of real-world SBP scenarios.
Zixuan Tan, Jiayuan Zhou, Xing Hu 0008, Shengyi Pan, Kui Liu 0001, Xin Xia 0001
ICSE1
2022 A Scenario-Based Study of Doctors and Patients on Video Conferencing Appointments from Home
abstract
Telemedicine systems that involve the use of video conferencing technologies have been available for more than three decades. Yet, they have primarily been used for specialist appointments or within health care facilities. We are now seeing a shift with the proliferation of commercial technologies, such as smartphone apps that allow people to have appointments with a general practitioner from nearly any location for various reasons. Telemedicine has also seen an uptake due to the COVID-19 pandemic. However, little is known about how doctors and patients perceive smartphone-based telemedicine systems, what types of medical ailments are best suited for these systems, what sociotechnical challenges might emerge through their usage, and how systems should be designed to best meet the needs of both doctors and patients. Thus, we applied a scenario-based design method by presenting a set of medical situations to both general practitioners and patients, and conducted contextual interviews with them to investigate their thoughts on video-based appointments for a range of medical situations. Results show that video consultations using smartphone apps could raise challenges in delivering appropriate care and utilization, conducting camera work to assist different types of examinations, supporting doctor–patient relationship creation and maintenance, allowing doctors to maintain control over the appointment, as well as protecting patients’ and doctors’ privacy. This suggests the need to create designs that can support particular workflows, relationship building, safety and privacy protection, and camera work for varying contexts.
Yasamin Heshmat, Denise Geiskkovitch, Zixuan Tan, Carman Neustaedter
ACM Trans. Comput. Hum. Interact.4