On malfunctioning software

Synthese 192 (4):1199-1220 (2015)
Authors
Giuseppe Primiero
University of Milan
Luciano Floridi
Oxford University
Nir Fresco
Ben-Gurion University of the Negev
Abstract
Artefacts 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.
Keywords No keywords specified (fix it)
Categories (categorize this paper)
ISBN(s)
DOI 10.1007/s11229-014-0610-3
Options
Edit this record
Mark as duplicate
Export citation
Find it on Scholar
Request removal from index
Revision history

Download options

Our Archive


Upload a copy of this paper     Check publisher's policy     Papers currently archived: 35,527
External links

Setup an account with your affiliations in order to access resources via your University's proxy server
Configure custom proxy (use this if your affiliation does not provide a proxy)
Through your library

References found in this work BETA

The Philosophy of Information.Luciano Floridi - 2011 - Oxford University Press.
In Defense of Proper Functions.Ruth Garrett Millikan - 1989 - Philosophy of Science 56 (June):288-302.
Software is an Abstract Artifact.Nurbay Irmak - 2012 - Grazer Philosophische Studien 86 (1):55-72.
Misrepresenting and Malfunctioning.Karen Neander - 1995 - Philosophical Studies 79 (2):109-41.

View all 28 references / Add more references

Citations of this work BETA

Why Separation Logic Works.David Pym, Jonathan M. Spring & Peter O’Hearn - forthcoming - Philosophy and Technology:1-34.

View all 9 citations / Add more citations

Similar books and articles

The Normativity of Artefacts.Maarten Franssen - 2006 - Studies in History and Philosophy of Science Part A 37 (1):42-57.
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.
What is Software?Peter Suber - 1988 - Journal of Speculative Philosophy 2 (2):89-119.
Software is an Abstract Artifact.Nurbay Irmak - 2012 - Grazer Philosophische Studien 86 (1):55-72.
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.
The Freedoms of Software and its Ethical Uses.Samir Chopra & Scott Dexter - 2009 - Ethics and Information Technology 11 (4):287-297.

Analytics

Added to PP index
2015-05-08

Total downloads
98 ( #64,740 of 2,287,534 )

Recent downloads (6 months)
2 ( #234,455 of 2,287,534 )

How can I increase my downloads?

Monthly downloads

My notes

Sign in to use this feature