Demo Data from EDBT 2026 / reviewers in the wild / expert
Richard Baker 0006
dblp:13/4585-6
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 2013
—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
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.
| Software engineering, system software, and programming languages
1 paper |
Software testing · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software testing
mutation testing |
0.2 | 1 | 2013 | An Empirical Evaluation of Mutation Testing for Improving the Test Quality of Safety-Critical Software · IEEE Trans. Software Eng. 2013 |
Software testing
test coverage |
0.2 | 1 | 2013 | An Empirical Evaluation of Mutation Testing for Improving the Test Quality of Safety-Critical Software · IEEE Trans. Software Eng. 2013 |
Software testing › test suite evaluation
test quality assessment |
0.2 | 1 | 2013 | An Empirical Evaluation of Mutation Testing for Improving the Test Quality of Safety-Critical Software · IEEE Trans. Software Eng. 2013 |
Methods — techniques the papers use, named apart from their topics
root cause analysis · 0.2mutation testing · 0.2empirical evaluation · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2013 | An Empirical Evaluation of Mutation Testing for Improving the Test Quality of Safety-Critical SoftwareabstractTesting provides a primary means for assuring software in safety-critical systems. To demonstrate, particularly to a certification authority, that sufficient testing has been performed, it is necessary to achieve the test coverage levels recommended or mandated by safety standards and industry guidelines. Mutation testing provides an alternative or complementary method of measuring test sufficiency, but has not been widely adopted in the safety-critical industry. In this study, we provide an empirical evaluation of the application of mutation testing to airborne software systems which have already satisfied the coverage requirements for certification. Specifically, we apply mutation testing to safety-critical software developed using high-integrity subsets of C and Ada, identify the most effective mutant types, and analyze the root causes of failures in test cases. Our findings show how mutation testing could be effective where traditional structural coverage analysis and manual peer review have failed. They also show that several testing issues have origins beyond the test activity, and this suggests improvements to the requirements definition and coding process. Our study also examines the relationship between program characteristics and mutation survival and considers how program size can provide a means for targeting test areas most likely to have dormant faults. Industry feedback is also provided, particularly on how mutation testing can be integrated into a typical verification life cycle of airborne software. Richard Baker 0006, Ibrahim Habli |
IEEE Trans. Software Eng. | 1 |