Archives of the TeradataForum

Message Posted: Thu, 17 Nov 2005 @ 18:06:56 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Thursday, November 17, 2005 12:32 -->

My company has a policy regarding forums and I respect that policy. I have made multiple presentations at conferences and that would hardly qualify me as a shy person. Heck you can't be shy if half your job is to facilitate meetings and create data and process models across all levels of the enterprise.

I read the forum regularly and posted once to correct a misleading statement on CASE tools because that has not been my professional experience and wanted to share that with the members and encourage them to try them before giving up on them. But in reality I should not complain too much. After all, I have made a nice living correcting the mistakes that other people made misusing CASE tools (including my most recent engagement from our favorite vendor).

I was also Tech Instructor for EDS, circa of 94 and 95, a couple of years teaching my favorite CASE tool. My best line to warn students was:

"CASE tools can make the disaster happen a lot faster". Meaning, CASE tools in the hands of incompetents are a disaster waiting to happen. The last thing an organization moving to CASE needs is the initiative from a young buck assigned to use the CASE tool that does not understand the values of Data Modeling, Process Modeling, and Structured Analysis techniques. Most of the misuse I witnesses and came in to help solve was nothing more than using the CASE tool as a substitute to write code, which was wrong, wrong, wrong (much like folks using Erwin to create database schemas). I guess when all you have is a hammer everything looks like a nail.

That's really what has caused most of the CASE tools capable of generated 100% of the application code across multiple platforms. if you give a high performance automobile to the uninitiated odds he will wrap it around a pole in short term. CASE tools are very powerful and very dangerous in the wrong hands.

Thank you for the forum,

PS. Use Pre and/or Post scripts in the Physical model ERWIN to generate PPIs and JIs. No need to make macros of any kind.

Anonym

	<Prev	Next>		<<First	<Prev	Next>	Last>>