Database schema evolution using EVER diagrams

ABSTRACT

We present an approach to schema evolution through changes to the ER diagram representing the schema of a database. In order to facilitate changes to the ER schema we enhance the graphical constructs used in ER diagrams, and develop EVER, an EVolutionary ER diagram for specifying the derivation relationships between schema versions, relationships among attributes, and the conditions for maintaining consistent views of programs. In this paper, we demonstrate the mapping of the EVER diagram into an underlying database and the construction of database views for schema versions. Through the reconstruction of views after database reorganization, changes to an ER diagram can be made transparent to the application programs while all objects in the database remain accessible to the application programs. The EVER system can serve as a front-end for object-oriented databases.

REFERENCES

• 1: M. Ahlscn and et. al. Making Type Changes Transparent. In Proceedinga of IEEE Workshop on .Language for Automation, 1983.
• 2: Jay Banerjee , Won Kim , Hyoung-Joo Kim , Henry F. Korth, Semantics and implementation of schema evolution in object-oriented databases, Proceedings of the 1987 ACM SIGMOD international conference on Management of data, p.311-322, May 27-29, 1987, San Francisco, California, United States
• 3: Elisa Bertino, A View Mechanism for Object-Oriented Databases, Proceedings of the 3rd International Conference on Extending Database Technology: Advances in Database Technology, p.136-151, March 23-27, 1992
• 4: Svein Erik Bratsberg, Unified Class Evolution by Object-Oriented Views, Proceedings of the 11th International Conference on the Entity-Relationship Approach: Entity-Relationship Approach, p.423-439, October 07-09, 1992
• 5: Peter Pin-Shan Chen, The entity-relationship model—toward a unified view of data, ACM Transactions on Database Systems (TODS), v.1 n.1, p.9-36, March 1976 [doi>10.1145/320434.320440]
• 6: P. Chen. ER vs. 00. In Proceedings of the 11th Internaltional Conference on Entity-Relationship Approach, 1992.
• 7: Stewart M. Clamen, Schema evolution and integration, Distributed and Parallel Databases, v.2 n.1, p.101-126, Jan. 1994 [doi>10.1007/BF01263340]
• 8: E. F. Codd, A relational model of data for large shared data banks, Communications of the ACM, v.13 n.6, p.377-387, June 1970 [doi>10.1145/362384.362685]
• 9: Ramez Elmasri , Shamkant B. Navathe, Fundamentals of database systems (2nd ed.), Benjamin-Cummings Publishing Co., Inc., Redwood City, CA, 1994
• 10: H. Kangassaio. Concept D: A Graphical Language for Conceptual Modeling and Data Base use. In Proceedings of the IEEE Workshop on Visual Languages, October 1988.
• 11: C. T. Liu, P. K. Chrysanthis, and S. K. Chang. Database Schema Evolution through the !Specification and Maintenance of Changes on Entities and Rclationsh.ips. Technical report, TR-94-14, Department of Computer Science, University of Pittsburgh, January 1994.
• 12: Shamkant B. Navathe , Mahan K. Pillalamarri, OOER: Toward Making the E-R Approach Object-Oriented, Proceedings of the Seventh International Conference on Enity-Relationship Approach: A Bridge to the User, p.185-206, November 16-18, 1988
• 13: H. A. Skarra and S. B. Zdonik. Type Evolution in an O'bject-Oriented Database. In Researc:h in Object- Oriented Databasea. Addison-Wesley, 1987.
• 14: Toby J. Teorey , Dongqing Yang , James P. Fry, A logical design methodology for relational databases using the extended entity-relationship model, ACM Computing Surveys (CSUR), v.18 n.2, p.197-222, June 1986 [doi>10.1145/7474.7475]
• 15: S. B. Zdonik. Object-Oriented Type Evolution . In Advances in Database Programming Languages. Addison- Wesley, 1990.
• 16: Roberto Zicari, A Framework for Schema Updates In An Object-Oriented Database System, Proceedings of the Seventh International Conference on Data Engineering, p.2-13, April 08-12, 1991

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques
          Subjects: User interfaces

Additional Classification:
  D. Software
  D.1 PROGRAMMING TECHNIQUES
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques
          Subjects: Flow charts

  H. Information Systems
  H.2 DATABASE MANAGEMENT
      H.2.1 Logical Design
          Subjects: Data models

General Terms:
Algorithms, Design, Languages