Synthese 192 (4):1199-1220 (2015)
AbstractArtefacts do not always do what they are supposed to, due to a variety of reasons, including manufacturing problems, poor maintenance, and normal wear-and-tear. Since software is an artefact, it should be subject to malfunctioning in the same sense in which other artefacts can malfunction. Yet, whether software is on a par with other artefacts when it comes to malfunctioning crucially depends on the abstraction used in the analysis. We distinguish between “negative” and “positive” notions of malfunction. A negative malfunction, or dysfunction, occurs when an artefact token either does not or cannot do what it is supposed to. A positive malfunction, or misfunction, occurs when an artefact token may do what is supposed to but, at least occasionally, it also yields some unintended and undesirable effects. We argue that software, understood as type, may misfunction in some limited sense, but cannot dysfunction. Accordingly, one should distinguish software from other technical artefacts, in view of their design that makes dysfunction impossible for the former, while possible for the latter.
Similar books and articles
A New Logic of Technical Malfunction.Bjørn Jespersen & Massimiliano Carrara - 2013 - Studia Logica 101 (3):547-581.
Two Conceptions of Technical Malfunction.Bjørn Jespersen & Massimiliano Carrara - 2011 - Theoria 77 (2):117-138.
A Philosophy of Maintenance? Engaging with the Concept of Software.David Love - 2007 - Philosophy of Management 6 (2):27-30.
Ethics and the Practice of Software Design.Matteo Turilli - 2008 - In P. Brey, A. Briggle & K. Waelbers (eds.), Current Issues in Computing and Philosophy. IOS Press.
Toward a profile of student software piraters.Ronald R. Sims, Hsing K. Cheng & Hildy Teegen - 1996 - Journal of Business Ethics 15 (8):839 - 849.
Software Theory: A Cultural and Philosophical Study.Federica Frabetti - 2014 - Rowman & Littlefield International.
An Evaluation of Agile Software Methodology Techniques.Anuradha Sutharshan & Stanislaw Maj - unknown
Free software and the economics of information justice.S. Chopra & S. Dexter - 2011 - Ethics and Information Technology 13 (3):173-184.
A bundle of software rights and duties.David M. Douglas - 2011 - Ethics and Information Technology 13 (3):185-197.
Not all codes are created equal: The software engineering code of ethics, a success story. [REVIEW]Don Gotterbarn - 1999 - Journal of Business Ethics 22 (1):81 - 89.
The freedoms of software and its ethical uses.Samir Chopra & Scott Dexter - 2009 - Ethics and Information Technology 11 (4):287-297.
Added to PP
Historical graph of downloads
Citations of this work
The ethics of algorithms: mapping the debate.Brent Mittelstadt, Patrick Allo, Mariarosaria Taddeo, Sandra Wachter & Luciano Floridi - 2016 - Big Data and Society 3 (2).
Can we trust Big Data? Applying philosophy of science to software.John Symons & Ramón Alvarado - 2016 - Big Data and Society 3 (2).
Why There is no General Solution to the Problem of Software Verification.John Symons & Jack J. Horner - 2020 - Foundations of Science 25 (3):541-557.
Why There is no General Solution to the Problem of Software Verification.John Symons & Jack K. Horner - 2020 - Foundations of Science 25 (3):541-557.
References found in this work
In defense of proper functions.Ruth Garrett Millikan - 1989 - Philosophy of Science 56 (June):288-302.
Teleological theories of mental content.Peter Schulte & Karen Neander - 2022 - Stanford Encyclopedia of Philosophy.