Gentle Listers:

I need some assistance in presenting to my client the necessity for
performing several database
modifications in systematic conceptual fashion. We are making several
non-trivial changes (additions) in functionality to a legacy application.
Some of the management feel that it has an expected life of 5 years and thus
are reluctant to change the physical design of several critical datasets
because a) They fear the aspect of missing source modules may arise, and b)
There is
reluctance to diddle the physical design because of the number of affected
Cobol and Powerhouse programs affected (only about 300). They propose to
graft on a Detail dataset with the required new fields althought they
(fields) by rights belong upon the Master that they are referenced to.

Apart from ascetics and first, second and third normal form concepts, would
you be so kind as to please furnish me some concrete ideas for my defending
the'right way' of doing these changes?

Please reply offline to this forum as discretion is appreciated.

Horror stories are welcome.

Cost overruns frankly received.

Missed deadlines relished.

Many thanks for assistance.

John M Penney

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *