|
Why Data Models Do Not Work: The Role of Reference Data
|
Last Update 2008/1/8 15:03
|
Category
Database
Data Modeling
|
Description
There is an assumption in database design that all design can be represented in data models. I have not actually heard this assumption stated, but I have not heard it challenged either. It is true that data modelers will question whether a denormalized data model intended for direct implementation as a database truly represents the enterprise’s view of its data. This is often a reason for disagreement between those responsible for logical data models and those responsible for instantiating physical databases. However, ardent purists never act in a way that questions whether a sound logical data model can capture everything that is needed to understand a database design.
|
Hits: 99
|
Why Data Models Cannot Work
|
Last Update 2009/2/3 4:08
|
Category
Database
Data Modeling
|
Description
This article explains why enterprise-level information knowledge management will never be attained by producing a comprehensive set of data models.
|
Hits: 83
|
UML as a Data Modeling Notation, Part 4
|
Last Update 2008/12/10 6:40
|
Category
Database
Data Modeling
:
Approaches, Process, Methods
UML
|
Description
Just as a transformation is required to convert an entity/relationship model into a relational database design, so is one required to convert an entity/relationship model into an object-oriented design. This may involve an automated process of attaching class names to role names, as well as manual efforts to add UML design adornments such as navigation and composition (and, of course, behavior). Because the meaning of the models is different, should the notations be different? There are strong arguments for making it so, but these articles attempted to show that this is not required for the models to make sense. Whatever notation is used, precise, semantically clear models can be produced. To do so is worthwhile, regardless of the particular experiences of the modeler.
|
Hits: 43
|
Too Simple, Too Soon
|
Last Update 2008/1/8 14:43
|
Category
Database
Data Modeling
|
Description
This article explains an application development approach advocated by many proponents of agile application development that can cause future problems for developers, while potentially sacrificing the integrity and reusability of the data.
|
Hits: 51
|
Thought Leaders on Data Modeling, Part 2
|
Last Update 2008/1/8 14:36
|
Category
Database
Data Modeling
|
Description
This article continues the discussion of a central question about data modeling: Is it a descriptive or a creative (design1) process? In the first part, we looked at the data modeling environment, and data modeling problems. Here we cover two further dimensions: process and product, including the “one right answer” issue.
|
Hits: 75
|
|
|
|