A Philosophical Approach to the Concept of Data Model: Is a Data Model, in Fact, a Model?

  • Authors:
  • E. Marcos;A. Marcos

  • Affiliations:
  • Department of Experimental Sciences and Engineering, Rey Juan Carlos University, C/Tulipán s/n, 28933 MOSTOLES, Madrid, Spain. cuca@escet.urjc.es;Department of Philosophy, Valladolid University, Plaza de la Universidad, 147002-Valladolid, Spain. amarcos@fyl.uva.es

  • Venue:
  • Information Systems Frontiers
  • Year:
  • 2001

Quantified Score

Hi-index 0.00

Visualization

Abstract

The design of the database is crucial to the process of designing almost any Information System (IS) and involves two clearly identifiable key concepts: schema and data model, the latter allowing us to define the former. Nevertheless, the term “model” is commonly applied indistinctly to both, the confusion arising from the fact that in Software Engineering (SE), unlike in formal or empirical sciences, the notion of “model” has a double meaning of which we are not always aware. If we take our idea of “model” directly from empirical sciences, then the schema of a database would actually be a model, whereas the data model would be a set of tools allowing us to define such a schema.The present paper discusses the meaning of “model” in the area of Software Engineering from a philosophical point of view, an important topic for the confusion arising directly affects other debates where “model” is a key concept. We would also suggest that the need for a philosophical discussion on the concept of data model is a further argument in favour of institutionalizing a new area of knowledge, which could be called: “Philosophy of Engineering”.