Re: Multiple specification of constraints

"Jerome H. Gitomer" <jgitomer_at_erols.com> wrote:

> You might partition your system development that way, but some
> of us use a different model. For example, I use a model based
> on the concept of noun and verb. Verbs (procedures) operate on
> Nouns (Data). Data is further divided into two categories:
> Control Data and Application Data.
>
> Using my model your dropdown list would be Control Data stored
> in a table and could only be changed when the installations
> change and validation criteria were satisfied.
>
> My model perpetuates the dba and developer project team for good
> reason -- Separation of Authority. It reflects the need for
> commercial enterprises to protect their data from change except
> through authorized, controlled and monitored processes. Those
> who control the data should not develop the procedures that
> operate on the data and those that develop the procedures should
> not be responsible for the integrity of the data. Experience
> has proven that it is too risky to do otherwise -- not from a
> systems point of view, but from the point of view of the
> enterprise that owns and uses the data.

Well explained Jerry. Received on Sun Mar 07 2004 - 02:20:12 CET