Cover Page    Full-Text Download    
Subscribe Now
Recommend the Paper
An Ameliorated Methodology to Establish Compatibility between Structural Parts of Object Oriented Technology and Network DBMS  
Siddappa G Makanur1,Shivanand M Handigund2,M. Sreenivasa Rao3
*1, S T J Institute of Technology, RANEBENNUR-581115, India, Email :
*2, Bangalore Institute of Technology, VV Purum, BANGALORE, Email :
3, School of IT, JN Technological University, HYDERABAD, India, Email :
Abstract .Object Oriented (OO) concept is widely accepted for software development by the software development community for its naturalness and mathematical rigor. Object Oriented Analysis & Design (OOAD) is supported by Unified Modeling Language (UML). Though, OO Technology (OOT) is developed with the state of the art technology, it is passive i.e. it can not be implemented for the development of software projects on its own. On the other hand the Network Database Management System (NDBMS) is active for the implementation of the information system, but suffers from lack of au-courant technology. Both are having complementing characteristics of each other. This paper identifies these complementing virtues and lacunae of both the paradigms and super imposes one over the other. The super imposed paradigm nullifies lacunae of one with the virtues of the other and vice versa. This superimposition is used to develop a robust object network database management system. This act necessitates establishment of compatibility amongst model elements of OOT and NDBMS. In this paper, we have developed an ameliorated methodology that brings compatibility between these two paradigms. This transforms the OOT paradigm from passive to active at the same time it provides NDBMS with state of the art coating without enhancing its complexity. We have mapped model elements viz. Class to Record Types, inter relationships such as Association, Composition and Aggregation to Set Types, inheritance of superclass and subclasses to record type, at present this is achieved at the cost of introducing a constraint that subclasses are non overlapping.
Keywords : Modeling elements ; UML ; OOAD ; OOT ; CODASYL ; NDBMS ; Bachman diagram ; ORDBMS ; OODBMS ; Multiple Inheritance

Subscribe Now

Email :    
Subscribe to receive free TOC's JSCSE by email

Recommend To Friend

Email :     People