Specification preservation in schema transformations — application to semantics and statistics

doi:10.1016/0169-023X(95)00041-P

Data & Knowledge Engineering

Volume 19, Issue 2, 1 June 1996, Pages 99-134

https://doi.org/10.1016/0169-023X(95)00041-P Get rights and content

Abstract

Software design can be modeled as a sequence of transformations applied on initial specifications. In the database domain too, most engineering processes can be described as schema transformations. First, this paper presents a wide spectrum specification model intended to describe data structures at different abstraction levels and according to the current modelling paradigms. This model includes the representation of statistical data about the instances of the data structures. Then, it defines and discusses the concepet transformation. The properties of specification preservation is defined and applied to two important aspects, namely semantics discussed and illustrated by some aspects of DB-MAIN, a representative CASE tool based on this approach.

References (33)

S.B. Navathe
Schema analysis for database restructuring
ACM TODS
(1980)
R. Balzer
Transformational implementation: An example
IEEE TSE
(1981)
C. Batini et al.
Conceptual Database Design
(1992)
C. Batini et al.
Structuring primitives for a dictionary of entity relationship data schemas
IEEE TSE
(1993)
G. Bolois et al.
Transformations in Reengineering Techniques
M. Casanova et al.
Mapping uninterpreted schemes into Entity-Relationship diagrams: Two applications to conceptual schema design
IBM J. Res. & Develop.
(January 1984)
A. D'Atri et al.
Equivalence and Mapping of Database Schemes
O. De Troyer
On data schema transformation
R. Fagin
Multivalued dependencies and a new normal form of relational databases
ACM TODS
(1977)
R. Fagin
Normal form for relational databases on domains and keys
ACM TODS
(September 1981)

S.F. Fikas

Automating the transformational development of software

IEEE TSE

(1985)

J.-L. Hainaut

Some tools for data independence in multilevel data base systems

J.-L. Hainaut

Theoretical and practical tools for data base design

J.-L. Hainaut

A generic Entity-Relationship model

J.-L. Hainaut

Entity-generating schema transformation for Entity-Relationship models

J.-L. Hainaut

Entity-generating schema transformation for Entity-Relationship models

J.-L. Hainaut

A temporal statistical model for Entity-Relationship schemas

Cited by (31)

Data migration: A theoretical perspective
2013, Data and Knowledge Engineering
Citation Excerpt :
ASMs are a practical and scientifically well-founded systems engineer method invented by [17], extensively discussed in [10] and applied in solving various database-related problems in [34,37]. One of the two subclasses of migration transformations – property-preserving transformations – captures schema and data translations in general, and is thus related to various approaches for schema mapping or model translations, e.g., model-independent translations [6], and schema transformations [18,19,22]. Moreover, our notion of reflecting a relation between two models has links with the notion of relative information capacity (i.e., information-capacity dominance and equivalence) studied in the area of semantic heterogeneity [24,25,28].
In this paper we investigate data migration fundamentals from a theoretical perspective. Following the framework of abstract interpretation, we first discuss models and schemata at different levels of abstraction to establish a Galois connection between abstract and concrete models. A legacy kernel is discovered at a high-level abstraction which consolidates heterogeneous data sources in a legacy system. We then show that migration transformations can be specified via the composition of two subclasses of transformations: property-preserving transformations and property-enhancing transformations. By defining the notions of refinement correctness for property-preserving and property-enhancing transformations, we develop a formal framework for refining transformations occurring in the process of data migration. In order to improve efficiency of static analysis, we further introduce an approach of verifying transformations by approximating abstraction relative to properties of interest, meanwhile preserving the refinement correctness as accurately as possible. The results of this paper lay down a theoretical foundation for developing data migration tools and techniques.
Database application evolution: A transformational approach
2006, Data and Knowledge Engineering
Citation Excerpt :
They can be combined to build more complex processes such as schema normalization, logical schema optimization, or DDL code generation. The concept of transformation used in this paper is described formally in [11,13], but we will briefly present those of its principles that are of interest in this paper. A transformation consists in deriving a target schema S′ from a source schema S by replacing construct C (possibly empty) in S with a new construct C′ (possibly empty).
While recent data management technologies, such as object oriented techniques, address the problem of database schema evolution, standard information systems currently in use raise challenging evolution problems. This paper examines database evolution from the developer point of view. It shows how requirements changes are propagated to database schemas, to data and to programs through a general strategy. This strategy requires the documentation of database design. When absent, such documentation has to be rebuilt through reverse engineering techniques. Our approach, called DB-MAIN, relies on a generic database model and on transformational paradigm that states that database engineering processes can be modeled by schema transformations. Indeed, a transformation provides both structural and instance mappings that formally define how to modify database structures and contents. We describe both the complete and a simplified approaches, and compare their merits and drawbacks. We then analyze the problem of program modification and describe a CASE tool that can assist developers in their task of system evolution. We illustrate our approach with Biomaze, a biochemical knowledge-based the database of which is rapidly evolving.
Co-transformations in information system reengineering
2005, Electronic Notes in Theoretical Computer Science
Database reengineering consists of deriving a new database from a legacy database and adapting the software components accordingly. This migration process involves three main steps, namely schema conversion, data conversion and program conversion. This paper explores the feasibility of transforming the application programs through code transformation patterns that are automatically derived from the database transformations. It presents the principles of a new transformational approach coupling database and program transformations and it describes a prototype CASE tool based on this approach.
Changing perceptions of CASE technology
2004, Journal of Systems and Software
The level to which CASE technology has been successfully deployed in IS and software development organisations has been at best variable. Much has been written about an apparent mismatch between user expectations of the technology and the products which are developed for the growing marketplace. In this paper we explore how this tension has developed over time, with the aim of identifying and characterising the major factors contributing to it. We identify three primary themes: volatility and plurality in the marketplace; the close relationship between tools and development methods; and the context sensitivity of feature assessment. By exploring the tension and developing these themes we hope to further the debate on how to improve evaluation of CASE prior to adoption.
An OO interpretation of graphs as meta-CASE's meta-meta-model
2002, Electronic Notes in Theoretical Computer Science
This paper presents the meta-meta-model of a meta-CASE that is largely based on graphs. Nevertheless, the graph aspects have been hidden behind an extended object-oriented model that makes easier the modeling task: the generalization of meta-models into meta-classes as well as the possibility to edit the inheritance relationships at the instance level makes this approach both simple and expressive.
On the representation of roles in object-oriented and conceptual modelling
2000, Data and Knowledge Engineering
Citation Excerpt :
But this observation is false, anyway: a person, for example, has many properties not required of a customer or supplier – rather, being a customer or supplier imposes its required properties on persons and organizations, making the former supertypes of the latter. In fact, some authors treating roles as named places also acknowledge that more than one type can fill one place of a relationship – the domains of Kent [40] or the multi-ET roles of DB-Main [31] are unions or disjunctions of types that are declared for just that purpose. However, while regarding Customer and Supplier as supertypes of both Person and Organization (Fig. 1(d)) accounts for the fact that all persons and organizations can appear in these roles, it defies the dynamic viewpoint, namely that at any point in time only some of all persons and organizations existing at that time are customers and/or suppliers.
The duality of objects and relationships is so deeply embedded in our thinking that almost all modelling languages include it as a fundamental distinction. Yet there is evidence that the two are naturally complemented by a third, equally fundamental notion: that of roles. Although definitions of the role concept abound in the literature, we maintain that only few are truly original, and that even fewer acknowledge the intrinsic role of roles as intermediaries between relationships and the objects that engage in them. After discussing the major families of role conceptualizations, we present our own basic definition and demonstrate how it naturally accounts for many modelling issues, including multiple and dynamic classification, object collaboration, polymorphism, and substitutability.

View all citing articles on Scopus

View full text

PaperSpecification preservation in schema transformations — application to semantics and statistics

Abstract

ACM TODS

Transformational implementation: An example

IEEE TSE

Conceptual Database Design

Structuring primitives for a dictionary of entity relationship data schemas

IEEE TSE

Transformations in Reengineering Techniques

Mapping uninterpreted schemes into Entity-Relationship diagrams: Two applications to conceptual schema design

IBM J. Res. & Develop.

Equivalence and Mapping of Database Schemes

On data schema transformation

Multivalued dependencies and a new normal form of relational databases

ACM TODS

Normal form for relational databases on domains and keys

ACM TODS

Automating the transformational development of software

IEEE TSE

Some tools for data independence in multilevel data base systems

Theoretical and practical tools for data base design

A generic Entity-Relationship model

Entity-generating schema transformation for Entity-Relationship models

Entity-generating schema transformation for Entity-Relationship models

A temporal statistical model for Entity-Relationship schemas

Paper
Specification preservation in schema transformations — application to semantics and statistics