Path: utzoo!attcan!lsuc!canrem![michael.daly@canrem.uucp]
From: michael.daly@canrem.uucp (michael daly)
Newsgroups: comp.object
Subject: data modeling and ood
Message-ID: <1991Jan28.1034.1193@canrem.uucp>
Date: 29 Jan 91 03:02:08 GMT
Reply-To: "michael daly" <michael.daly@canrem.uucp>
Organization: Canada Remote Systems
Lines: 30

Some may complain that this is not an OO topic, but I feel it is.

I have not found any information on data modeling in any object oriented
design/analysis/programming textbook.  I have recently finished a
contract on the construction of an application for a mainframe using
object oriented design techniques.  It was coded in PL/I, with
programmers creating objects and (most of them) enforcing OO concepts
like encapsulation etc.  There were two concepts used by the architect
of this system that seem uncommon in OO environments - relational
objects and data modeling.

I don't want to discuss the relational objects (a solution to the
dilemma of OODB vs RDBMS?), but I am having a problem with data
modeling.  I joined the project after the data modeling was done and had
no direct exposure to the techniques.  I have a generic understanding of
the end result of data normalization, but don't know how to do it.  I
have been told that there is a "cookbook" approach that will result in a
reasonable data model (at least up to third normal form, I think).  This
approach can be specified in a few written pages.  Can anyone offer some
advice on this topic, especially in an object oriented environment?

+------------------------------------------------------------------+
|  Michael Daly      | Usenet:   michael.daly@canremote.uucp       |
|                    | Internet: michael.daly%canrem#lsuc.uucp     |
+------------------------------------------------------------------+
---
 ~ DeLuxe}ab #289 ~ 
--
Canada Remote Systems.  Toronto, Ontario
NorthAmeriNet Host