Demo Data from VLDB 2026 / reviewers in the wild / expert
Maurice H. Halstead
dblp:48/1819
· DBLP profile ↗
4ranked-venue papers
2as first author
0since 2021 · last 1979
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 4 · 2 first-authorApplied, interdisciplinary, general and emerging computing · 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
2 papers |
Empirical software engineering · 93% Programming languages and type systems · 7% | |
| Interdisciplinary, comprehensive, and emerging computing
1 paper |
Computing education · 100% |
Topics — the 4 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering
software metrics |
0.0 | 2 | 1979 | The Frequency Distribution of Operators in PL/I Programs · IEEE Trans. Software Eng. 1979 A Simple Experiment in Top-Down Design · IEEE Trans. Software Eng. 1979 |
Empirical software engineering › software metrics
software science metrics |
0.0 | 1 | 1979 | A Simple Experiment in Top-Down Design · IEEE Trans. Software Eng. 1979 |
Computing education
programming education |
0.0 | 1 | 1979 | A Simple Experiment in Top-Down Design · IEEE Trans. Software Eng. 1979 |
Programming languages and type systems
language design |
0.0 | 1 | 1979 | The Frequency Distribution of Operators in PL/I Programs · IEEE Trans. Software Eng. 1979 |
Methods — techniques the papers use, named apart from their topics
software metrics · 0.0controlled experiment · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1979 | A Simple Experiment in Top-Down DesignabstractIn this paper we: 1) discuss the need for quantitatively reproducible experiments in the study of top-down design; 2) propose the design and writing of tutorial papers as a suitably general and inexpensive vehicle; 3) suggest the software science parameters as appropriate metrics; 4) report two experiments validating the use of these metrics on outlines and prose; and 5) demonstrate that the experiments tended toward the same optimal modularity. Douglas Comer, Maurice H. Halstead |
IEEE Trans. Software Eng. | 2 |
| 1979 | Guest Editorial on Software Science
Maurice H. Halstead |
IEEE Trans. Software Eng. | 1 |
| 1979 | The Frequency Distribution of Operators in PL/I ProgramsabstractDuring the past few years, several investigators have noted definite patterns in the distribution of operators in computer programs. Their proposed models have provided explanations for other observed software phenomena and have suggested possible relationships between programming languages and natural languages. However, these models contain notable deficiencies. Stuart H. Zweben, Maurice H. Halstead |
IEEE Trans. Software Eng. | 2 |
| 1978 | Management Prediction - Can Software Science Help?abstractNearly a generation ago, I was involved in sizing and scheduling a Navy programming project. Because it was estimated to be "half-again" as complicated as the one we had just done, it was predicted that it would require 75 man-years. When the system went to sea on time and on budget, those of us who had participated in the scheduling thought that we had demonstrated scheduling ability. None of us realized that we might instead have only demonstrated that a tossed coin can come up heads five times in a row. Maurice H. Halstead |
COMPSAC | 1 |