VLDB 2026 Research / reviewers in the wild / expert
F. Terry Baker
dblp:97/3669
· DBLP profile ↗
2ranked-venue papers
1as first author
0since 2021 · last 1987
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 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 |
Software testing · 50% Empirical software engineering · 25% Requirements engineering and software design · 15% |
Topics — the 4 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software testing
statistical testing |
0.0 | 1 | 1987 | Cleanroom Software Development: An Empirical Evaluation · IEEE Trans. Software Eng. 1987 |
Empirical software engineering
developer studies |
0.0 | 1 | 1987 | Cleanroom Software Development: An Empirical Evaluation · IEEE Trans. Software Eng. 1987 |
Requirements engineering and software design
formal specification |
0.0 | 1 | 1987 | Cleanroom Software Development: An Empirical Evaluation · IEEE Trans. Software Eng. 1987 |
Programming languages and type systems › programming paradigms
structured programming |
0.0 | 1 | 1975 | Structured Programming in a Production Programming Environment · IEEE Trans. Software Eng. 1975 |
Methods — techniques the papers use, named apart from their topics
statistical testing · 0.0formal methods · 0.0cleanroom · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1987 | Cleanroom Software Development: An Empirical EvaluationabstractThe Cleanroom software development approach is intended to produce highly reliable software by integrating formal methods for specification and design, nonexecution-based program development, and statistically based independent testing. In an empirical study, 15 three-person teams developed versions of the same software system (800-2300 source lines); ten teams applied Cleanroom, while five applied a more traditional approach. This analysis characterizes the effect of Cleanroom on the delivered product, the software development process, and the developers. Richard W. Selby, Victor R. Basili, F. Terry Baker |
IEEE Trans. Software Eng. | 3 |
| 1975 | Structured Programming in a Production Programming EnvironmentabstractDiscusses how structured programming methodology has been introduced into a large production programming organization using an integrated but flexible approach. It next analyzes the advantages and disadvantages of each component of the methodology and presents some quantitative results on its use. It concludes with recommendations based on this generally successful experience, which could be useful to other organizations interested in improving reliability and productivity. F. Terry Baker |
IEEE Trans. Software Eng. | 1 |