Archives of the TeradataForum

Message Posted: Thu, 17 Nov 2005 @ 20:02:15 GMT

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

I agree wholeheartedly with Anonym, having been a Data and Process modeler many years, at all three levels of the enterprise (Conceptual, Logical, and Physical). I agree with your sentiments exactly, and warn anyone who listens to me, as much as I love CASE / design tools, they are just that, a tool. Besides tools, you also need methods, techniques, standards, training, (some would call that a methodology) and a consistent, planned strategy for implementation across not only IT but the Business Units as well, since they need to understand the models being produced for them.

That plan should include the Data Administration function (not to be confused with Database Administration) that can set global policy for those things and manage the Enterprise Wide architecture via what ultimately is produced, hopefully with DA guidance. Oh, and one other thing, a globally accessible data-dictionary or meta-data repository really helps, and should be managed by the DA role as well!

I didn't take the time to make a distinction between Upper Case and Lower Case. UPPER Case tools support the design phases [Conceptual (definition), Logical (function), and Physical (organization)], similar to Architectural artist renderings (conceptual), Architectural Drafts (logical) and Construction blueprints (physical). LOWER case, on the other hand, generates "code", whether it is DDL statements for a database or OOP code for JAVA or C++ that can create or generate the real database or program module as designed by the architect.

A case (no pun intended) can be made, as Anonym pointed out, that without proper training and skill development of Structured Analysis and Structured Design or even Object Orientated Methodology (OOM), the tools become more destructive rather than constructive!

What I like to share with my colleagues is, "Never let a tool drive your development strategy, it should always be the other way around, let your development strategy drive your tools."

Michael E. McBride, MSCIS

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