What Are Universal Patterns for Data Modeling?
Much of the material in this article is excerpted with permission from the newly released book, The Data Model Resource Book, Volume 3: Universal Patterns for Data Modeling by Len Silverston and Paul Agnew, published by Wiley Computer Publishing (released January 2009). We have a useful rule of thumb that seems to apply to most data models: One-third of a data model usually consists of common constructs that are applicable to most organizations, one-third of the data model is usually industry-specific, and one-third of the model is specific to an organization. What we have also found in our experience with decades of data modeling is that there are very common patterns, what we call universal patterns, that apply to well over 50 percent of most data model constructs and that can be reused. For example, a status for an order works in the same way as a status for a shipment. The classification of product or person follows the same pattern, regardless of the fact that one classification d
Related Questions
- What are the differences between the ER/Studio Developer Edition data modeling capabilities in RAD Studio Architect and the standard ER/Studio product?
- Does Concentrate just look for predefined patterns, or discover them from the data itself?
- Will JDeveloper provide the same features for Data Modeling as Designer?