While carpenters apply the “measure twice, cut once” rule in practicing their craft, the IT industry often ignores this warning when building operational and analytical systems. Few of us would have difficulty providing examples of systems that were delayed, or even abandoned, due to quality issues associated with data upon which they depended. Many times these issues could have been avoided or implementation schedules more realistically set if an effort had first been made to audit the source data files. An audit would reveal what was really contained in the files as opposed to what was expected based on the file documentation — assuming of course, that any documentation actually existed. When setting up their databases, IT practitioners would be wise to customize another carpentry rule: “verify, then load.”
Der Beitrag ist Mitgliedern der Competence Site vorbehalten. Sie müssen zudem nach Login - falls noch nicht in Ihrem Profil geschehen - einwilligen, dass Ihre folgenden Nutzerdaten:
E-Mail-Adresse, Vorname, Nachname, Position, Organisation und Adresse
an den Herausgeber des Content bzw. den Partner der Verlosung zum Zwecke der Marktforschung, des Marketing und der Kontaktaufnahme weitergegeben werden ("Member Content").
Wenn Sie Mitglied sind, melden Sie sich bitte im folgenden Formular an (Login)!
Keine Kommunikationsobjekte vorhanden.

