From: Austin Ziegler <austin@...>
Date: 2002-12-17T12:57:44+09:00
Subject: Re: [OT] RE: help -- persuade my boss to adopt ruby

On Mon, 16 Dec 2002 23:13:19 +0900, Russ Freeman wrote:
>> an object model is an *instance* of a data model for a particular
>> problem. A good data model, represents the data being modeled --
>> not the data being modeled for a particular problem.
> Interesting one although I disagree. :) I agree that an
> abstraction can have many "aspects", if you like, but to say one
> of them is primordal is not true. The data model is just the
> intersection of what all applications to date require, nothing
> more nothing less. When it comes to designing an object or data
> model, rules of nomalisation, etc. still apply.

Well, yes. But I do see the object model and the data model as
separate; an object model is useful only in the context of a single
program -- whereas the overall data model should be more general and
attempt to anticipate the value of the data outside of any single
program.

I also don't see anything in my career that would convince me that
many developers know anything *at all* about data modeling, and this
includes a lot of strong OO proponents.

-austin
-- Austin Ziegler, austin@halostatue.ca on 2002.12.16 at 22.53.12