The software engineering discipline advocates an approach toward software development that is \u201csystematic, disciplined,\u201d and \u201cquantifiable\u201d [1]. However, it has long been recognised that software \u2013 both in its construction and operation \u2013 is more closely tied to the human- than to the physical world. An early articulation of the social aspects of software development can be found in reports of two working conferences held by the NATO Science Committee in 1968 and 1969 [2,3]. Within these two events, the term \u201csoftware engineering\u201d was chosen to distinguish software development activity from craft, in order to address a crisis in the quality of software: the weaknesses in its features, design, and performance, that were depicted by participants to lie in failings of the people who make it. One aim of the conferences was to solve the problem of human contribution by aligning software development toward theoretical and practical techniques that were closer to those in established, traditional forms of engineering.<\/p>\n
Given these proto-engineering origins and the complex narrative space that surrounds software engineering practice today, what is software developers\u2019 own understanding of who they are and the contributions they make to the design and construction of software?<\/p>\n
This project invites proposals for projects that provide an interdisciplinary examination of professional identity in software engineering that critically engages with depictions of the profession made within industry, media, and research.<\/p>\n
You should have an appreciation of qualitative research methods and an understanding of primary sources and internet-based research. A first degree in a Computing field is welcome, but a first degree in the Social Sciences or Humanities will also be considered. In both cases a postgraduate degree or professional experience in the relevant companion area is advised.<\/p>\n
[1] ISO\/IEC\/IEEE 24765:2017 Systems and Software Engineering – Vocabulary<\/p>\n
[2] P. Naur and B. Randell, \u2018Software Engineering\u2019, NATO, Garmisch, Germany, Oct. 1968. Accessed: May 01, 2025. [Online<\/a>].<\/p>\n [3] B. Randell and J. N. Buxton, \u2018Software Engineering Techniques\u2019, NATO, Rome, Italy, Oct. 1969. Accessed: May 01, 2025. [Online<\/a>].<\/p>\n