Re: Relation or attribute and why
Date: Wed, 24 May 2006 18:24:22 GMT
Message-ID: <qx1dg.12442$A26.295405_at_ursa-nb00s0.nbnet.nb.ca>
David Cressey wrote:
> "dawn" <dawnwolthuis_at_gmail.com> wrote in message
> news:1148432908.908347.174660_at_j55g2000cwa.googlegroups.com...
>
>>Gene Wirchenko wrote:
>>
>>>On 23 May 2006 15:44:15 -0700, "dawn" <dawnwolthuis_at_gmail.com> wrote:
>>>
>>>
>>>>Gene Wirchenko wrote:
>>>>
>>>>>On 23 May 2006 13:44:29 -0700, "dawn" <dawnwolthuis_at_gmail.com> wrote:
>>>>>
>>>>>[snip]
>>>>>
>>>>>
>>>>>>In my example, the conceptual data model includes: name, firstName,
>>>>>>lastName with relationships such that name has-a firstName and name
>>>>>>has-a lastName.
>>>>>
>>>>> That is part of the logical model. The conceptual model is the
>>>>>business statement.
>>>>
>>>>The identification of name, lastName, firstName and the relationships
>>>>among these terms is not part of the business scope and definition, the
>>>>conceptual data model? What would the CDM include related to these
>>>>terms? I put everything that is conceptual and not directed to a
>>>>particular implementation model (such as the RM) in the CDM. Where do
>>>>you draw the (possibly fuzzy) line? --dawn
>>>
>>> Possibly fuzzy, but nonetheless.
>>>
>>> Conceptual might fit on a napkin: "We want an E-commerce Web site
>>>for selling our products. It has to be able to handle North America,
>>>but we plan to go international, so have the capability to add other
>>>languages, etc. easily without rewriting large chunks. We want
>>>someone able to complete an order quickly. Do not forget good
>>>security. OtherCorp recently had a bad situation, and they are taking
>>>a kicking. Now is our chance, if we do it right."
>>
>>Those are high level requirements, but not a conceptual data model.
>>Conceptual, yes; CDM, no. You need at least an ORM, ERD, or a cleaner
>>list of propositions related to these requirements, I would think.
David,
If you are going to interract with the self-aggrandizing ignorants, please, take the time to point out the most fundamental and profound points of their ignorance. Failing to do so only serves to reinforce and to spread the widespread ignorance and misconception in our industry.
>>> Logical gets into the details, but not the implementation.
>>
>>A typical use of the term would allow for a conceptual data model to go
>>from high level to detailed (in the end). [Although if a decision is
>>made earlier that the requirements have been captured sufficiently to
>>do flesh it out using common sense in a transition to an LDM, I can
>>live with some agility.]
See what I mean? Here the self-aggrandizing ignorant once again pretends that ignorant nonsense like 'conceptual data model' has meaning. Then she demonstrates profound ignorance and confusion between a logical design and a logical data model, among which one finds the relational data model, the network data model and the hierarchic data model, themselves.
The surest sign that Dawn is a crank is her ignorant parroting of fashion statements like 'agility'.
>>I once considered the LDM to be implementation-independent, but after
>>reading other definitions the logical data model appears to be data
>>model dependent to most who use the term. In that case, you would not
>>have the same logical data model for an RM implementation as an MV
>>implementation, for example.
Here, again, the self-aggrandizing ignorant shows her profound ignorance
regarding logical data models. The relational data model is, itself, a
logical data model. A logical data model is a formalism for the symbolic
manipulation of data. A specific set of base relations and views is not
a logical data model nor is a specific set of records and pointers.
Of course! A logical design depends on the logical data model one
targets! How could it not? The whole point of a logical design is to
describe the represention of some subset of the information in a form
suitable for symbolic manipulation, which necessitates one represent the
data according to the structures and operations of the formal system. Duh!
See the trap? By failing to recognize that Dawn is nothing more than a
self-aggrandizing ignorant spouting volumes of ignorant nonsense, you
fall into the trap of repeating the ignorant nonsense yourself.
> Agreed.
>
> The LDM is data model dependent.