Hostname: page-component-cd9895bd7-hc48f Total loading time: 0 Render date: 2024-12-29T06:06:36.141Z Has data issue: false hasContentIssue false
  • English
  • Français

A formal ontological perspective on the behaviors and functions of technical artifacts

Published online by Cambridge University Press:  16 December 2008

Stefano Borgo ,
Massimiliano Carrara ,
Pawel Garbacz  and
Pieter E. Vermaas
Stefano Borgo
Affiliation:
Laboratory for Applied Ontology, ISTC-CNR, Trento, Italy
Massimiliano Carrara
Affiliation:
Department of Philosophy, University of Padua, Padua, Italy
Pawel Garbacz
Affiliation:
Department of Philosophy, John Paul II Catholic University, Lublin, Poland
Pieter E. Vermaas
Affiliation:
Department of Philosophy, Delft University of Technology, Delft, The Netherlands
Get access Rights & Permissions [Opens in a new window]

Abstract

In this paper we present a formal characterization of the engineering concepts of behavior and function of technical artifacts. We capture the meanings that engineers attach to these concepts by formalizing, within the formal ontology DOLCE, the five meanings of artifact behavior and the two meanings of function that Chandrasekaran and Josephson identified in 2000 within the functional representation approach. We begin our formalization by reserving the term “behavior” of a technical artifact as “the specific way in which the artifact occurs in an event.” This general notion is characterized formally, and used to provide definitions of actual behaviors of artifacts, and the physically possible and physically impossible behaviors that rational agents believe that artifacts have. We also define several other notions, for example, input and output behaviors of artifacts, and then show that these ontologically characterized concepts give a general framework in which Chandrasekaran and Josephson's meanings of behavior can be explicitly formalized. Finally we show how Chandrasekaran and Josephson's two meanings of artifact functions, namely, device-centric and environment-centric functions, can be captured in DOLCE via the concepts of behavioral constraint and mode of deployment of an artifact. A more general goal of this work is to show that foundational ontologies are suited to the engineering domain: they can facilitate information sharing and exchange in the various engineering domains by providing concept structures and clarifications that make explicit and precise important engineering notions. The meanings of the terms “behavior” and “function” in domains like designing, redesigning, reverse engineering, product architecture, and engineering knowledge bases are often ambiguous or overloaded. Our results show that foundational ontologies can accommodate the variety of denotations these terms have and can explain their relationships.

Keywords

BehaviorEngineeringFormal OntologyFunctionTechnical Artifact
Type
Research Article
Information
AI EDAM , Volume 23 , Issue 1: Developing and Using Engineering Ontologies , February 2009 , pp. 3 - 21
Copyright
Copyright © Cambridge University Press 2009

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

References

REFERENCES

Bhatta, S., & Goel, A. (2002). Design patterns and creative design. In Engineering Design Synthesis (Chakrabarti, A., Ed.) pp. 271–284. Berlin: Springer.CrossRefGoogle Scholar
Bhatta, S., Goel, A., & Prabhakar, S. (1994). Innovation in analogical design: a model-based approach. Artificial Intelligence in Design—1994 (Gero, J., & Sudweeks, F., Eds.), pp. 57–74. Dordrecht: Kluwer.Google Scholar
Borgo, S. (2007). How formal ontology can help civil engineers. In Ontologies for Urban Development (Teller, J., Lee, J., & Roussey, C., Eds.), pp. 37–45. Berlin: Springer.CrossRefGoogle Scholar
Borgo, S., Carrara, M., Vermaas, P.E., & Garbacz, P. (2006). Behavior of a technical artifact: an ontological perspective in engineering. Formal Ontology in Information Systems: Proc. 4th Int. Conf. (FOIS 2006). Frontiers in Artificial Intelligence and Applications (Bennett, B., & Fellbaum, C., Eds.), Vol. 150, pp. 214–225. Amsterdam: IOS.Google Scholar
Borgo, S., & Leitao, P. (2007). Foundations for a core ontology of manufacturing. In Ontologies: A Handbook of Principles, Concepts and Applications in Information Systems. Integrated Series in Information Systems (Kishore, R., Ramesh, R., & Sharman, R., Eds.), Vol. 14, pp. 752–776. Dordrecht: Springer.CrossRefGoogle Scholar
Borgo, S., & Vieu, L. (in press). Artefacts in formal ontology. In Handbook of Philosophy of Technology and Engineering Science. Amsterdam: Elsevier.Google Scholar
Bryant, C.R., McAdams, D.A., Stone, R.B., Kurtoglu, T., & Campbell, M.I. (2006). A validation study of an automated concept generator design tool. Proc. 2006 ASME IDETC/CIE Conf., Paper No. DETC2006-99489, Philadelphia, PA, September 10–13.CrossRefGoogle Scholar
Bucciarelli, L.L. (1994). Designing Engineers. Cambridge, MA: MIT.Google Scholar
Chandrasekaran, B. (1994). Functional representation and causal processes. Advances in Computers 38, 73–143.CrossRefGoogle Scholar
Chandrasekaran, B. (2005). Representing function. Artificial Intelligence for Engineering Design, Analysis and Manufacturing 19(1), 65–74.CrossRefGoogle Scholar
Chandrasekaran, B., & Josephson, J.R. (2000). Function in device representation. Engineering With Computers 16(3/4), 162–177.CrossRefGoogle Scholar
Chandrasekaran, B., Josephson, R., & Benjamins, V. (1999). What are ontologies, and why do we need them? IEEE Intelligent Systems 14, 20–26.CrossRefGoogle Scholar
Chittaro, L., & Kumar, A.N. (1998). Reasoning about function and its applications to engineering. Artificial Intelligence in Engineering 12, 331–336.CrossRefGoogle Scholar
Dretske, F. (1988). Explaining Behavior. Cambridge, MA: MIT.Google Scholar
Fine, K. (1995). Ontological dependence. Proceedings of the Aristotelian Society 95, pp. 269–290.CrossRefGoogle Scholar
Garbacz, P. (2006). A formal model of functional decomposition. Proc. 2006 ASME IDETC/CIE Conf., Paper No. DETC2006-99097, Philadelphia, PA, September 10–13.CrossRefGoogle Scholar
Gero, J.S. (1990). A knowledge representation schema for design. AI Magazine 11(4), 26–36.Google Scholar
Gero, J.S., & Kannengiesser, U. (2004). The situated function–behavior–structure framework. Design Studies 25, 373–391.CrossRefGoogle Scholar
Goel, A. (1991). A model-based approach to case adaptation. Proc. 13th Annual Cognitive Science Conf., pp. 143–148. Mahwah, NJ: Erlbaum.Google Scholar
Hirtz, J., Stone, R.B., McAdams, D.A., Szykman, S., & Wood, K.L. (2002). A functional basis for engineering design: reconciling and evolving previous efforts. Research in Engineering Design 13, 65–82.CrossRefGoogle Scholar
Kitamura, Y., Koji, Y., & Mizoguchi, R. (2005/2006). An ontological model of device function: industrial deployment and lessons learned. Applied Ontology 1, 237–262.Google Scholar
Kitamura, Y., Sano, T., Nambo, K., & Mizoguchi, R. (2002). A functional concept ontology and its application to automatic identification of functional structures. Advanced Engineering Informatics 16(2), 145–163.CrossRefGoogle Scholar
Lehmann, J., Borgo, S., Masolo, C., & Gangemi, A. (2004). Causality and causation in dolce. Proc. 3rd Int. Conf. FOIS 2004 (Varzi, A.C., & Vieu, L., Eds.), pp. 273–284. Amsterdam: IOS.Google Scholar
Lemmon, E.J. (1965). Beginning Logic. Indianapolis, IN: Hackett Publishing Company.Google Scholar
Masolo, C., Borgo, S., Gangemi, A., Guarino, N., & Oltramari, A. (2003). Wonderweb deliverabled18. Accessed at http://www.loa-cnr.it/Papers/D18.pdfGoogle Scholar
Mizoguchi, R., Sunagawa, E., Kozaki, K., & Kitamura, Y. (2007). Model of roles within an ontology development tool: Hozo. Journal of Applied Ontology 2, 159–179.Google Scholar
Pahl, G., & Beitz, W. (1998). Engineering Design. Berlin: Springer.Google Scholar
Rosenman, M.A., & Gero, J.S. (1998). Purpose and function in design. Design Studies 19, 161–186.CrossRefGoogle Scholar
Simons, P. (1987). Parts: A Study in Ontology. Oxford: Clarendon.Google Scholar
Staab, S., & Studer, R. (2004). Handbook of Ontologies; International Handbooks on Information Systems. Berlin: Springer.Google Scholar
Stone, R.B., & Wood, K. (2000). Development of a functional basis for design. Journal of Mechanical Design 122(4), 359–276.CrossRefGoogle Scholar
Thomasson, A. (1999). Fiction and Metaphysics. Cambridge: Cambridge University Press.Google Scholar
Umeda, Y., Ishii, M., Yoshioka, M., Shimomura, Y., & Tomiyama, T. (1996). Supporting conceptual design based on the function–behavior–state modeler. Artificial Intelligence for Engineering Design, Analysis and Manufacturing 10, 275–288.CrossRefGoogle Scholar
Umeda, Y., Kohdoh, S., Shimomura, Y., & Tomiyama, T. (2005). Development of design methodology for upgradable products based on function–behavior–state modeling. Artificial Intelligence for Engineering Design, Analysis and Manufacturing 19, 161–182.CrossRefGoogle Scholar
Umeda, Y., & Tomiyama, T. (1997). Functional reasoning in design. IEEE Expert: Intelligent Systems and Their Applications 12, 42–48.CrossRefGoogle Scholar
Vermaas, P.E. (2007). The functional modelling account of Stone and Wood: some critical remarks. Proc. 16th Int. Conf. Engineering Design, Design for Society: Knowledge, Innovation and Sustainability, Abstract, Paris, 28–30 August, pp. 851–852, full paper on accompanying CD, Paris: Ecole Centrale.Google Scholar
Vermaas, P.E., & Dorst, K. (2007). On the conceptual framework of John Gero's FBS-model and the prescriptive aims of design methodology. Design Studies 28, 133–157.CrossRefGoogle Scholar