Re: Just one more anecdote

On Wed, 03 Aug 2005 23:26:41 -0400, Kenneth Downs wrote:

(snip)
>What I said was that you can take the user's needs and think about them
>directly in terms of the end result - tables. Using either white-board,
>chalk-board, GUI design tool, or paper and pen (my own method), you state
>the record-keeping needs in terms of tables that will hold the information.
>You erase, change, and modify until the needs are precisely stated. At
>this point you have completed analysis, and ain't that the dickens, you've
>got table designs also.
>
>Stating the needs in any other way is incomplete unless you have enough
>information to design the tables, so why not just state them as table
>definitions in the first place.

Hi Kenneth,

Are you aware of ORM?

ORM is an analysis method. But the completed ORM model holds *MORE* information than can be mapped into tables. An ORM diagram maps to tables, primary key, unique, check and foreign key constraints, plus a bunch of constraints that can't be directly implemented in any RDBMS that I know of.

I'd say that stating the needs as table definitions is incomplete.

Best, Hugo

-- 

(Remove _NO_ and _SPAM_ to get my e-mail address)