Demo Data from SIGIR 2026 / reviewers in the wild / expert
Stephen M. Thebaut
dblp:20/6341
· DBLP profile ↗
4ranked-venue papers
1as first author
0since 2021 · last 1989
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 3Databases, data management, data science and information retrieval · 1 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 1
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 |
Empirical software engineering · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering › software defect prediction
fault-prone component identification |
0.0 | 1 | 1985 | Identifying Error-Prone Software - An Empirical Study · IEEE Trans. Software Eng. 1985 |
Empirical software engineering › software metrics
product and process metrics |
0.0 | 1 | 1985 | Identifying Error-Prone Software - An Empirical Study · IEEE Trans. Software Eng. 1985 |
Empirical software engineering
software defect prediction |
0.0 | 1 | 1985 | Identifying Error-Prone Software - An Empirical Study · IEEE Trans. Software Eng. 1985 |
Empirical software engineering
software metrics |
0.0 | 1 | 1985 | Identifying Error-Prone Software - An Empirical Study · IEEE Trans. Software Eng. 1985 |
Methods — techniques the papers use, named apart from their topics
correlation analysis · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1989 | An approach to software fault localization and revalidation based on incremental data flow analysisabstractA systematic approach for reducing the cost of regression testing and fault localization through the use of incremental data flow analysis is described. Incremental data flow analysis is used to identify that portion of a program affected by a change so that testing efforts can be focused accordingly. The analysis allows the partitioning of existing test cases into relevant, nonrelevant, and invalid classes. This greatly reduces the effort associated with validating a program following modification.> Abu-Bakr Taha, Stephen M. Thebaut, Sying-Syang Liu |
COMPSAC | 2 |
| 1989 | The maintenance assistant: Work in progress
Norman Wilde, Stephen M. Thebaut |
J. Syst. Softw. | 2 |
| 1985 | Identifying Error-Prone Software - An Empirical StudyabstractA major portion of the effort expended in developing commercial software today is associated with program testing. Schedule and/ or resource constraints frequently require that testing be conducted so as to uncover the greatest number of errors possible in the time allowed. In this paper we describe a study undertaken to assess the potential usefulness of various product-and process-related measures in identifying error-prone software. Our goal was to establish an empirical basis for the efficient utilization of limited testing resources using objective, measurable criteria. Through a detailed analysis of three software products and their error discovery histories, we have found simple metrics related to the amount of data and the structural complexity of programs to be of value for this purpose. Vincent Y. Shen, Tze-Jie Yu, Stephen M. Thebaut, Lorri R. Paulsen |
IEEE Trans. Software Eng. | 3 |
| 1984 | An analytic resource model for large-scale software development
Stephen M. Thebaut, Vincent Y. Shen |
Inf. Process. Manag. | 1 |