Architecture of an open object-oriented database management system

Both object-oriented and relational database management systems are referred to as DBMS. The web-scale is expanding at an incredible rate, and with it comes an increase in mobile applications, technologies, and social media platforms. The rapid growth of these technologies produces a variety of structured and unstructured data in various forms, each of which has various consequences for data security. Using RDBMS and OODBMS, this study's methodology outlines the development, installation, and management process of multiple and complicated data sets. This study gives a documented study comparing different kinds of data stored in databases by employing two types of database techniques: relational database method and object-oriented database technique. We use a different fingerprint database for the web and mobile devices. This database is also managed using different technologies, such as MySQL, and it accommodates data generated using distinct methods. In addition, this study explores the benefits and advantages of the various databases and determines the ideal database management system for organizations. According to the survey's findings, RDBMS stores data and the relationships between them in tables, but OODBMS stores data in objects, in a manner analogous to Object-Oriented Programming (OOP). According to the study's findings, the primary distinction between relational database management systems (RDBMS) and object-oriented database management systems (OODBMS) is that RDBMS is a Database Management System based on the relational model. In contrast, OODBMS is a Database Management System that facilitates creating and modeling data as objects.

In several working environments, production involves repeated executions of certain procedures. A workflow describes the individual tasks performed in these procedures and their interrelationships. Current workflow management systems (WFMSs) use a database management system (DBMS) to store task descriptions, and implement all workflow functionality in modules that run on top of the DBMS. Motivated by scientific workflows, we propose a much more DBMS-centric architecture, in which conventional database technology provides much of the desired scientific WFMS functionality. A key element of our approach is viewing the workflow as a web of data objects interconnected with active links that carry process descriptions. The workflow is fully defined as a database schema, and its execution is the gradual buildup of an instance of this schema through the active object links. For our work, we use the modeling and querying tools of Horse, the object-oriented DBMS that we have developed in the context of the Zoo Desktop Experiment Management Environment.

Results and observations gathered while implementing the ANSI T1M1.5 GNM-T1.214 standard within an object-oriented database management system (ODBMS) framework are discussed. The generic network model (GNM) proposes a dynamic network modeling methodology that encompasses a wide spectrum of managed telecommunication network resources. Within the GNM, managed telecommunication resources are modeled from building blocks of lower-level resource elements (logical or physical). The complex relationships between GNM resource elements are described either by specialization/generalization or user/containment; therefore, an ODBMS is well suited for implementation of the GNM as compared to conventional database management systems. The ODBMS framework described also allows the database model to evolve with the GNM. It is demonstrated that a proposed refinement of the GNM into subclasses results in a functional database design that can model a large variety of network resources in accord with a standardized network view. >

The V 3 Video Server is a demonstration showing a multimedia application developed on top of the VODAK database management system. VODAK is a prototype of an object-oriented and distributed database management system (DBMS) developed at GMD-IPSI. The V 3 Video Server allows a user to interactively store, retrieve, manipulate, and present analog and short digital video clips. A video clip consists of a sequence of pictures and corresponding sound. Several attributes like author, title, and a set of keywords are annotated. The highlights of the demonstration are as follows. (1) It is shown that an object-oriented database management systems is very useful for the development of multimedia applications. (2) The video server gives valuable hints for the development of an object-oriented database management system in direction to a multimedia database management system .

The use of diverse standards while developing web and mobile technologies brings new challenges when it comes to flexibility, interoperability, customizability and extensibility of the software systems. In addition, such systems in most of the cases are closed, thus make the development and customization process for system designers, developers and end-users a challenging effort. All these developments require further research attention. This work addresses these challenges from open system architecture perspective. The proposed approach is based on practical development efforts, and theoretical research including state of the art projects and definitions related to open architectures that we surveyed. The initial results indicate that a combination of service-oriented approaches with open source components and open standard data formats pave the way towards an open, extensible architecture. The core contribution of this research will be (a) an open architecture model and (b) the developed system itself based on the model, and (c) the benefits of applying open architecture approaches throughout the development processes.

The V3 Video Server is a demonstration showing a multimedia application developed on top of the VODAK database management system. VODAK is a prototype of an object-oriented and distributed database management system (DBMS) developed at GMD-IPSI. The V3 Video Server allows a user to interactively store, retrieve, manipulate, and present analog and short digital video clips. A video clip consists of a sequence of pictures and corresponding sound. Several attributes like author, title, and a set of keywords are annotated. The highlights of the demonstration are as follows. (1) It is shown that an object-oriented database management systems is very useful for the development of multimedia applications. (2) The video server gives valuable hints for the development of an object-oriented database management system in direction to a multimedia database management system.

As the industrial robot manipulators are widely used in various industrial fields, the limitation of traditional closed architectures for robot control systems becomes increasingly evident. It is almost impossible to modify the planning algorithms, the robot model, or the type of servo amplifier block. In this paper, an open architecture of robot control system is presented. It allows users to change the hardware architecture of the control system, e.g. change the geometric parameters of robots, the number/type of axes, and the servo amplifier block. It allows users to modify both the motion and interfacing software, e.g., modify/replace motion planning/control algorithms or change the human-machine interface to make it friendlier. In most traditional robot control systems, it is not provided to plan velocity profile on-line, which becomes essential in some applications. An on-line velocity filter with the function of look-ahead is thus proposed and implemented. It is integrated in the open-architecture robot control system, which provides users great flexibility to plan the motion on-line. Furthermore, the velocity look-ahead function guarantees the motion accuracy by imposing limits on velocity. Experiments validated the proposed velocity filter and the control system.

PurposeTo describe the evolution of a content management system at the University of Maine Library that would function as a universal, extensible metadata repository, thereby eliminating the need to build separate databases for new digital collections, and facilitating both end‐user access and the management of electronic resources in an integrated technology environment.Design/methodology/approachBeginning with the development of a prototype system that mapped EAD encoded finding aids to a relational database, this paper discusses the evolution of this prototype into the design and implementation of a RDBMS (and continuing development of an object‐oriented database management systems (OODBMS) system) to actively manage digital objects and associated metadata. The key to the system design is metadata: extracting and mapping, transforming, and managing the processing of MARC‐based metadata into non‐MARC schemes to build digital collections. Other relevant CMS architecture issues discussed are the design of a functional bibliographic structure and utilities for metadata harvesting and indexing.FindingsProvides information on the use of the Dublin Core Abstract Model and a flexible and adaptable collection‐centric approach in the overall CMS architecture as implemented on a non‐MARC RDBMS, and provides an explanation of the advantages of an object oriented database system over the complexity of evolving relational database tables.Practical implicationsA useful source for the development of an in‐house CMS, and a contribution to the growing body of literature about the transformation of MARC‐based metadata for database design.Originality/valueThis paper is a case study of actual work conducted at the University of Maine Library. The RDBMS manages digital collections; the OODBMS manages digital video and other multimedia resources.

A key observation is that the invariants in database management determine the mapping steps of the supporting architecture. Referring to the multi-layered architecture of record-oriented database management systems (DBMSs), we sketch the advances made during the past decades. Then, we explore the ways how this proven architecture can be used to implement XML DBMSs (XDBMSs). Major changes and adaptations are needed in most of the layers to support fine-grained XML document processing (XDP). The use of DeweyIDs opens a new paradigm for the management of XML document trees: While preventing node relabeling, even in case arbitrary large subtrees are inserted into an XML document, DeweyIDs offer great benefits for efficient navigation in the document trees, for declarative query processing, and for fine-grained locking thereby avoiding access to external storage as far as possible. The proposed architecture also captures horizontal and vertical distribution of XML processing. Nevertheless, new architectural models are needed beyond record-oriented data types.

We present a strategy for the validation of an Object Oriented Database Management System (ODBMS), an off-the-shelf component software, when we deliberately introduced faults and observe its behavior in the presence of these faults. A tool designed for the injection of faults in OO applications, specially Java language systems, was used. This Software Fault Injection tool, Jaca, was developed at UNICAMP and has the ability to inject faults in objects’ attributes and methods. For the experiments we used an ODBMS performance test benchmark, Wisconsin OO7. The experiments were aimed at validating the robustness of the ODBMS component in the presence of errors originated at the application. For that purpose a fault injection strategy was proposed to help answer the questions: Where to inject? What error model to use? This strategy was applied, so some results and their analysis are presented. Improvement for Jaca were addressed as a experiments’ result.

There are many problems facing scientists in their efforts to use computers to manage, access, and analyze data. One serious problem is the heterogeneity of data sources. Previous research into accessing heterogeneous data has not addressed problems with accessing large data sources that are not managed by database management systems. We believe that an object-oriented database management system can be used to implement an object-oriented heterogeneous database (OOHDB) that efficiently addresses the problem of heterogeneity among large scientific property databases. The object-oriented data model provides a powerful modeling paradigm for representing complex scientific data. Objects within the OOHDB hide heterogeneity among various data sources. Efficient access to external data is achieved by representing external data with a small amount of data stored within the OOHDB.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

CASE tool for reusable software component storage and retrieval in rapid prototyping

We describe the implementation of a version manager on an object-oriented database management system. The version manager supports various version semantics and version derivation graphs. Especially, it supports the version propagation to effectively manage versions of design objects and the efficient storage management for versions. All functionalities of the presented version manager are integrated with an object-oriented database programming language seamlessly. Therefore, designers can simply develop their applications which manipulate design objects.

The large number of flight critical and maintenance intensive dynamic components in a helicopter has led to the development of diagnostic systems to improve flight safety and reduce operations and support costs. These systems, commonly called health and usage monitoring systems (HUMS), have been used on large commercial helicopters and are now being developed for military helicopters. US Navy embarked on an innovative approach to fielding an integrated mechanical diagnostic system for Navy helicopters. An accelerated program was started to field a militarized version of a commercial health and usage monitoring system for the CH-53E and SH-60B helicopters. An open systems architecture is critical to the military implementation of HUMS technology on multiple platforms. An open system architecture is essential for system upgrades and for the introduction of the broad range of new technologies as they become available from a number of different sources. Through significant team effort and participation, the IMD-KUMS program is successfully navigating the often-turbulent waters of open system architecture implementation. This paper will provide details on some of the lessons learned from both an industry and government perspective and provide a program status update.

As information systems and, more specifically, database management systems, attempt to model particular application environments, they must be able to account for and keep track of how the entities in the environments relate to each other. In the first or navigational generation of DBMS, relationships were maintained by pointer chains that connected the records representing the related entities. In the second or relational generation of DBMS, the tuples, representing related entities were not connected by pointers, but could be “joined†at query time based on common values of particular fields. In the third or object–oriented generation of DBMS, there are two major structural approaches. One is a pointer–based approach while the other, is designed to add advanced, object–oriented features to the relational model. Recently, perhaps inevitably, interest in the object–oriented pointer–based approach has led to questions of whether it is, in some sense, a return to navigational DBMS. While object–oriented database clearly has major features that go far beyond the capabilities of first generation DBMSs, this article will show that a comparative analysis of pointer usage in navigational DBMS and in object– oriented DBMS can yield interesting results, plus a better understanding of the object–oriented DBMS paradigm.