Abstract
In this chapter we assess the explanatory utility of ascriptions of technical functions by considering two explanation-seeking contexts that often figure in the philosophical literature on functions (and explanations). Applied to the technical domain, these are: (i) why was artifact x produced?, and (ii) why does artifact x not have the expected capacity to ϕ? We argue that function ascriptions are explanatorily irrelevant for the first explanation-seeking question, and are explanatorily relevant for the second one. We argue these points in terms of the desideratum that explanations should only list difference making factors.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
Notes
- 1.
- 2.
Note that this desideratum is different from the theory or model constraint of ‘simplicity’. When endorsing ‘simplicity’ a theorist or modeler may intentionally exclude reference to factors that make a difference to whether or not a phenomenon occurs. The constraint which we endorse here, requires that an agent should strive for describing all the factors that make a difference to whether or not a phenomenon occurs. Whether an agent succeeds in doing so is, of course, a different matter. Weisberg (2007) labels this constraint an “1-causal” representational ideal, and distinguishes it from the representational ideals of “simplicity” and “completeness”. The latter requires that an explanation should specify both difference making properties with respect to whether or not a phenomenon occurs, as well as the “higher order causal factors” that affect the precise manner in which the phenomenon occurs (cf. Weisberg 2007, p. 651).
- 3.
An astute reader may point out that (justified) function ascription could have played no role in answering the first explanation-seeking question since there was no physical artifact yet to which a designer could have ascribed a function to. Agreed, yet our answer is in keeping with the ICE theory: “The historical perspective required to ascribe ICE functions may be limited to the design process; it need not extend to earlier generations of artefacts. An artefact can therefore straightaway be ascribed the capacity for which designers selected it, even if the artefact is a completely novel one (the case of the first nuclear plant)” (Houkes and Vermaas 2010, p. 93) (our italics). In other words, the answer accords with the ICE theory. To be sure, we here take function ascriptions as answers to the explanation-seeking question under consideration to be ‘proper’ function ascriptions. Proper function ascriptions are discussed by Houkes and Vermaas (2010) against the backdrop of what they call ‘proper use plans’.
- 4.
An astute reader may also point out that regarding production, belief initially is sufficient and justified belief only becomes relevant in continuation of the production process. Again, agreed. However, justified belief is central to the ICE theory, both in the ascriptions of functions to technical artifacts, and in accommodating central desiderata put forward in the function literature, such as the proper-accidental function distinction, function ascription in innovative contexts, and the handling of malfunction statements. The underlying reason is that the ICE theory is a “normative rather than a descriptive perspective” on “justifiable function ascriptions” (Houkes and Vermaas 2010, p. 4). Given this perspective, the requirement of justified belief for explaining the production of an artifact is either a bullet one has to bite when adopting the ICE theory, or the ICE theory should be extended to also encompass a descriptive perspective in which ‘mere belief’ suffices for explaining the production of an artifact. Hence, our use of the term ‘justified’.
- 5.
We focus on those difference making factors that are part of the conceptual framework of the ICE theory, and do not consider other potential difference making factors, such as, say, the choice of materials for the computer mouse. Therefore, our labelling of the notion that explanations should specify difference-making factors as a desideratum (cf. note 3). That there are, in the explanatory context under consideration, other difference making factors does not affect the outcome of our comparison of the explanatory superiority of functional vis-à-vis teleological explanations.
- 6.
Note that the argumentation presented here is not to be confused with conceptual explication of the term ‘technical function’. On the ICE account, ‘technical function’ refers to a physical-chemical capacity. We here invoke the ICE function ascription machinery to construct two parallel explanations.
- 7.
Varieties of this general question-format are for instance: ‘why does component x function suboptimal?’ (cf. Otto and Wood 2001)?; ‘why is this unexpected and undesired behavior present?’; ‘which malfunction is responsible for the undesired behavior?’; ‘which components/module does not work as expected?’ (cf. Goel and Chandrasekaran 1989; Bell et al. 2007); ‘does the trigger of the function fail and/or its effect?’ (Bell et al. 2007).
- 8.
The explanation might also list some further ‘local details’ that enable understanding how specific features make a difference to a specific malfunction. For instance, oil leaking into the hot exhaust due to a rupture in the oil reservoir may cause a car to expel thick black smoke. One can imagine that some further details are relevant to understand this malfunction, say, the exhaust function of expelling (normal amounts of) smoke and the carburetor producing sparks, since sparking is a cause of both expulsion of normal and excess amounts of smoke. More on this ‘enrichment’ of malfunction explanations with specific mechanism details in Chap. 2.
- 9.
Malfunction explanations already require various assumptions about the structure of a system, of course: a lot of structural and behavioral knowledge is involved (cf. Goel and Chandrasekaran 1989; Bell et al. 2007). This knowledge serves as backdrop against which to assess which features are explanatorily relevant and thus get referred to in the function descriptions.
- 10.
Triggers are inputs for main or primary normal functions and provide ‘pointers’ to possible malfunctions (as will become clear later on). Triggers are thus different from ‘control functions’ which are intended to counteract unwanted disturbances and unwanted changes in engineering systems (cf. Lind 1994).
References
Bell, J., Snooke, N., & Price, C. (2005). Functional decomposition for interpretation of model based simulation. Proceedings of the 19 th International Workshop on Qualitative Reasoning, QR-05, 192–198.
Bell, J., Snooke, N., & Price, C. (2007). A language for functional interpretation of model based simulation. Advanced Engineering Informatics, 21, 398–409.
Bigelow, J., & Pargetter, R. (1987). Functions. Journal of Philosophy, 84, 181–196.
Couch, M. (2011). Mechanisms and constitutive relevance. Synthese, 183, 375–388.
Cummins, R. (1975). Functional analysis. Journal of Philosophy, 72, 741–765.
De Ridder, J. (2006). Mechanistic artefact explanation. Studies in History and Philosophy of Science, 37, 81–96.
De Winter, J. (2011). A pragmatic account of mechanistic artifact explanation. Studies in History and Philosophy of Science, 42(4), 602–609.
Goel. A., & Chandrasekaran, B. (1989). Functional representation of designs and redesign problem solving. Proceedings Eleventh International Joint Conference on Artificial Intelligence (IJCAI-89), Detroit, Michigan, August, 1989: 1388–1394.
Hawkins, P. G., & Woollons, D. J. (1998). Failure modes and effects analysis of complex engineering systems using functional models. Artificial Intelligence in Engineering, 12(4), 375–397.
Houkes, W. (2006). Knowledge of artifact functions. Studies in History and Philosophy of Science, 37, 102–113.
Houkes, W., & Meijers, A. (2006). The ontology of artefacts: the hard problem. Studies in History and Philosophy of Science, 37, 118–131.
Houkes, W., & Vermaas, P. E. (2010). Technical functions: On the use and design of artefacts. Dordrecht: Springer.
Houkes, W., Kroes, P., Meijers, A., & Vermaas, P. E. (2011). Dual-Nature and collectivist frameworks for technical artefacts: a constructive comparison. Studies in History and Philosophy of Science, 42, 198–2005.
Kroes, P. (2003). Screwdriver philosophy Searle’s analysis of technical functions. Techné, 6(3), 22–35.
Krohs, U. (2009). Functions as based on a concept of general design. Synthese, 166, 69–89.
Lind, M. (1994). Modeling goals and functions of complex industrial plants. Applied Artificial Intelligence, 8, 259–283.
Lipton, P. (1993). Making a difference. Philosophica, 51, 39–54.
McLaughlin, P. (2001). What functions explain. Cambridge: Cambridge University Press.
Millikan, R. (1989). In defense of proper functions. Philosophy of Science, 56, 288–302.
Neander, K. (1991). The teleological notion of “function”. Australasian Journal of Philosophy, 69, 454–468.
Otto, K. N., & Wood, K. L. (2001). Product design: Techniques in reverse engineering and new product development. Upper Saddle River NJ: Prentice Hall.
Preston, B. (1998). Why is a wing like a spoon? A pluralist theory of functions. Journal of Philosophy, 95, 215–254.
Price, C. J. (1998). Function-directed electrical design analysis. Artificial Intelligence in Engineering, 12(4), 445–456.
Searle, J. (1995). The construction of social reality. New Haven: Free Press.
Sembugamoorthy, V., & Chandrasekaran, B. (1986). Functional representation of devices and compilation of diagnostic problem-solving systems. In J. Kolodner & C.K. Riesbeck (Eds.), Experience, memory, and reasoning. Hillsdale, NJ: Lawrence Erlbaum Associates: 47–53.
Strevens, M. (2004). The causal and unification approaches to explanation unified—causally. Noûs, 38(1), 154–176.
Strevens, M. (2008). Depth: An account of scientific explanation. Harvard University Press.
van Eck, D., & Weber, E. (2014). Function ascription and explanation: Elaborating an explanatory utility desideratum for ascriptions of technical functions. Erkenntnis, 79, 1367–1389.
van Eck, D., & Weber, E. (2016). In defense of co-existing engineering meanings of function. Artificial Intelligence for Engineering Design, Analysis, and Manufacturing. Online first, doi:10.1017/S0890060416000172.
Vermaas, P. E. (2006). The physical connection: engineering function ascriptions to technical artefacts and their components. Studies in History and Philosophy of Science, 37, 62–75.
Vermaas, P. E., & Houkes, W. (2003). Ascribing functions to technical artefacts: A challenge to etiological accounts of functions. British Journal for the Philosophy of Science, 54, 261–289.
Weisberg, M. (2007). Three kinds of idealization. The Journal of Philosophy, 104(12), 639–659.
Wimsatt, W. C. (1972). Teleology and the logical structure of function statements. Studies in History and Philosophy of Science, 3, 1–80.
Woodward, J. (2003). Making things happen. Oxford: Oxford University Press.
Wouters, A. G. (2003). Four notions of biological function. Studies in History and Philosophy of Biology and Biomedical Science, 34, 633–668.
Wright, L. (1973). Functions. Philosophical Review, 82, 139–168.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2016 The Author(s)
About this chapter
Cite this chapter
van Eck, D., Weber, E. (2016). Assessing the Explanatory Relevance of Ascriptions of Technical Functions. In: The Philosophy of Science and Engineering Design. SpringerBriefs in Philosophy. Springer, Cham. https://doi.org/10.1007/978-3-319-35155-1_1
Download citation
DOI: https://doi.org/10.1007/978-3-319-35155-1_1
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-35154-4
Online ISBN: 978-3-319-35155-1
eBook Packages: Religion and PhilosophyPhilosophy and Religion (R0)