CoChat
Sign Up
Cited by 5,981Software Engineering Techniques and PracticesSoftware Engineering ResearchSoftware Reliability and Analysis Research

The DOI matches its Crossref record.

Software Engineering Economics

Boehm, Barry W.·2001·Pioneers and Their Contributions to Software Engineering
DOI 10.1007/978-3-642-48354-7_5
Open this paper in CoChat — free account

Abstract

This paper summarizes the current state of the art and recent trends in software engineering economics. It provides an overview of economic analysis techniques and their applicability to software engineering and management. It surveys the field of software cost estimation, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.

Overview

Integrity signals

Registry

Crossref · 10.1007/978-3-642-48354-7_5

Cites

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

No references could be resolved yet.

Research works printed but not linked: 52

  1. T. K. Abdel-Hamid and S. E. Madnick, “A model of software project management dynamics,” in Proc. IEEE COM PS AC 82, Nov. 1982, pp. 539–554.
  2. A. J. Albrecht, “Measuring Application Development Productivity,” in SHARE-GUIDE, 1979, pp. 83-92.
  3. J. D. Aron, “Estimating resources for large programming systems.” NATO Sci. Committee, Rome, Italy, Oct. 1969.
  4. J. J. Bailey and V. R. Basili, “A meta-model for software development resource expenditures,” in Proc. 5th Int. Conf. Software Eng., IEEE/ACM/NBS, Mar. 1981, pp. 107-116.
  5. V. R. Basili, “Tutorial on models and metrics for software and engineering,” IEEE Cat. EHO-167-7, Oct. 1980.
  6. L. A. Belady and M. M. Lehman, “Characteristics of large systems,” in Research Directions in Software Technology, P. Wegner, Ed. Cambridge, MA: MIT Press, 1979.
  7. H. D. Benington, “Production of large computer programs,” in Proc. ONR Symp. Advanced Programming Methods for Digital Computers, June 1956, pp. 15-27.
  8. B. W. Boehm, “Software and its impact: A quantitative assessment,” Datamation, pp. 48-59, May 1973.
  9. B. W. Boehm, Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.
  10. B. W. Boehm, J. F. Elwell, A. B. Pyster, E. D. Stuckle, and R. D. Williams, “The TRW software productivity system,” in Proc. IEEE 6th Int. Conf Software Eng., Sept. 1982.
  11. B. W. Boehm, T. E. Gray, and T. Seewaldt, “Prototyping vs. specifying: A multi-project experiment,” IEEE Trans. Software Eng., to be published.
  12. R. N. Britcher and J. E. Gaffney, “Estimates of software size from state machine designs,” in Proc. NASA-Goddard Software Eng. Workshop, Dec. 1982.
  13. N. S. Coulter, “Software science and cognitive psychology,” IEEE Trans. Software Eng., pp. 166-171, Mar. 1983. · DOI
  14. T. DeMarco, Controlling Software Projects. New York: Your-don, 1982.
  15. H. F. Dircks, “SOFCOST: Grumman’s software cost eliminating model,” in IEEE NAECON 1981, May 1981.
  16. L. E. Druffel, “Strategy for DoD software initiative,” RADC/ DACS, Griffiss AFB, NY, Oct. 1982.
  17. L. C. Duclos, “Simulation model for the life-cycle of a software product: A quality assurance approach,” Ph. D. dissertation, Dep. Industrial and Syst. Eng., Univ. Southern California, Dec. 1982.
  18. F. R. Freiman and R. D. Park, “PRICE software model—Version 3: An overview,” in Proc. IEEE-PINY Workshop on Quantitative Software Models, IEEE Cat. TH0067-9, Oct. 1979, pp. 32-41.
  19. R. Goldberg and H. Lorin, The Economics of Information Processing. New York: Wiley, 1982.
  20. M. H. Halstead, Elements of Software Science. New York: Elsevier, 1977.
  21. P. G. Hamer and G. D. Frewin, “M. H. Halstead’s software science’A critical examination,” in Proc. IEEE 6th Int. Conf. Software Eng., Sept. 1982, pp. 197-205.
  22. W. Harrison, K. Magel, R. Kluczney, and A. DeKock, “Applying software complexity metrics to program maintenance,” Computer, pp. 65-79, Sept. 1982. · DOI
  23. J. R. Herd, J. N. Postak, W. E. Russell, and K. R. Stewart, “Software cost estimation study—Study results,” Doty Associates, Inc., Rockville, MD, Final Tech. Rep. RADC-TR-77-220, vol. 1 (of two), June 1977. · DOI
  24. C. Houtz and T. Buschbach, “Review and analysis of conversion cost-estimating techniques,” GSA Federal Conversion Support Center, Falls Church, VA, Rep. GSA/FCSC-81/001, Mar. 1981.
  25. M. Itakura and A. Takayanagi, “A model for estimating program size and its evaluation,” in Proc. IEEE 6th Software Eng., Sept. 1982, pp. 104-109.
  26. R. W. Jensen, “An improved macrolevel software development resource estimation model,” in Proc. 5th ISPA Conf., Apr. 1983, pp. 88-92.
  27. R. W. Jensen and S. Lucas, “Sensitivity analysis of the Jensen software model,” in Proc. 5th ISPA Conf, Apr. 1983, pp. 384-389.
  28. B. A. Kitchenham, “Measures of programming complexity,” ICL Tech. J., pp. 298-316, May 1981.
  29. B. A. Kitchenham, “Systems evolution dynamics of VME/B,” ICL Tech. J., pp. 43-57, May 1982.
  30. W. W. Kuhn, “A software lifecycle case study using the PRICE model,” in Proc. IEEE NAECON, May 1982.
  31. M. J. Lawrence, “Programming methodology, organizational environment, and programming productivity,” J. Syst. Software, pp. 257-270, Sept. 1981. · DOI
  32. “An examination of evolution dynamics,” in Proc. IEEE 6th Int. Conf. Software Eng., Sept. 1982, pp. 188-196.
  33. M. M. Lehman, “Programs, life cycles, and laws of software evolution,” Proc. IEEE, pp. 1060-1076, Sept. 1980.
  34. R. D. Luce and H. Raiffa, Games and Decisions. New York: Wiley, 1957.
  35. T. J. McCabe, “A complexity measure,” IEEE Trans. Software Eng., pp. 308-320, Dec. 1976. · DOI · Paper page
  36. F. E. McGarry, “Measuring software development technology: What have we learned in six years,” in Proc. NASA-Goddard Software Eng. Workshop, Dec. 1982.
  37. E. A. Nelson, “Management handbook for the estimation of computer programming costs,” Syst. Develop. Corp., AD-A648750, Oct. 31, 1966. · DOI
  38. M. Okada and M. Azuma, “Software development estimation study—A model from CAD/CAM system development experiences,” in Proc. IEEE COMPSAC 82, Nov. 1982, pp. 555–564.
  39. M. Phister, Jr., “A model of the software development process,” J. Syst. Software, pp. 237-256, Sept. 1981. · DOI
  40. L. H. Putnam, “A general empirical solution to the macro software sizing and estimating problem,” IEEE Trans. Software Eng.t pp. 345-361, July 1978. · DOI
  41. L. H. Putnam and A. Pitzsimmons, "Estimating software costs," Datamation, pp. 189-198, Sept. 1979
  42. continued in Datamation, pp. 171-178, Oct. 1979 and pp. 137-140, Nov. 1979.
  43. L.H. Putnam, “The real economics of software development,” in The Economics of Information Processing, R. Goldberg and H. Lorin. New York: Wiley, 1982.
  44. V. Y. Shen, S. D. Conte, and H. E. Dunsmore, “Software science revisited: A critical analysis of the theory and its empirical support,” IEEE Trans. Software Eng., pp. 155-165, Mar. 1983. · DOI
  45. T. Sunohara, A. Takano, K. Uehara, and T. Ohkawa, “Program complexity measure for software development management,” in Proc. IEEE 5th Int. Conf. Software Eng., Mar. 1981, pp. 100-106.
  46. R. C. Tausworthe, “Staffing implications of software productivity models,” in Proc. 7th Annu. Software Eng. Workshop, NASA/Goddard, Greenbelt, MD, Dec. 1982.
  47. R. Thibodeau, “An evaluation of software cost estimating models,” General Res. Corp., Rep. T10-2670, Apr. 1981. · DOI
  48. C. E. Walston and C. P. Felix, “A method of programming measurement and estimation,” IBM Syst. J., vol. 16, no. I, pp. 54–73, 1977. · DOI
  49. G. F. Weinwurm, Ed., On the Management of Computer Programming. New York: Auerbach, 1970.
  50. G. M. Weinberg and E. L. Schulman, “Goals and performance in computer programming,” Human Factors, vol. 16, no. 1, pp. 70–77, 1974. · DOI
  51. J. D. Wiest and F. K. Levy, A Management Guide to PERT/CPM. Englewood Cliffs, NJ: Prentice-Hall, 1977.
  52. R. W. Wolverton, “The cost of developing large-scale software,” IEEE Trans. Compute pp. 615-636, June 1974. · DOI

Cited by

Sorted by citations

Metadata

Authors
Boehm, B. W.
Affiliations
TRW (United States) (US)
Corresponding author
Boehm, Barry W.
Venue
Pioneers and Their Contributions to Software Engineering
Publisher
Springer Berlin Heidelberg
Published
2001
Volume
SE-10
Issue
1
Pages
99-150
DOI
10.1007/978-3-642-48354-7_5
OpenAlex
W1557824269
Cited by
5,981
References
0
Citations by year
2026: 49 · 2025: 43 · 2024: 57 · 2023: 60 · 2022: 59 · 2021: 103 · 2020: 117 · 2019: 110 · 2018: 146 · 2017: 120 · 2016: 139 · 2015: 194 · 2014: 230 · 2013: 242 · 2012: 272
FWCI
112.24
Type
book chapter
Language
en
Open access
closed
Locations
  • Springer eBooks (publishedVersion)
  • IEEE Transactions on Software Engineering (publishedVersion)
  • CERN Document Server (European Organization for Nuclear Research) (submittedVersion)
  • Andalas University Repository (Andalas University) (submittedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Software › Software Reliability and Analysis Research
Keywords
software engineering economics, software cost estimation, software project management, research challenges

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