IDEAS home Printed from https://ideas.repec.org/a/spr/infosf/v3y2001i2d10.1023_a1011460711754.html
   My bibliography  Save this article

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

Author

Listed:
  • E. Marcos

    (Rey Juan Carlos University)

  • A. Marcos

    (Plaza de la Universidad)

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”.

Suggested Citation

  • E. Marcos & A. Marcos, 2001. "A Philosophical Approach to the Concept of Data Model: Is a Data Model, in Fact, a Model?," Information Systems Frontiers, Springer, vol. 3(2), pages 267-274, June.
    • Handle: RePEc:spr:infosf:v:3:y:2001:i:2:d:10.1023_a:1011460711754
    DOI: 10.1023/A:1011460711754
    as

    Download full text from publisher

    File URL: http://link.springer.com/10.1023/A:1011460711754
    File Function: Abstract
    Download Restriction: Access to the full text of the articles in this series is restricted.
    File URL: https://libkey.io/10.1023/A:1011460711754?utm_source=ideas
    LibKey link: if access is restricted and if your library uses this service, LibKey will redirect you to where you can use your library subscription to access this item
    ---><---

    As the access to this document is restricted, you may want to search for a different version of it.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:infosf:v:3:y:2001:i:2:d:10.1023_a:1011460711754. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.