How are Data Models like Metaphors?

In classical linguistics a metaphor is a figure of speech that explains one thing in terms of another. The cognitive linguist George Lakoff revolutionized contemporary linguistics when he proposed that metaphor is “an ontological mapping across conceptual domains. Metaphor is not just a matter of language, but of thought and reason. The language is secondary; the mapping is primary.” Lakoff (1980)

Data models are like metaphors because they map one domain onto another. In fact, the logical data model is mapped in two directions.

  1. We use the logical model going downward to design the physical database so that it can record significant facts about the operations of the enterprise. In this direction the data model is a metaphor for the physical model and database.
  2. We use the logical model going upward to map the complex ideas implicit in the logical model onto a simpler conceptual model. The conceptual model can then be used for system integration by helping to understand how one application or business area fits into the larger enterprise.

A model is a visual metaphor. Instead of using figurative language to explain one thing in terms of another it uses a combination of visual shapes, colors, captions, and relationship symbols to map data requirements onto the physical or conceptual domains.

It may sound strange to talk about visual metaphors but that’s only because we are still thinking of the classical definition of metaphor as a part of the figurative language of poetry and literature. In order to see just how common visual metaphors have become one need only look at examples from commercial advertising. Visual metaphors have become so common that the conceptual mapping is almost subconscious.

Consider the Heinz Ketchup Advertisement. The image of a ketchup bottle sliced up like a tomato clearly expresses the message that Heinz ketchup is as fresh as a tomato.

About Joe D

Joe Danielewicz spent 28 years at various business units of Motorola in data architecture, enterprise architecture and systems development. More recently Mr. Danielewicz was a Senior Data Architect at General Motors, Chandler, AZ. Joe Danielewicz is a past president of Phoenix chapter of DAMA.
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *