Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!postnews.google.com!z34g2000cwc.googlegroups.com!not-for-mail
From: "dawn" <dawnwolthuis@gmail.com>
Newsgroups: comp.databases.theory
Subject: Re: Logical data design, Pick style
Date: 29 Mar 2006 17:25:58 -0800
Organization: http://groups.google.com
Lines: 43
Message-ID: <1143681957.996322.224150@z34g2000cwc.googlegroups.com>
References: <1143681886.781190.304170@u72g2000cwu.googlegroups.com>
NNTP-Posting-Host: 24.176.45.11
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1143681963 11485 127.0.0.1 (30 Mar 2006 01:26:03 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 30 Mar 2006 01:26:03 +0000 (UTC)
In-Reply-To: <1143681886.781190.304170@u72g2000cwu.googlegroups.com>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: z34g2000cwc.googlegroups.com; posting-host=24.176.45.11;
   posting-account=fLxfag0AAADzmFPc_IBdM-stGY4WCEYa
Xref: dp-news.maxwell.syr.edu comp.databases.theory:37656

Oops -- this was for cdp.  Sorry.  --dawn

dawn wrote:
> I'll be back in the office next week Tuesday, but while I'm online I
> thought I'd toss out a question.  I've done a little work on the
> following question, but have more to do and thought others might be
> interested in jumping in on this one:
>
> If you don't do logical data modeling relational model style, using
> 1NF, then how do you model the data?
>
> 1.  Entity-relationship models or the analogous UML diagrams are good
> for identifying and communicating conceptual data models.  The topic of
> conceptual modeling is bigger than this, but the focus of this question
> is the "logical data model" or "implementation data model."
>
> 2.  Take the conceptual model and look for strong entities -- those
> that exist independent of other entities.  Model those as files.
>
> 3.  Identify unique keys for these files.
>
> 4.  Identify some high level types for these files, including the old
> designations of master files, transaction/event files, and code files.
>
> 5.  Decide whether you will pour all code files together or use one
> code file for typical abbreviation-description tables (see a previous
> discussion on this topic a few months ago).
>
> 6.  Add in all properties for these entities as attributes/fields in
> these files.
>
> 7.  Add in foreign keys where appropriate as well as the redundant
> "return links"
>
> 8.  Look for functional dependencies and put it into Boyce-Codd normal
> form sans 1NF.
>
> I have a lot of other notes, but this should be good enough for a
> discussion starter, I hope. Your thoughts?  --dawn
>
> P.S.  Blog is at http://www.tincat-group.com/mewsings, latest entry is
> on MV NULLs.