Re: Modelling Considered Harmful

From: Kenneth Downs <knode.wants.this_at_see.sigblock>
Date: Wed, 27 Apr 2005 09:33:58 -0400
Message-Id: <o1h4k2-94q.ln1@pluto.downsfam.net>

David Cressey wrote:

>
> "Kenneth Downs" <knode.wants.this_at_see.sigblock> wrote in message
> news:4v4mj2-92l.ln1_at_pluto.downsfam.net...

>> I wonder if anybody would care to dispute the thesis that use of the term
>> "modelling" with regard to databases does more harm than good.

>
> [major snip]
>

>>  Nor is the meta-data a model.  The meta-data for the employees table
>>  does
>> not model the company, it specifies what information must be recorded to
>> conform with law and policy.  since meta-data is data, the meta-data is a
>> record of what must be recorded.  Still no model.
>>
>> Agree?  Disagree?

>
> I disagree. First off, my usage of the term "modelling" with regard to
> databases does NOT address the issue of whether or not the data in the
> database is a "model of reality". I don't even want to tackle that one
> just yet.

It seems you don't disagree, but use the term modelling to describe the attempt to design the database. Works for me....

>
> The value of modelling goes down, as it becomes cheaper to build a
> database. But the model is still useful, in some ways, that the real thing
> is less
> useful for. Specifically, a model of a database is easier tounderstand
> than
> a database itself. Provided that understanding is a trustworthy guide to
> the actual database, there is value in that.

This would be an interesting discussion, the value of a model vs. a working sytem. We have made every attempt to bring the price of creating a db + system to zero (the ideal), so that we can jump from brainstorming to demo. Customers seem to greatly appreciate this, and find it very easy to work through the system and evaluate it as a real thing.

-- 
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@(Sec)ure(Dat)a(.com)

Received on Wed Apr 27 2005 - 08:33:58 CDT