Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Robert W. Reiter Jr.

dblp:02/1292 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1981
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 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 · 77% Requirements engineering and software design · 23%

Topics — the 2 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
controlled experiment
0.011981
A Controlled Experiment Quantitatively Comparing Software Development Approaches · IEEE Trans. Software Eng. 1981
Requirements engineering and software design › software process
software process measurement
0.011981
A Controlled Experiment Quantitatively Comparing Software Development Approaches · IEEE Trans. Software Eng. 1981

Methods — techniques the papers use, named apart from their topics

statistical hypothesis testing · 0.0controlled experiment · 0.0
YearPublicationVenuePosition
1981 A Controlled Experiment Quantitatively Comparing Software Development Approaches
abstract
A software engineering research study has been undertaken to empirically analyze and compare various software development approaches; its fundamental features and initial findings are presented in this paper. An experiment was designed and conducted to confirm certain suppositions concerning the beneficial effects of a particular disciplined methodology for software development. The disciplined methodology consisted of programming teams employing certain techniques and organizations commonly defined under the umbrella term structured programming. Other programming teams and individual programmers both served as control groups for comparison. The experimentally tested hypotheses involved a number of quantitative, objective, unobtrusive, and automatable measures of programming aspects dealing with the software development process and the developed software product. The experiment's results revealed several programming aspects for which statistically significant differences existed between the disciplined methodology and the control groups. The results were interpreted as confirmation of the original suppositions and evidence in favor of the disciplined methodology. This paper describes the specific features of the experiment; outlines the investigative approach used to plan, execute, and analyze it; reports its immediate results; and interprets them according to intuitions regarding the disciplined methodology.
Victor R. Basili, Robert W. Reiter Jr.
IEEE Trans. Software Eng.2