Software Professionals use Object Oriented data modeling instead of traditional relational data modeling

Abstract

The purpose of this paper is to explain why object oriented data modeling is more popular than relational data modeling. A data model is a logic organization of the real world objects (entities), constraints on them, and the relationships among objects. Relational model is very simple since data in represented in the form of relations that are depicted by use of two-dimensional tables. Rows in the table represent records and Columns represent attributes of the entity. The basic concept in the relational model is that of a relation. In object-oriented model main construct is an object. As in relational model, there are relations similarly we have objects in OO data modeling. So first thing in OO model is to identify the objects for the systems. Examining the problem statement can do it. Other important task is to identify the various operations for these objects. It is easy to relate the objects to the real world entity. The object-oriented approach has proved to be especially fruitful in application areas, such as the design of geographical information systems which have a richly structured knowledge domain and are associated with multimedia databases. Relational data modeling is different from Object Oriented data modeling because it focuses solely on data while object oriented data models focuses on both the behavior and data aspects of your domain. OODBMS are faster than relational DBMS because data isn’t stored in relational rows and columns but as objects. Objects have a many to many relationship and are accessed by the use of pointers.