Evolution of persistent data is a critical need for a large class of software systems, like CASE or CAD environments. So, it is quite natural for data management needs to change and for possible drawbacks in the logical database design to be highlighted. In order to satisfy these needs, the data schema must be able to change and the database must be restructured to meet the newly adopted schema...

Schema Matching is a method of finding attributes that are either similar to each other linguistically or represent the same information. In this project, we take a hybrid approach at solving this problem by making use of both the provided data and the schema name to perform one to one schema matching and introduce creation of a global dictionary to achieve one to many schema matching. We exper...

| The database schemata often experience considerable changes during the development and initial use phases of database systems for advanced applications, such as manufacturing automation and computer-aided design. An automated schema evolution system can signiicantly reduce the amount of eeort and potential errors related to schema changes. Although schema evolution for non-real-time databases...

There exists a current trend in database technology to make databases more extensible and exible, or even to generate databases for speci c customer needs. So far, schema management and especially schema evolution have been excluded from this trend. In this paper, we propose a new approach to schema management and topics centered around it, like schema consistency and schema evolution. This app...

Schema model (schema network) is a established on the concept of neural network, networking memory, and subconsciousness. It also related to psychoanalysis which barely seen in papers neuroscience today. This paper reviews different pre-existing theories around “cognition” schema. To some extent, it redefines subconscious without being overly philosophic creates system another perspective view ...

Advanced object-oriented applications require the management of schema versions, in order to cope with changes in the structure of the stored data. Two types of versioning have been separately considered so far: branching and temporal. The former arose in application domains like CAD/CAM and software engineering, where different solutions have been proposed to support design schema versions (co...

Practical experience shows that the design of very large database schemata causes severe problems, and no systematic support is provided. In this paper we address this problem. We define an Entity-Relationship schema algebra, which permits the representation of very large database schemata by algebraic expressions involving smaller schemata. Similar to abstraction mechanisms found in semantic d...

With rapid advances in computer network technology and the increasing interest in global information sharing, grows the need for facilities that can eeectively maintain the database consistency and program compatibility as the schema evolves. In this paper, we present a general framework based on versions of schema for supporting seamless schema evolution in large-scale object-oriented software...