Central Department of Computer Science and Information Technology

Tribhuvan University

Comparative Study
Of
Object Oriented DBMS and Relational DBMS
Object Oriented Software Engineering (CSC-539)

Submitted To:
Professor Dr. Subarna Shakya
Central Department of Computer Science
And Information Technology

Accomplishment of the requirement for a

Master’s Degree in
Computer Science and Information Technology

Submitted By:
Sibu Dhital
Roll No: 036/080
Regd. No: 5-2-1075-22-2016
May 2024
 V

Table of Content
I. Introduction ................................................................................................................... 1
Comparison of OODBMS to RDBMS ........................................................................... 2
II. Literature Review ……................................................................................................ 2
III. Objective ……………………………………………................................................. 3
IV. Case Study Area Description ………......................................................................... 3
Scenario Overview ……………………......................................................................... 3
Challenges ……………………………........................................................................... 3
Database Requirements ………………........................................................................... 4
Implementation Consideration ….……........................................................................... 4
V. Requirement Model …………….................................................................................. 4
Scenario Overview …………………….......................................................................... 4
Functional Requirement ……………….......................................................................... 4
Non-functional Requirement..………….......................................................................... 5
VI. Analysis Model ……..……………................................................................................ 5
Comparative Analysis ………………….......................................................................... 5
VII. Design Model ……..……………................................................................................ 6
Schema Design ……..………………….......................................................................... 6
API integration ………..……………….......................................................................... 6
Security Implementation …...………….......................................................................... 6
User Interface Design ....……………….......................................................................... 6
Scalability Consideration …..………….......................................................................... 6
VIII. Implementation Model ..…….................................................................................. 6
Technology Stack Selection …..……….......................................................................... 6
Development Environment setup ..…….......................................................................... 6
Schema Implementation …....………….......................................................................... 7
API development ……...……………….......................................................................... 7
Security Implementation .…..………….......................................................................... 7
UI development ..……...……………….......................................................................... 7
Testing & Quality Assurance .………….......................................................................... 7
 V

Deployment and maintenance.……….......................................................................... 8

IX. Conclusion ................................................................................................................. 8
X. Conclusion ................................................................................................................... 8
References ........................................................................................................................ 10
 1

I. INTRODUCTION
In today's world, where technology is everywhere, managing data is crucial for all kinds of
organizations, big or small. From keeping track of customer information to handling internal
records, databases play a vital role in organizing and accessing large amounts of data
efficiently. However, not all databases are the same. There are different types of Database
Management Systems, which can be listed as:
- RDBMS(Relational Database Management System)
- ORDBMS(Object Relational Database Management System)
- OODBMS(Object Oriented Database Management System)
In this paper as a part of case study for the fulfillment of our course work we’re going to
discuss about two of the most common ones called RDBMS and OODBMS.
RDBMS, which stands for Relational Database Management System, is like a digital filing
cabinet that stores data in tables and keeps track of how different pieces of information are
related to each other. RDBMS allows the user to control the database through creating,
updating, administrating and interacting with relational table like structure.

End User

DB Application DB management system

Database

Fig: Diagram of Relational Database Management System

Fig: Basic Model of Tables in RDBMS

On the other hand, OODBMS, or Object-Oriented Database Management System, is a bit

more flexible. Instead of tables, it stores data as objects, similar to how objects work in
computer programming. It focuses on concept of objects such as object categories, object
ownership, polymorphism, encapsulation, etc.
 2

Fig: Object Oriented Database

With so much data being generated every day, especially from things like websites, mobile
apps, and social media, it's essential to understand which type of database is best suited for
different kinds of information. That's where our case study comes in.
Comparison of OODBMS to RDBMS:
Parameters OODBMS RDBMS
Full Form Object Oriented Database Relational Database Management
System System
Objective It ensures data encapsulation.It keeps data independent from
application and programmers.
Query Language Depends on products, Easy Standard Query Language (SQL). It is
to handle recursive queries. difficult to handle recursive queries.
Advanced It supports advanced It doesn’t support advanced
Applications applications. applications
Normalization No need of normalizations. Normalization is strongly
recommended
Use of Algebra Objective algebra. Relational algebra.
Representation Effective representation for Poor representation for real world
real world entities. entities.

II. LITERATURE REVIEW

Historically, Relational Database Management Systems (RDBMS) have been widely utilized
for storing structured data. However, with the exponential growth of data, including both
structured and unstructured forms, there has been a surge in the adoption of Object-Oriented
Database Management Systems (OODBMS) for handling massive and complex datasets.
Studies by Sirish Shetty B and Akshay KC [1] have indicated that non-relational databases
often outperform relational databases in certain scenarios. Furthermore, research by Mahesh
S. Raisinghani and Gabriel Custodio [2] highlights the architectural aspects and applications
of OODBMS, emphasizing their superior performance and scalability compared to relational
database alternatives.
Kwok K. Yu, Byung S. Lee, and Michael R. Olson [3] explored the scalability of OODBMS
architecture, emphasizing the importance of optimizing object cache management for efficient
performance. Meanwhile, Hardeep Singh Damesha [4] delved into the concepts, advantages,
 3

and limitations of both RDBMS and OODBMS, underscoring the evolution of object-based
databases to address the limitations of relational databases and support advanced applications.
Theresa Beaubouef and Frederick E. Petry [5] emphasized the importance of security in
database systems, particularly in applications involving statistical databases and data
mining. They noted the criticality of maintaining data security in rough relational databases
and related systems.

III. OBJECTIVE
Our case study aims to explore and compare the strengths and weaknesses of RDBMS and
OODBMS. By looking closely at how these databases are built, how they handle data, and
how they're used in real-life situations, we hope to help organizations make better decisions
about which database system to use for their needs.
We'll use examples like managing fingerprint databases on websites and mobile apps to show
how different types of data require different approaches to storage and management. By the
end of our study, we hope to provide clear insights into the benefits of each database system
and help organizations choose the right one for their specific requirements.

IV. CASE STUDY AREA DESCRIPTION

In our case study, we will focus on the management of sensitive data, particularly fingerprint
databases, across web and mobile platforms. Fingerprint data is a type of biometric
information used for identity verification and authentication in various applications, including
law enforcement, access control, and mobile device security.
Scenario Overview:
Imagine a scenario where a government agency or a security company needs to manage
fingerprint data collected from citizens or employees. This data needs to be securely stored,
easily accessible, and compatible with both web-based systems and mobile applications.
Challenges:
1. Data Security: Fingerprint data is highly sensitive and requires robust security
measures to prevent unauthorized access and protect individual privacy.
2. Scalability: As the number of individuals in the database grows, the system must be
able to handle the increasing volume of data efficiently.
3. Compatibility: The database must be compatible with both web-based platforms,
such as government portals or corporate websites, and mobile applications used by
field agents or employees.
4. Performance: Quick and reliable access to fingerprint data is essential, especially in
scenarios where real-time authentication is required.
5. Data Integrity: Ensuring the accuracy and integrity of fingerprint data is crucial to
prevent errors or mismatches during identity verification processes.
 4

Database Requirements:
1. Storage Structure: The database should support the storage of fingerprint images or
templates, along with associated metadata such as timestamps and user identifiers.
2. Access Control: Role-based access control mechanisms should be implemented to
restrict access to authorized personnel only.
3. Encryption: Fingerprint data should be encrypted both at rest and in transit to prevent
unauthorized interception or tampering.
4. Cross-Platform Compatibility: The database should be accessible from web
browsers as well as mobile applications running on iOS and Android devices.
5. Scalability: The database should scale seamlessly to accommodate growing datasets
without compromising performance or reliability.

Implementation Considerations:
1. Choice of Database System: Evaluating the suitability of both RDBMS and
OODBMS for storing and managing fingerprint data.
2. Schema Design: Designing an appropriate database schema to represent fingerprint
records and related information.
3. API Integration: Developing APIs for interacting with the database from web and
mobile applications, including methods for data retrieval, insertion, and update.
4. Security Measures: Implementing encryption, access control, and audit logging
mechanisms to ensure the security and integrity of fingerprint data.
5. Performance Testing: Conducting performance tests to evaluate the responsiveness
and scalability of the database under various load conditions.
By focusing on the management of fingerprint data in a real-world scenario, our case study
will provide valuable insights into the comparative effectiveness of RDBMS and OODBMS
in handling sensitive and complex datasets across web and mobile platforms.

V. REQUIREMENT MODEL
Scenario Description:
Our scenario involves the management of fingerprint data across web and mobile platforms
for a government agency or security company. The database system must securely store
fingerprint images or templates and associated metadata, such as timestamps and user
identifiers. Access to the database should be restricted to authorized personnel, and the system
should support both web-based portals and mobile applications for data retrieval and
manipulation.
Functional Requirements:
1. Data Storage: Store fingerprint images or templates along with associated metadata.
 5

2. Access Control: Implement role-based access control mechanisms to restrict database

access.
3. Compatibility: Ensure compatibility with both web-based platforms and mobile
applications.
4. Data Retrieval: Provide methods for retrieving fingerprint data based on specified
criteria.
5. Data Manipulation: Support operations for inserting, updating, and deleting
fingerprint records.
6. Encryption: Encrypt fingerprint data to ensure data security and privacy.
7. Scalability: Scale the database system to handle growing datasets without
compromising performance.
Non-functional Requirements:
1. Security: Ensure data security through encryption and access control mechanisms.
2. Performance: Optimize database performance to ensure quick access to fingerprint
data.
3. Reliability: Maintain high availability and reliability of the database system to prevent
data loss or downtime.
4. Usability: Design a user-friendly interface for interacting with the database system.
5. Scalability: Ensure scalability to accommodate increasing data volumes and user
loads.
6. Compatibility: Ensure compatibility with commonly used web browsers and mobile
operating systems.

VI. ANALYSIS MODEL

Comparative Analysis:
1. Performance: Evaluate the performance of RDBMS and OODBMS in storing and
retrieving fingerprint data.
2. Scalability: Assess the scalability of both database systems in handling increasing
data volumes.
3. Security: Compare the security features of RDBMS and OODBMS, including
encryption and access control mechanisms.
4. Compatibility: Analyze the compatibility of RDBMS and OODBMS with web and
mobile platforms.
5. Ease of Use: Evaluate the ease of use and usability of both database systems for
developers and end-users.
6. Cost: Compare the cost implications of implementing and maintaining RDBMS and
OODBMS solutions.
 6

VII. DESIGN MODEL

Schema Design:
1. RDBMS: Design relational database schema to represent fingerprint data using tables
and relationships.
2. OODBMS: Design object-oriented database schema to represent fingerprint data
using objects and classes.
API Integration:
1. RDBMS: Develop APIs for interacting with the relational database system from web
and mobile applications.
2. OODBMS: Develop APIs for interacting with the object-oriented database system
from web and mobile applications.
Security Implementation:
1. RDBMS: Implement encryption and access control mechanisms to ensure data
security in the relational database system.
2. OODBMS: Implement encryption and access control mechanisms to ensure data
security in the object-oriented database system.
User Interface Design:
1. RDBMS: Design user interfaces for web-based portals and mobile applications to
interact with the relational database system.
2. OODBMS: Design user interfaces for web-based portals and mobile applications to
interact with the object-oriented database system.
Scalability Considerations:
1. RDBMS: Implement scalability features such as sharding and replication to handle
increasing data volumes in the relational database system.
2. OODBMS: Implement scalability features such as distributed caching and
partitioning to handle increasing data volumes in the object-oriented database system.

VIII. IMPLEMENTATION MODEL

Technology Stack Selection:
1. RDBMS: Select a suitable relational database management system such as MySQL,
PostgreSQL, or SQL Server based on performance, scalability, and compatibility with
the chosen development framework.
2. OODBMS: Choose an object-oriented database management system such as db4o,
ObjectDB, or Versant Object Database based on its ability to handle complex data
structures and scalability requirements.
Development Environment Setup:
 7

1. RDBMS: Set up the development environment with the chosen relational database
management system, including installing the database server software and configuring
database connections.
2. OODBMS: Set up the development environment with the chosen object-oriented
database management system, including installing the database server software and
configuring object mapping frameworks.
Schema Implementation:
1. RDBMS: Create relational database schemas to represent fingerprint data using
tables, columns, and relationships. Define primary keys, foreign keys, and indexes to
optimize query performance.
2. OODBMS: Define object-oriented database schemas to represent fingerprint data
using object classes, attributes, and associations. Implement inheritance,
encapsulation, and polymorphism concepts to model complex data structures.
API Development:
1. RDBMS: Develop RESTful APIs or GraphQL endpoints to interact with the relational
database system from web and mobile applications. Implement CRUD (Create, Read,
Update, Delete) operations for managing fingerprint data.
2. OODBMS: Develop object-oriented APIs or object-relational mapping (ORM)
frameworks to interact with the object-oriented database system from web and mobile
applications. Implement object persistence and retrieval methods for handling
fingerprint objects.
Security Implementation:
1. RDBMS: Implement security measures such as encryption at rest and in transit, role-
based access control (RBAC), and parameterized queries to prevent SQL injection
attacks.
2. OODBMS: Implement encryption of object attributes, access control lists (ACLs),
and object-level permissions to secure sensitive fingerprint data in the object-oriented
database system.
User Interface Development:
1. Web Interface: Develop user interfaces for web-based portals using HTML, CSS,
and JavaScript frameworks such as React, Angular, or Vue.js. Implement
authentication and authorization mechanisms to control user access to fingerprint data.
2. Mobile Interface: Develop mobile applications for Android and iOS platforms using
native or cross-platform frameworks such as React Native or Flutter. Integrate
fingerprint scanning APIs for biometric authentication on mobile devices.
Testing and Quality Assurance:
1. Unit Testing: Write unit tests to validate the functionality of database operations and
API endpoints using testing frameworks such as JUnit, NUnit, or Jest.
2. Integration Testing: Perform integration tests to ensure seamless communication
between the database system and web/mobile applications. Test data persistence,
retrieval, and security features under different scenarios.
 8

3. Performance Testing: Conduct performance tests to measure the responsiveness and

scalability of the database system under various load conditions. Identify and optimize
performance bottlenecks to ensure optimal system performance.
Deployment and Maintenance:
1. Deployment: Deploy the database system and web/mobile applications to production
environments using cloud platforms such as AWS, Azure, or Google Cloud. Configure
auto-scaling and monitoring tools to ensure high availability and performance.
2. Maintenance: Regularly monitor database performance, security vulnerabilities, and
system logs to detect and address issues proactively. Apply database schema updates,
security patches, and performance optimizations as needed to ensure the stability and
reliability of the system.

IX. CONCLUSION
This comparative study has explored the strengths and weaknesses of Relational Database
Management System (RDBMS) and Object-Oriented Database Management System
(OODBMS). While it is challenging to definitively declare one as superior to the other, each
database type offers distinct advantages depending on the nature of the data and the
requirements of the application.
RDBMS excels in managing structured data efficiently, offering robust mechanisms for data
manipulation and query optimization. However, when dealing with complex and unstructured
data, OODBMS emerges as a more effective solution. OODBMS can handle big data
seamlessly, accommodating both structured and unstructured data formats with ease.
Through an analysis of various research papers, it is evident that both RDBMS and OODBMS
have their unique architectural features and benefits. While RDBMS remains widely used for
its familiarity and suitability for structured data, OODBMS offers advantages in handling
complex data structures and supporting advanced applications.

X. RECOMMENDATIONS
1. Consider the Nature of Data: Evaluate the nature of the data to be stored and
processed. If dealing primarily with structured data, RDBMS may be sufficient.
However, for applications involving complex or unstructured data, OODBMS may
offer more efficient management.
2. Assess Application Requirements: Assess the specific requirements of the
application, including scalability, performance, and compatibility. Choose the
database system that best aligns with these requirements and offers the necessary
features and capabilities.
3. Explore Hybrid Approaches: Consider hybrid approaches that combine elements of
both RDBMS and OODBMS to leverage the strengths of each. This may involve using
RDBMS for structured data storage and OODBMS for managing complex data
objects.
 9

4. Stay Informed: Keep abreast of advancements in database technologies and evaluate

emerging solutions that may better suit evolving data management needs. Regularly
assess the performance and suitability of the chosen database system in light of
changing requirements and technological developments.
5. Invest in Training and Expertise: Ensure that the development team possesses the
necessary skills and expertise to effectively utilize the chosen database system. Invest
in training and development opportunities to enhance proficiency and maximize the
benefits of the selected database technology.
By carefully considering the nature of the data, application requirements, and available
technologies, organizations can make informed decisions regarding the selection and
implementation of database management systems. While both RDBMS and OODBMS have
their merits, choosing the right database system entails a thorough evaluation of specific needs
and objectives to achieve optimal performance and efficiency.
 10

XI. REFERENCES
[1] Sirish Shetty B and Akshay KC “Performance Analysis of Queries in RDBMS vs
NoSQL”, Published in “2019 2nd International Conference on Intelligent Computing,
Instrumentation and Control Technologies (ICICICT).” Available:
https://ieeexplore.ieee.org/document/8993394
[2] M AHESH S. R AISINGHANI, University of Dallas and G ABRIEL C USTODIO,
Associates Information Services, Inc. “Object Oriented Database Management Systems:
Architecture And Application”, Published in “Journal of Information Technology Theory And
Application”.
[3] Kwok K. Yu, Byung S. Lee, Michael R. Olson “The Scalability of an Object Descriptor
Architecture OODBMS” Published in “1999, Proceedings. IDEAS’99. International Database
Engineering and Application Symposium(Cat. No. PR00265)”
[4] Hardeep Singh Damesha “Object Oriented Database Management Systems-Concepts,
Advantages, Limitations and Comparative Study with Relational Database Management
Systems” in “Global Journal of Computer Science and Technology : C Software & Data
Engineering” Volume 15 Issue 3 Version 1.0 Year 2015 Type: “Double Blind Peer Reviewed
International Research Journal”, Publisher: “Global Journals Inc. (USA) Online ISSN: 0975-
4172 & Print ISSN: 0975-4350”.
[5] Theresa Beaubouef and Frederick E. Petry “Database Security Issues in Rough Relational
Databases”, Published in “2010 42nd South Eastern Symposium on System Theory
University of Texas at Tyler” Tyler, TX, USA, March 7-9, 2010