Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!uunet!bellcore!towernet!taichi!haim
From: haim@taichi.uucp (24122-Haim Kilov(L028)m000)
Newsgroups: comp.object
Subject: Re: data modeling and ood
Message-ID: <1991Feb6.150817.25887@towernet.cc.bellcore.com>
Date: 6 Feb 91 15:08:17 GMT
References: <1991Jan28.1034.1193@canrem.uucp>
Sender: @towernet.cc.bellcore.com
Reply-To: haim@taichi.UUCP (24122-Haim Kilov)
Organization: Bellcore, Livingston, NJ
Lines: 21


The idea of object information modeling is great and has in fact been
used for some time. The generic object information modeling concepts
superficially look like extended ER ones, but differ in at least the
following manner:
- they are precisely defined
- they are implementation-independent (i.e., don't use attributes,
  normalization, and other relational concepts)
- they are not "CASE tool"-oriented
- they are extensible.

The definitions of these concepts are based on primitive (CRUD) behavior,
i.e., on operations jointly owned by an object and associated objects.
A paper about this approach will be presented at TOOLS'91 in Paris in March
("Generic information modeling concepts: a reusable component library"
by myself). We at Bellcore use this approach.

Hope this helps.

-Haim Kilov
haim@bcr.cc.bellcore.com