The DOI matches its Crossref record; 3 of the 3 references it cites were found in a registry or an index.
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].
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Halstead, M. H. (1977) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,339
Measuring application development productivity
Albrecht, A. (1979) · Medical Entomology and Zoology · Cited by 1,258
Self-citationPippenger, N. J. (1978) · Scientific American · doi:10.1038/scientificamerican0678-114 · Cited by 53
Cited by
Estimating software project effort using analogies
Shepperd, M., & Schofield, C. (1997) · IEEE Transactions on Software Engineering · doi:10.1109/32.637387 · Cited by 954
Where do capabilities come from and how do they matter? A study in the software services industry
Ethiraj, S. K., Kale, P., Krishnan, M. S., & Singh, J. V. (2005) · Strategic Management Journal · doi:10.1002/smj.433 · Cited by 897
An empirical validation of software cost estimation models
Kemerer, C. F. (1987) · Communications of the ACM · doi:10.1145/22899.22906 · Cited by 896
A systematic review of software development cost estimation studies
Jørgensen, M., & Shepperd, M. (2007) · Brunel University Research Archive (BURA) (Brunel University London) · doi:10.1109/tse.2007.3 · Cited by 742
A Systematic Review of Software Development Cost Estimation Studies
Jorgensen, M., & Shepperd, M. (2007) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.256943 · Cited by 729
Cross-project defect prediction: a large scale experiment on data vs. domain vs. process
Zimmermann, T., Nagappan, N., Gall, H. C., Giger, E., & Murphy, B. (2009) · Zurich Open Repository and Archive (University of Zurich) · doi:10.5167/uzh-25785 · Cited by 694
Systematic literature review of machine learning based software development effort estimation models
Wen, J., Li, S., Lin, Z., Hu, Y., & Huang, C. (2012) · Information and Software Technology · doi:10.1016/j.infsof.2011.09.002 · Cited by 526
Machine learning approaches to estimating software development effort
Srinivasan, K., & Fisher, D. (1995) · IEEE Transactions on Software Engineering · doi:10.1109/32.345828 · Cited by 483
Predicting risk of software changes
Mockus, A., & Weiss, D. M. (2002) · Bell Labs Technical Journal · doi:10.1002/bltj.2229 · Cited by 429
The adoption of software measures: A technology acceptance model (TAM) perspective
Wallace, L. G., & Sheetz, S. D. (2014) · Information & Management · doi:10.1016/j.im.2013.12.003 · Cited by 344
Clarke, P., & O’Connor, R. V. (2012) · Information and Software Technology · doi:10.1016/j.infsof.2011.12.003 · Cited by 332
Rai, A., Maruping, L. M., & Venkatesh, V. (2009) · MIS Quarterly · doi:10.2307/20650313 · Cited by 311
Software development cost estimation using function points
Matson, J. E., Barrett, B. E., & Mellichamp, J. M. (1994) · IEEE Transactions on Software Engineering · doi:10.1109/32.277575 · Cited by 291
Finnie, G. R., Wittig, G. E., & Desharnais, J.-M. (1997) · Journal of Systems and Software · doi:10.1016/s0164-1212(97)00055-1 · Cited by 286
Heiat, A. (2002) · Information and Software Technology · doi:10.1016/s0950-5849(02)00128-3 · Cited by 284
An assessment and comparison of common software cost estimation modeling techniques
Briand, L. C., El Emam, K., Surmann, D., Wieczorek, I., & Maxwell, K. D. (1999) · Proceedings of the 21st international conference on Software engineering · doi:10.1145/302405.302647 · Cited by 277
Software effort models for early estimation of process control applications
Mukhopadhyay, T., & Kekre, S. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.163607 · Cited by 272
Banker, R. D., Davis, G. B., & Slaughter, S. A. (1998) · Management Science · doi:10.1287/mnsc.44.4.433 · Cited by 269
On the Value of Ensemble Effort Estimation
Kocaguneli, E., Menzies, T., & Keung, J. W. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.111 · Cited by 266
An Empirical Analysis of Productivity and Quality in Software Products
Krishnan, M. S., Kriebel, C. H., Kekre, S., & Mukhopadhyay, T. (2000) · Management Science · doi:10.1287/mnsc.46.6.745.11941 · Cited by 264
Software cost estimation with incomplete data
Strike, K., El Emam, K., & Madhavji, N. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.962560 · Cited by 252
Data mining techniques for software effort estimation: a comparative study
Dejaeger, K., Verbeke, W., Martens, D., & Baesens, B. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.55 · Cited by 224
How does radical collocation help a team succeed?
Teasley, S., Covi, L., Krishnan, M. S., & Olson, J. S. (2000) · Proceedings of the 2000 ACM conference on Computer supported cooperative work · doi:10.1145/358916.359005 · Cited by 224
Metadata
- Authors
- Albrecht, A. J., & Gaffney, J. E.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 1983-11
- Volume
- SE-9
- Issue
- 6
- Pages
- 639-648
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W1994410397
- Cited by
- 1,558
- References
- 3
- FWCI
- 35.15
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.