VLDB 2026 Research / reviewers in the wild / expert
Tom Love
dblp:97/4423
· DBLP profile ↗
4ranked-venue papers
0as first author
0since 2021 · last 1994
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 4
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
3 papers |
Software maintenance and evolution · 59% Requirements engineering and software design · 32% Empirical software engineering · 8% |
Topics — the 6 heaviest of 8, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › object-oriented analysis and design
object-oriented design |
0.0 | 1 | 1986 | Object-Oriented Programming for Product Development - Panel · OOPSLA 1986 |
Requirements engineering and software design › software design methodology
prototyping |
0.0 | 1 | 1989 | Panel: From Prototype to Product? · OOPSLA 1989 |
Software maintenance and evolution
program comprehension |
0.0 | 1 | 1979 | Measuring the Psychological Complexity of Software Maintenance Tasks with the Halstead and McCabe Metrics · IEEE Trans. Software Eng. 1979 |
Software maintenance and evolution
software complexity |
0.0 | 1 | 1979 | Measuring the Psychological Complexity of Software Maintenance Tasks with the Halstead and McCabe Metrics · IEEE Trans. Software Eng. 1979 |
Empirical software engineering
software metrics |
0.0 | 1 | 1979 | Measuring the Psychological Complexity of Software Maintenance Tasks with the Halstead and McCabe Metrics · IEEE Trans. Software Eng. 1979 |
Software maintenance and evolution › software maintenance
software modification |
0.0 | 1 | 1979 | Measuring the Psychological Complexity of Software Maintenance Tasks with the Halstead and McCabe Metrics · IEEE Trans. Software Eng. 1979 |
Methods — techniques the papers use, named apart from their topics
correlation analysis · 0.0controlled experiment · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1994 | Smalltalk in the Business World: The Good, the Bad, and the Future (Panel)
Yen-Ping Shan, Ken Auer, Andrew J. Bear, Jim Adamczyk, Adele Goldberg 0001, Tom Love, Dave A. Thomas |
OOPSLA | 6 |
| 1989 | Panel: From Prototype to Product?
Ken Auer, Theodore C. Goldstein, Tom Love, Dave A. Thomas |
OOPSLA | 4 |
| 1986 | Object-Oriented Programming for Product Development - Panel
Bob Wilhelm, Peggy Poggio, Evelyn Van Orden, Hamid Eghbalnia, Tom Love |
OOPSLA | 6 |
| 1979 | Measuring the Psychological Complexity of Software Maintenance Tasks with the Halstead and McCabe MetricsabstractThree software complexity measures (Halstead's E, McCabe's u(G), and the length as measured by number of statements) were compared to programmer performance on two software maintenance tasks. In an experiment on understanding, length and u(G) correlated with the percent of statements correctly recalled. In an experiment on modification, most significant correlations were obtained with metrics computed on modified rather than unmodified code. All three metrics correlated with both the accuracy of the modification and the time to completion. Relationships in both experiments occurred primarily in unstructured rather than structured code, and in code with no comments. The metrics were also most predictive of performance for less experienced programmers. Thus, these metrics appear to assess psychological complexity primarily where programming practices do not provide assistance in understanding the code. Bill Curtis, Sylvia B. Sheppard, Phil Milliman, M. A. Borst, Tom Love |
IEEE Trans. Software Eng. | 5 |