Re: Clean Object Class Design -- What is it?

From: Lee Fesperman <firstsql_at_ix.netcom.com>
Date: Fri, 27 Jul 2001 13:19:57 -0700
Message-ID: <3B61CCED.7B5F_at_ix.netcom.com>


Steve Wart wrote:
>
> "Lee Fesperman" <firstsql_at_ix.netcom.com> wrote in message
> news:3B61284C.1C50_at_ix.netcom.com..
> > Bill Cole wrote:
 

> > > My point being that the data in a Database is often used by *multiple*
> > > programs written in a variety of programming languages. Consequently
> > > the context of "data" in a shared repository (Database) has a
> > > different (and larger) set of design factors than "data" encapsulated
> > > in a single application object instance (program).
> >
> > Agreed. I've said it before. The modeling problems of a 'shared' database
 are quite
> > large, and I don't see that OO techniques have the power to be used in
 organizing such a
> > database.
>
> But the problem with *any* model of the world is that it is purely
> subjective. Whether it is a departmental model, an enterprise model or an
> industry model, the shortcomings will be proportional to the ambition of the
> team.

Well, it is a 'model', not the real thing. Anyway, I have to disagree with you. Relational techniques for modelling are not 'purely' subjective, they have a very sound theoretical basis. Obviously, there are subjective aspects, but the sound fundamentals can carry you pretty far. OO modelling techniques, OTOH, are very close to 'purely subjective'.

-- 
Lee Fesperman, FFE Software, Inc. (http://www.firstsql.com)
===================================================================
* Check out Database Debunkings (http://www.firstsql.com/dbdebunk/)
* "The Forum Where Database Matters Are Set Straight"
Received on Fri Jul 27 2001 - 22:19:57 CEST

Original text of this message