A 5 page paper discussing attributes and benefits of object-oriented (OO) database management systems. As organizations’ data needs become more complex, the need for OO databases will grow as well. Though more complex and more difficult to manage, the OO database management system enables more efficient use of data. Includes a SWOT analysis. Bibliography lists 8 sources.
Name of Research Paper File: CC6_KSitObjOrienDB.rtf
Unformatted Sample Text from the Research Paper:
Brown, DeHayes and Hoffer (2002) give a concise definition of object-oriented databases. Data "can be graphics, video, and sound as well as simpler data types; attributes (data) and methods
are encapsulated in object classes, and relationships between classes can be shown by nesting one class within another" (p. 87). Other database types include hierarchical, network and relational, none
of which is as versatile as the object-oriented database. The Object-Oriented Database There are many examples of relational database systems in use today.
Each consists of "two main modules: a query processor and a storage system. A query processor returns the result of a given query by translating it into a series
of internal storage system calls" (Ahn and Kim, 2002; p. 15). The low-level storage system enables data integrity and transaction management. In object-oriented (OO) database management systems, however,
"it is no longer adequate for upper layers, such as a query processor, to call a low-level storage system directly" (Ahn and Kim, 2002; p. 15). The objects of
the OO system are too complex for this type of access. Though it is possible to manage access in this manner, it is
by no means efficient. Ahn and Kim (2002) write that the upper layers of an OO database management system "should be adapted to the rich and extensible nature of
the object-oriented data model directly, while a traditional relational storage system supports only record-oriented data abstraction" (Ahn and Kim, 2002; p. 15). If upper layers must implement object abstraction
before completing a request, then the user can expect much poorer performance resulting from the increased complexity of approach and the time required by the system to deal with that