This article discusses the different types and uses of data models, what they are good for, what the differences are between them. The author then analyzes the needs of an integration architecture and the special requirements it puts on a data model.
This article shows that there is far more to data modeling than simply applying a few stereotypes to UML class diagrams. It describes conceptual, logical and physical data modeling notation, focusing on physical modeling.
This article offers a step by step approach to transform a UML object-oriented class model in a purely relational database.