1 / 17

OBJECT-ORIENTED DBMS

OBJECT-ORIENTED DBMS. Structured & Object Oriented Approaches. Structured approach – long history, well-documented ERD - modeling data DFD - modeling process Tools – System Architect, Visible Analysis OO approach – new, offer benefits such as soft reuse Class Diagram - modeling data

travis
Download Presentation

OBJECT-ORIENTED DBMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. OBJECT-ORIENTED DBMS

  2. Structured & Object Oriented Approaches • Structured approach – long history, well-documented • ERD - modeling data • DFD - modeling process • Tools – System Architect, Visible Analysis • OO approach – new, offer benefits such as soft reuse • Class Diagram - modeling data • USE-Case diagram - system functionalities • Tools – Rational Rose

  3. OO Concepts • Classes • Class is a group of objects that have similar attributes (properties) and behavior • All objects in class have similar attributes and they perform similar operations • E.g. all pupils in a studentsclass will have the same attributes (not attribute values) such as name and address.

  4. An object is a structure that encapsulates (or packages) both data and methods. • The data (also called properties) describes the attributes of the object while methods (also called operations, services, functions or procedures) describe its behavior.

  5. An Object with Attributes and Methods Employee Object’s Name EmpNo EmpName Pay Object’s Attribute ModifyInfo ComputePay Object’s Method

  6. Encapsulation • Encapsulation means packaging both the data object’s and method together • Only methods within an object are allowed to modify the object’s attribute (data). • The data and details of the methods of an object are hidden from other object’s data and methods – i.e. the external methods (belonging to other objects) cannot modify other object’s attribute.

  7. Class Hierarchy Person Superclass (also known as base, parent or ancestor class) Student Lecturer Subclass (also known as child or derived class)

  8. Person Superclass • Multilevel Class Hierarchy Student Employee Base class Full Time student Part Time Student Local employee Foreign employee Base class

  9. Inheritance • Inheritance is the property that when classes are arranged in a hierarchy, a derived class can inherit (automatically) the properties ( attributes) and behaviors (methods) of its parent or base class.

  10. e.g.

  11. Inherited attributes and methods Person Name Age Sex Initialize Add modify Derived Properties Name Age Sex Initialize Add modify Student Employee StudNo Course EmpNo Pay ChangeInfo ComputePay

  12. OO Databases • In OO data management (OODM) , each object in the system has an identity that is internal to the data stored within the object • There is no concept of primary key • OODBMS maintains an external identifier for each object, which is not accessible to any object, function or application • The identity of the object does not change

  13. Types of Methods

  14. Advantages of OODBMS • Enriched modeling capabilities – closely model the real world object • Extensibility – allows to develop new abstract data types using existing data types • More expressive query • Suitable for advance DB applications

  15. Disadvantages of OODBMS • Lack of experience • Lack of standards • Lack of view mechanism • Inadequate security

  16. Despite of its capability, OODBMS did not gain so much popularity and not widely accepted. • Reasons why organizations are reluctant to use OODBMS : • Existing investment • High switching cost • Using two methodologies in the same organization can be expensive • Staff training cost

  17. THE END

More Related