Added by Geoff Sauer on May 25, 2006.
Average rating: 2.25/5.00 (n=4, std dev: 0.96)
 


When it comes to providing reliable, flexible and efficient object persistence for software systems, today's designers and architects are faced with many choices. From the technological perspective, the choice is usually between pure Object-Oriented, Object-Relational hybrids, pure Relational and custom solutions based on open or proprietary file formats (eg. XML, OLE structured storage). From the vendor aspect Oracle, IBM, Microsoft, POET and others offer similar but often-incompatible solutions. This article is about only one of those choices, that is the layering of an object-oriented class model on top of a purely relational database. This is not to imply this is the only, best or simplest solution, but pragmatically it is one of the most common, and one that has the potential for the most misuse.
 

Please share your rating/opinion of "Database Modelling in UML - Part 1".
 PoorExcellent 
click this box if you find the link above broken or out-of-date.

Copyright © 2001-17 by the EServer. All rights reserved.Add a Work | Discussion Forum | Habitués