Don't Forget About Database Design
Okay, you have mapped the workflows, defined the performance gaps, generated measurable objectives and supporting metrics, but what have you done to insure that the database design is functionally correct? Yes, you heard me right: database design. Virtually all process improvement initiatives rely heavily on technology to leverage operations. The foundation of every business application is its database. Get the database design right, and you will greatly reduce the Total Cost of Ownership (TCO) of the application over time. Get the database design wrong, and you can expect a bumpy implementation and a TCO that could run 8 to 20 times the original development cost over the next 10 years.
Here comes the hard part. Most of you PI pros out there rely on the IT staff to deliver a quality database design that is "normalized" and that mirrors the "natural structure" of the industry and business the applications are intended to support. Unfortunately, most IT folk are competent in tools, hardware and languages but NOT in database design. In fact, many database administrators (DBAs) are gurus in a specific database engine like Oracle, Sybase, DB2, Informix, etc., but not in how to design a structure that truly transcends time (present readers excluded, of course). This is not because they don't have the theoretical background to do the job, but t is because they do not understand how
Please log in or sign up below to read the rest of the article.
|
"Very deep. You should send that into Reader's Digest, they've got a page for people like you." - Douglas Adams |




