For a company with many databases in different data models, it is necessary to consolidate them into one data model interchangeable and present data in one data model concurrently to users. The benefit is to let user stick to his/her own data model to access database in another data model. This paper presents a semantic metadata to preserve database constraints for data materialization to suppo...

My guess is that object-oriented programming will be in the 1980s what structured programming was in the 1970s. Everyone will be in favor of it. Every manufacturer will promote his products as supporting it. Every manager will pay lip service to it. Every programmer will practice it (differently). And no one will know just what it is. Tim Rentsch in [Ren82] In this chapter we explore essential ...

Although views have been found to be important mechanisms for database systems, currently no commercially available OODBMS supports view management tools. There are many challenging problems related to view management that must be adressed in the context of object-oriented models: what features are required to support a view system, how to provide updatable views, and how to utilize the complex...

In this dissertation we present a new approach to updatable, object-oriented, virtual (non-materialized) database views. It is based on the Stack-Based Approach (SBA) to object-oriented query languages, which assumes the description of semantics in the form of abstract implementation of query/programming language constructs. The semantics is expressed in terms of naming, scoping and binding. It...

Recently, a range of applications of views increases. Views are not anymore tightly related to classical databases – there are proposals to use them as means of data transformation and integration in distributed environment. Despite many aspects of view applications, there is still lack of suitable graphical notation that would help designers by providing clear notions from the very early stage...

This paper presents an environment to support the use of specification for mixed systems, i.e. systems with both dynamic (behaviour) and static (data type) aspects. We provide an open and extensible environment based on the KORRIGAN specification model. This model uses a hierarchy of view concepts to specify data types, behaviours and compositions in a uniform way. The key notion behind a view ...

Because there is no difference between derivation rules and view definitions, DOOD systems are the best candidates to support an object-oriented view mechanism. Yet, to combine expressive power (i.e. no restriction on queries defining views), reusability and modeling accuracy (i.e. insertion of views into the generalization hierarchy), and consistency (stability in oid generation) is still an o...