Re: One-To-One Relationships

"Marshall" <marshall.spight_at_gmail.com> wrote in message news:a4fffcd0-451b-4fad-8ae8-caac4aa32456_at_d21g2000prf.googlegroups.com...
> On Dec 2, 10:46 am, "David Cressey" <cresse..._at_verizon.net> wrote:
> >
> > I've said this before, and I'll say it again: ER is an analysis tool,
not
> > a design tool.
> > A "schema" is a feature of the design, not a feature of the problem
> > statement.
>
> Interesting. The part of that I understood made sense to me.
>
> Okay, I'm just going to come out and ask the question,
> even though it's embarrassing to do so.
>
> What is analysis?
>
> I've been programming for 20+ years. I go talk to people
> and I find out what they want and I write some software
> and I show it to them and they say they'd like the changes
> and so forth. Very concrete.
>
> I often find myself confused about all the terminology
> people use to describe what I do. It took me a long
> time to figure out the difference between a requirements
> doc and a functional spec.
>
> I know what a requirement is. I know what a change
> request is. I know what code is and I think I know
> what a design is.
>
> What's analysis?
>

OK, now that you've asked, and now that Cimode has asked what, in this context is the difference between an analysis model and a design model, it's time to give a erious answer to the question.

I'll start a new topic.

>
> Marshall
Received on Mon Dec 03 2007 - 01:14:26 CET