The DOI matches its Crossref record; 20 of the 20 references it cites were found in a registry or an index.
Prospects for an engineering discipline of software
Open accessAbstract
Although software engineering is not yet a true engineering discipline, it has the potential to become one. Older engineering fields are examined to ascertain the character that software engineering might have. The current state of software technology is discussed, covering information processing as an economic force, the growing role of software in critical applications, the maturity of development techniques, and the scientific basis for software engineering practice. Five basic steps that the software engineering profession must take to become a true engineering discipline are described. They are: understanding the nature of expertise, recognizing different ways to get information, encouraging routine practice, expecting professional specializations, and improving the coupling between science and commercial practice.>
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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
Perry's chemical engineers' handbook
Green, D. W., & Perry, R. H. (2008) · Choice Reviews Online · doi:10.5860/choice.45-4393 · Cited by 10,131
No Silver Bullet Essence and Accidents of Software Engineering
Brooks (1987) · Computer · doi:10.1109/mc.1987.1663532 · Cited by 3,281
Cultural Literacy: What Every American Needs to Know
Warnock, J. W., & Hirsch, E. D. (1987) · College Composition and Communication · doi:10.2307/357649 · Cited by 2,324
Marks' standard handbook for mechanical engineers
Avallone, E. A., Baumeister, T., Sadegh, A. M., & Marks, L. S. (2000) · Choice Reviews Online · doi:10.5860/choice.37-6297 · Cited by 919
Boehm (1976) · IEEE Transactions on Computers · doi:10.1109/tc.1976.1674590 · Cited by 545
The Existential Pleasures of Engineering
Watson, S. R., & Florman, S. C. (1976) · Technology and Culture · doi:10.2307/3103538 · Cited by 319
Software manual for the elementary functions
(1981) · Computer Languages · doi:10.1016/0096-0551(81)90076-x · Cited by 219
Education for computing professionals
Parnas, D. L. (1990) · Computer · doi:10.1109/2.48796 · Cited by 138
Grand challenges to computational science
Wilson, K. G. (1989) · Future Generation Computer Systems · doi:10.1016/0167-739x(89)90038-1 · Cited by 70
A Social History of Engineering
Armytage, W. H. G. (2003) · The MIT Press eBooks · doi:10.7551/mitpress/6299.001.0001 · Cited by 59
Foundations and grand challenges of artificial intelligence
Reddy, R. (1988) · doi:10.1609/aimag.v9i4.950 · Cited by 53
Martin, W. A. (1971) · ACM Computing Surveys · doi:10.1145/356593.356594 · Cited by 49
Scaling Up: A Research Agenda for Software Engineering
Traub, J. F. (1989) · Medical Entomology and Zoology · Cited by 47
DoD Related Software Technology Requirements, Practices, and Prospects for the Future
Becker, L., Marmor-Squires, A., Martin, R. J., & Nash, S. H. (1984) · Cited by 37
A History of Civil Engineering: An Outline from Ancient to Modern Times
Collins, P., & Strauβ, H. (1963) · Journal of Architectural Education (1947-1974) · doi:10.2307/1423870 · Cited by 30
Engineering and Western civilization
Finch, J. K. (1951) · Medical Entomology and Zoology · Cited by 29
History of Chemical Engineering
(1981) · Chemical & Engineering News · doi:10.1021/cen-v059n050.p018 · Cited by 19
Grand challenges to computation science
Levin, E. (1989) · Communications of the ACM · doi:10.1145/76380.76385 · Cited by 16
The Origins of Chemical Engineering
Antwerpen, F. J. V. (1980) · Advances in chemistry series · doi:10.1021/ba-1980-0190.ch001 · Cited by 15
What a Software Engineer Needs to Know: 1. Program Vocabulary
Shaw, M., Giuse, D. A., & Reddy, R. (1989) · doi:10.21236/ada219064 · Cited by 2
Self-citation
Research works printed but not linked: 4
- 1990, Keeping the US Computer Industry Competitive
- 1989, Engineering and the Advancement of Human Welfare 10 Outstanding Achievements 1964-1989
- dijkstra, 1989, On the Cruelty of Really Teaching Computing Science, Comm ACM, 1,398
- 1969, Software Engineering Report on a Conference Sponsored by the NATO Science Committee Gartnisch Germany 1968
Cited by
Sorted by citations
Nuseibeh, B., & Easterbrook, S. (2000) · Future of Software Engineering (FOSE) · doi:10.1145/336512.336523 · Cited by 1,836
Automated Reasoning on Feature Models
Benavides, D., Trinidad, P., & Ruiz–Cortés, A. (2005) · Notes on numerical fluid mechanics and multidisciplinary design · doi:10.1007/11431855_34 · Cited by 631
Reusing software: issues and research directions
Mili, H., Mili, F., & Mili, A. (1995) · IEEE Transactions on Software Engineering · doi:10.1109/32.391379 · Cited by 557
Research in software engineering: an analysis of the literature
Glass, R. L., Vessey, I., & Ramesh, V. (2002) · Information and Software Technology · doi:10.1016/s0950-5849(02)00049-6 · Cited by 391
Davis, G. B., Gorgone, J. T., Couger, J. D., Feinstein, D. L., & Longenecker, H. E. (1996) · ACM SIGMIS Database the DATABASE for Advances in Information Systems · doi:10.1145/511965.512222 · Cited by 389
Metadata
- Authors
- Shaw, M.
- Affiliations
- Carnegie Mellon University (US)
- Corresponding author
- Shaw, M.
- ORCID
- Shaw, M.
- Venue
- IEEE Software
- Published
- 1990-11
- Volume
- 7
- Issue
- 6
- Pages
- 15-24
- ISSN
- 0740-7459 (ISSN-L)
- 1937-4194
- OpenAlex
- W2122253789
- Cited by
- 346
- References
- 20
- Citations by year
- 2026: 2 · 2025: 3 · 2024: 11 · 2023: 3 · 2022: 5 · 2021: 8 · 2020: 7 · 2019: 6 · 2018: 9 · 2017: 5 · 2016: 12 · 2015: 5 · 2014: 9 · 2013: 8 · 2012: 16
- FWCI
- 39.50
- Type
- journal article
- Language
- en
- Open access
- green
- figshare.com
- Licence
- Locations
- IEEE Software (publishedVersion)
- Figshare (submittedVersion, cc-by)
- KiltHub Repository (submittedVersion)
- KiltHub Repository
- Funders
- U.S. Department of Defense
- Defense Advanced Research Projects Agency
- U.S. Air Force
- Advanced Research Projects Agency
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Engineering › Safety, Risk, Reliability and Quality › Safety Systems Engineering in Autonomy
- Keywords
- software engineering profession, software development maturity, professional specialization, software engineering practices
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
