These models do not have the proper detail to encourage active involvement from business professionals. Models that are seldom oriented toward audiences other than database developers. These multiple appearances are usually inconsistent and conflicting. Data integrity rules seldom exist and are often shown on the data structure.ĭata definitions and data integrity rules are seldom normalized, and often appear multiple times within and across data models. Data definitions are not comprehensive and denotative. Data names are often abbreviated physical names and those abbreviations are seldom consistent. They seldom have formal data names, comprehensive data definitions, or precise data integrity rules. Models that are not developed within a single organization wide data architecture, leading to disparate models, multiple models of the same data, conflicting models, and competing models. A brute-force-physical orientation towards developing physical data models, consisting largely of structure, and physical data names for cutting the code to develop a database, with little orientation toward business professional understanding of the data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |