Demo Data from EDBT 2026 / reviewers in the wild / expert
Faryn Dumont
dblp:320/9462
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2022
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 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 · 50% Blockchain and cryptocurrency security · 50% | |
| Software engineering, system software, and programming languages
1 paper |
Requirements engineering and software design · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Systems and software security
security testing |
0.6 | 1 | 2022 | Detecting Software Security Vulnerabilities Via Requirements Dependency Analysis · IEEE Trans. Software Eng. 2022 |
Blockchain and cryptocurrency security › smart contract security
vulnerability detection |
0.6 | 1 | 2022 | Detecting Software Security Vulnerabilities Via Requirements Dependency Analysis · IEEE Trans. Software Eng. 2022 |
Requirements engineering and software design
requirements traceability |
0.6 | 1 | 2022 | Detecting Software Security Vulnerabilities Via Requirements Dependency Analysis · IEEE Trans. Software Eng. 2022 |
Requirements engineering and software design › non-functional requirements
security requirements |
0.6 | 1 | 2022 | Detecting Software Security Vulnerabilities Via Requirements Dependency Analysis · IEEE Trans. Software Eng. 2022 |
Methods — techniques the papers use, named apart from their topics
requirements tracing · 1.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2022 | Detecting Software Security Vulnerabilities Via Requirements Dependency AnalysisabstractCyber attacks targeting software applications have a tremendous impact on our daily life. For example, attackers have utilized vulnerabilities of web applications to steal and gain unauthorized use of sensitive data stored in these systems. Previous studies indicate that security testing is highly precise, and therefore is widely applied to validate individual security requirements. However, dependencies between security requirements may cause additional vulnerabilities. Manual dependency detection faces scalability challenges, e.g., a previous study shows that the pairwise dependency analysis of 40 requirements would take around 12 hours. In this article, we present a novel approach which integrates the interdependency among high-level security requirements, such as those documented in policies, regulations, and standards. We then use automated requirements tracing methods to identify product-level security requirements and their dependencies. Our manual analysis of HIPAA and FIPS 200 leads to the identification of five types of high-level security requirements dependencies, which further inform the automated tracing methods and guide the designs of system-level security tests. Experimental results on five projects in healthcare and education domains show the significant recall improvements at 81 percent. Our case study on a deployed production system uncovers four previously unknown vulnerabilities by using the detected requirements dependencies as test paths, demonstrating our approach's value in connecting requirements engineering with security testing. Wentao Wang 0003, Faryn Dumont, Nan Niu, Glen Horton |
IEEE Trans. Software Eng. | 2 |