Fandom

Database Management

Object-Oriented Database Model

154pages on
this wiki
Add New Page
Talk0 Share

Object-Oriented Database Model Edit


The Future of Object Oriented Database Modeling Edit

Object oriented database models have been around since the seventies when the concept of object oriented programming was first explored. For several reasons, however, it has not caught on for any major publicly traded organization. It is only in the last ten or fifteen years that companies are utilizing object oriented DBMSs (OODBMS). The major problem for OODBMSs was that relational DBMSs (RDBMS) were already implemented industry wide. Companies preferred to stick with the applications they knew how to use, and had the greatest amount of technical support for. As time passes, this perspective becomes more and more antiquated because object oriented programming has become the preferred technique used by developers (largely due to its superior efficiency and flexibility).

OODBMS should be used when there is a business need, high performance required, and complex data is being used. Due to the object oriented nature of the database model, it is much simpler to approach a problem with these needs in terms of objects. The result can be a performance increase of ten to one thousand times while writing as little as 40% of the code (this is because it requires no intermediate language such as SQL; everything is programmed in the OO language of choice). This code can be directly applied to a database, and thus saves time and money in development and maintenance.

Today companies are starting to catch on and integrate OODBMSs with their RDBMSs. This seems to make the most sense: using the OODBMS for situations that require high performance with complex data and RDBMSs for more traditional functions. An OODBMS is just another tool in a developer’s toolbox that should be used when appropriate to maximize profit. Web applications are an obvious exploitation of this because of the speed and flexibility of the object oriented approach. With the huge rise in use of XML as the backbone of web applications, this popular object modeling language with certainly be key to synchronizing online databases and applications using OODBMSs.

Time will only tell whether OODBMSs will catch on in the main stream, but one would assume that it is only a matter of time before we capture the true power of object oriented systems. They are by far the best attempt developers have made at modeling real life. Software developers have already figured it out; soon enough, DBAs will harness the strength of this powerful developing tool.

References:

UnixSpace Database Models

Service Architecture - ODBMS FAQS

Service Architecture- Other ODBMS Articles



Object-Oriented Database Model


The Future of Object Oriented Database Modeling Edit

Object oriented database models have been around since the seventies when the concept of object oriented programming was first explored. For several reasons, however, it has not caught on for any major publicly traded organization. It is only in the last ten or fifteen years that companies are utilizing object oriented DBMSs (OODBMS). The major problem for OODBMSs was that relational DBMSs (RDBMS) were already implemented industry wide. Companies preferred to stick with the applications they knew how to use, and had the greatest amount of technical support for. As time passes, this perspective becomes more and more antiquated because object oriented programming has become the preferred technique used by developers (largely due to its superior efficiency and flexibility).

OODBMS should be used when there is a business need, high performance required, and complex data is being used. Due to the object oriented nature of the database model, it is much simpler to approach a problem with these needs in terms of objects. The result can be a performance increase of ten to one thousand times while writing as little as 40% of the code (this is because it requires no intermediate language such as SQL; everything is programmed in the OO language of choice). This code can be directly applied to a database, and thus saves time and money in development and maintenance.

Today companies are starting to catch on and integrate OODBMSs with their RDBMSs. This seems to make the most sense: using the OODBMS for situations that require high performance with complex data and RDBMSs for more traditional functions. An OODBMS is just another tool in a developer’s toolbox that should be used when appropriate to maximize profit. Web applications are an obvious exploitation of this because of the speed and flexibility of the object oriented approach. With the huge rise in use of XML as the backbone of web applications, this popular object modeling language with certainly be key to synchronizing online databases and applications using OODBMSs.

Time will only tell whether OODBMSs will catch on in the main stream, but one would assume that it is only a matter of time before we capture the true power of object oriented systems. They are by far the best attempt developers have made at modeling real life. Software developers have already figured it out; soon enough, DBAs will harness the strength of this powerful developing tool.

References:

UnixSpace Database Models

Service Architecture - ODBMS FAQS

Service Architecture- Other ODBMS Articles


Modeling the real world can be a complex process, and the current modeling techniques are not adequate to represent these increasingly complex problems. A more efficient model is needed to do this and the semantic data model (SDM) can accomplish this real world representation. The semantic data model was developed by Michael Hammer and Dennis McLeod in 1981. Entities are represented as objects that contain both data and the relationships of those data. This is why the semantic data model can be designated an object-oriented data model. Another useful characteristic of the object-oriented approach is that objects can also contain the operations or methods that can be performed on it. Objects are classified as simple, composite, compound, hybrid or associative.


Simple objects contain only single value attributes and no attributes that refer to other objects. Composite objects contain at least one multivalued attribute and no attributes that refer to other objects. Compound objects contain at least one attribute that references another object. Hybrid objects contain repeating groups of attributes, one of which must reference another object. Associative objects are used to show relationships between two or more objects. This object contains its own set of attributes and methods.


Objects contain unique identifiers called object ID's. These ID's are stored independently of object attributes. The ID can not be changed and can only be deleted once the object is deleted. This ID, along with attributes and methods make up an objects state. Objects that have similar characteristics can be grouped into classes which contain information on data structure and method implementation. Classes are then organized into a class hierarchy where superclasses are at the top and subclasses branch off to the bottom. In this way inheritance can take place, where superclass methods can be defined and then used in all subclass objects.

Modeling the real world can be a complex process, and the current modeling techniques are not adequate to represent these increasingly complex problems. A more efficient model is needed to do this and the semantic data model (SDM) can accomplish this real world representation. The semantic data model was developed by Michael Hammer and Dennis McLeod in 1981. Entities are represented as objects that contain both data and the relationships of those data. This is why the semantic data model can be designated an object-oriented data model. Another useful characteristic of the object-oriented approach is that objects can also contain the operations or methods that can be performed on it. Objects are classified as simple, composite, compound, hybrid or associative.


Simple objects contain only single value attributes and no attributes that refer to other objects. Composite objects contain at least one multivalued attribute and no attributes that refer to other objects. Compound objects contain at least one attribute that references another object. Hybrid objects contain repeating groups of attributes, one of which must reference another object. Associative objects are used to show relationships between two or more objects. This object contains its own set of attributes and methods.


Objects contain unique identifiers called object ID's. These ID's are stored independently of object attributes. The ID can not be changed and can only be deleted once the object is deleted. This ID, along with attributes and methods make up an objects state. Objects that have similar characteristics can be grouped into classes which contain information on data structure and method implementation. Classes are then organized into a class hierarchy where superclasses are at the top and subclasses branch off to the bottom. In this way inheritance can take place, where superclass methods can be defined and then used in all subclass objects.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.