Object‑Oriented Model

In database management systems, the Object-Oriented Model is a database model that represents data as objects, similar to the concepts used in object-oriented programming (OOP). In this model, data and the operations (methods) that act on that data are packaged together into objects. This model is used in Object-Oriented Database Management Systems (OODBMS) to store complex data structures that are difficult to handle with traditional relational tables.

The Object-Oriented Model extends traditional data models by directly supporting concepts such as classes, instances (objects), inheritance, encapsulation, and polymorphism. It is particularly useful for applications that need to store and manage complex, real-world objects with rich behavior, such as engineering designs, multimedia contents, or simulation data.

What is the Object-Oriented Model?

In the Object-Oriented Model:

Object

An object is a self-contained unit that combines:

• data (attributes)

• operations (methods)

Each object is an instance of a class.

Class

A class is a blueprint that defines:

• the structure of objects

• the behavior of objects

All objects of the same class share the same attributes and methods.

Attribute

An attribute is a property or data member of an object.

Examples:

• Roll_No

• Name

• CGPA

• Price

• Rating

Method

A method is a function or operation associated with an object.

Examples:

• enroll_in_course()

• calculate_grade()

• display_details()

• update_price()

This model is suitable for representing:

• engineering designs

• multimedia objects

• spatial data

• medical imaging data

• simulation models

because such systems involve complex structures and behaviors.

Example of the Object-Oriented Model

Consider a student management system.

Class: STUDENT

The STUDENT class defines:

Attributes

Roll_No
Name
Branch
CGPA

Methods

enroll_in_course(course)
calculate_grade()
display_details()

Objects (Instances)

Student1

Roll_No = 101
Name = "Aman"
Branch = "CSE"
CGPA = 8.5

Student2

Roll_No = 102
Name = "Riya"
Branch = "ECE"
CGPA = 7.9

Each object stores:

• its own data

• and can perform operations defined by the class

This closely resembles real-world entities and their behavior.

How the Object-Oriented Model Works

In this model:

Data is Stored as Objects

Objects contain:

• attributes

• methods

instead of only rows and columns.

Relationships Use Object References

Objects may reference other objects directly.

Example:

• a student object may reference course objects it is enrolled in.

Inheritance

A child class can inherit attributes and methods from a parent class.

Example:

UG_STUDENT and PG_STUDENT
inherit from STUDENT

Encapsulation

The internal state of an object is hidden.

Access is controlled through public methods.

Polymorphism

The same method may behave differently for different object types.

Example:

display_details()

may display different formats for:

• Undergraduate students

• Postgraduate students

Because the model matches OOP languages like:

• Java

• C++

• C#

applications can directly map program objects to database objects. This reduces the mismatch between relational tables and program structures.

Key Features of the Object-Oriented Model

Objects with Data and Behavior

Objects combine:

• state (attributes)

• behavior (methods)

Classes and Inheritance

Supports reusable hierarchical structures.

Encapsulation

Internal data is hidden from outside access.

Polymorphism

Methods can behave differently depending on object type.

Support for Complex Data

Naturally handles:

• multimedia data

• spatial data

• nested structures

• temporal data

Object Identity

Each object has a unique identity independent of attribute values.

Advantages of the Object-Oriented Model

Natural Real-World Representation

Models real entities more naturally than tables.

High Reusability

Inheritance reduces code duplication.

Seamless OOP Integration

Works well with:

• Java

• C++

• C#

Efficient for Complex Applications

Useful for:

• CAD systems

• CAM systems

• GIS systems

• multimedia databases

• engineering simulations

Flexible Schema

Classes can evolve without redesigning the whole database.

Limitations of the Object-Oriented Model

Complex Design

More difficult than relational models.

No Universal Query Language

Unlike SQL, no single standard query language exists.

Learning Curve

Requires understanding of object-oriented programming concepts.

Limited Ecosystem

Fewer tools and less industry adoption compared to relational DBMS.

Not Ideal for Simple Business Systems

Relational databases are usually simpler for:

• banking

• inventory

• payroll

• transactional systems

When to Use the Object-Oriented Model?

The Object-Oriented Model is suitable when:

• data is highly complex

• applications use OOP languages

• behavior is tightly coupled with data

• multimedia or spatial objects are stored

• simulation or engineering systems are built

Visualization of the Object-Oriented Model

Class Definition

Class STUDENT

Attributes:
Roll_No : Integer
Name    : String
Branch  : String
CGPA    : Float

Methods:
enroll_in_course(course)
calculate_grade()
display_details()
change_branch(new_branch)

Objects

Student1:
  Roll_No = 101
  Name = "Aman"
  Branch = "CSE"
  CGPA = 8.5

Student2:
  Roll_No = 102
  Name = "Riya"
  Branch = "ECE"
  CGPA = 7.9

Object-Oriented Model vs Relational Model

Summary

The Object-Oriented Model in DBMS stores data as objects that combine attributes and methods, closely following object-oriented programming concepts. It supports classes, inheritance, encapsulation, and polymorphism, making it ideal for complex applications involving multimedia, engineering, spatial, and simulation data. Although it is more flexible and expressive than the relational model, it is also more complex and less standardized, so it is mainly used in specialized domains rather than general business applications.