ABSTRACT
If you ask anyone who knows a little about databases what should go into a database management system (DBMS) product, they will most likely specify the facilities provided by current network or relational DBMSs. If you ask anyone who knows a little about Object Oriented databases what should go into an Object Oriented database management system (OODBMS) product, there will be a wide range of responses, not all of which will be consistent with each other. When purchasing a DBMS, one knows what to look for as far as user interface, software architecture and functionality are concerned. In the case of an OODBMS, though, there are currently so many variables that comparison between systems is very difficult. This problem will need to be resolved before OODBMSs take off as commercial products.
