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.

Allan J. Albrecht

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

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

Software engineering, systems software and programming languages · 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
1 paper
Empirical software engineering · 100%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › software metrics
function points
0.011983
Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation · IEEE Trans. Software Eng. 1983
Empirical software engineering
software metrics
0.011983
Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation · IEEE Trans. Software Eng. 1983
Empirical software engineering
software effort estimation
0.011983
Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation · IEEE Trans. Software Eng. 1983
YearPublicationVenuePosition
1983 Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation
abstract
One of the most important problems faced by software developers and users is the prediction of the size of a programming system and its development effort. As an alternative to "size," one might deal with a measure of the "function" that the software is to perform. Albrecht [1] has developed a methodology to estimate the amount of the "function" the software is to perform, in terms of the data it is to use (absorb) and to generate (produce). The "function" is quantified as "function points," essentially, a weighted sum of the numbers of "inputs," "outputs,"master files," and "inquiries" provided to, or generated by, the software. This paper demonstrates the equivalence between Albrecht's external input/output data flow representative of a program (the "function points" metric) and Halstead's [2] "software science" or "software linguistics" model of a program as well as the "soft content" variation of Halstead's model suggested by Gaffney [7].
Allan J. Albrecht, John E. Gaffney Jr.
IEEE Trans. Software Eng.1