The push to make software engineering respectable
Abstract
A recognized engineering profession must have an established body of knowledge and skill that its practitioners understand and use consistently. After 30 years, there is still a wide gap between the best and the typical software engineering practices. To close this gap, we need a deeper partnership among industry, academia, and professional societies. We have spent some time considering the reasons for SE's immaturity. All of us are heavily involved in both industry and academia and have been active in professional societies that aim to promote SE as a profession. Promotion efforts are by no means limited to the US, but because our experience is primarily with US activities, that is our focus in this article. Our main goal is to explore, from a multifaceted perspective, why we are where we are now and how we can move forward.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
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?
While software engineering degrees can now be accredited, a license is not required to practice, with some national exceptions.
“While software engineering degrees can now be accredited, a license is not required to practice, 71 with some national exceptions.”
From Principles alone cannot guarantee ethical AI (2019) · cites this paper as [73]
Cites
Prospects for an engineering discipline of software
Shaw, M. (1990) · IEEE Software · doi:10.1109/52.60586 · Cited by 346 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
Principles alone cannot guarantee ethical AI
Mittelstadt, B. (2019) · Nature Machine Intelligence · doi:10.1038/s42256-019-0114-4 · Cited by 1,886 · see citing works
AI Ethics – Too Principled to Fail?
Mittelstadt, B. (2019) · SSRN Electronic Journal · doi:10.2139/ssrn.3391293 · Cited by 82 · see citing works
- Authors
- Pour, G., Griss, M. L., & Lutz, M.
- Affiliations
- San Jose State University (US)
- Hewlett-Packard (United States) (US)
- Rochester Institute of Technology (US)
- ORCID
- Griss, M.L.
- Venue
- Computer
- Published
- 2000-05
- Volume
- 33
- Issue
- 5
- Pages
- 35-43
- ISSN
- 0018-9162 (ISSN-L)
- OpenAlex
- W2020235753
- Cited by
- 53
- References
- 1
- Citations by year
- 2020: 1 · 2019: 3 · 2018: 2 · 2016: 1 · 2015: 1 · 2014: 1 · 2013: 4 · 2012: 3
- FWCI
- 11.68
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Computer (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
- Physical Sciences › Engineering › Media Technology › Engineering Education and Curriculum Development
- Keywords
- software engineering profession, software engineering maturity, university-industry collaboration, professional associations
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
