object oriented data base management system

Views:
 
Category: Education
     
 

Presentation Description

No description available.

Comments

Presentation Transcript

The Object-Oriented Database System:

The Object-Oriented Database System MIS

Three Points Characterize:

Three Points Characterize Lack of a common data model Lack of formal foundations Strong experimental activity

Must Satisfy Three Criteria:

Must Satisfy Three Criteria Should be a DBMS Should be an object oriented system Should be consistent with object oriented languages

Main Features and Characteristics of OODBMS:

Main Features and Characteristics of OODBMS Mandatory Features Optional Features Open Features

Mandatory Features:

Mandatory Features Features for general databases Features for object oriented databases

Features for General Databases:

Features for General Databases Persistence Secondary storage management Concurrency Recovery Ad-Hoc query facility

Features for Object Oriented Databases:

Features for Object Oriented Databases Complex objects Object identity Encapsulation Types and classes Inheritance Overriding combined with late binding Extensibility Computational completeness

Complex Objects:

Complex Objects Simple objects Integer, characters, byte string, boolean, float, vs. Complex objects Tuples, sets, bags, lists, arrays Thou shalt support complex objects

Complex Objects Cont’d:

Complex Objects Cont’d Object constructers must be orthogonal Appropriate operators must be provided Thou shalt support complex objects

Object Identity:

Object Identity Object sharing Object updates Thou shalt support object identity

Encapsulation:

Encapsulation Interface and implementation Modularity Thou shalt encapsulate thine objects

Types and Classes:

Types and Classes Supporting the notion of class Supporting the notion of type Thou shalt support types and classes

Class or Type Hierarchies:

Class or Type Hierarchies Substitution inheritance Inclusion inheritance Constraint inheritance Specialization inheritance Thine classes or types shalt inherit from their ancestors

Late Binding:

Late Binding Overriding Overloading Late binding Thou shalt not bind prematurely

Computational Completeness:

Computational Completeness SQL is not computationally complete Reasonable connection to existing programming languages Thou shalt be computationally complete

Extensibility:

Extensibility System defined types User defined types No distinction in usage Distinction in low level support Thou shalt be extensible

Persistence:

Persistence Data survival Should be orthogonal Should be implicit Thou shalt remember thy data

Secondary Storage Management:

Secondary Storage Management Index management Data management Data clustering Data buffering Access path selection Query optimization Thou shalt manage very large databases

Concurrency:

Concurrency Same level of service Harmonious coexistence Atomicity of a sequence of operations Controlled sharing Serializability of operations Thou shalt accept concurrent users

Recovery:

Recovery Back to coherant state of data Processor failures Disk failures Thou shalt recover from hardware and software failures

Ad Hoc Query Facility:

Ad Hoc Query Facility Should be high level Should be efficient Should be application independent Thou shalt have a simple way of querying data

No Consensus:

No Consensus View definition and derived data Database administration utilities Integrity constraints Schema evolution facility

Optional Features:

Optional Features Multiple inheritance Type checking and type inferencing Distribution Design transactions Versions

Open Features:

Open Features Programming paradigm Representation system Type system Uniformity