A Graphical User Interface for Schema Evolution in an Object-Oriented Database

  • Simon Monk
Conference paper
Part of the Workshops in Computing book series (WORKSHOPS COMP.)


This paper describes work carried out to prototype a GUI to support schema evolution using class versions. Class versions used for schema evolution require a more sophisticated GUI than schema editors (for schema design), because the database is populated an because support is required to browse and maintain the class versions. Current systems for class versioning require exception handlers or conversion functions to be defined as part of the schema evolution process and thus the GUI must provide support for these operations.

A number of desirable properties for such a GUI are discussed and illustrated with examples from the GUI developed by the author.


Schema Evolution Class Version Schema Change Class Definition External Program 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Sjoberg, D. Quantifying schema evolution. Information and Software Technology 1993; 35 (1): 35–44.CrossRefGoogle Scholar
  2. 2.
    Monk, S R and I Sommerville. Schema Evolution in OODBs Using Class Versioning. SIGMOD Record 1993; 22 (3). 16–22.CrossRefGoogle Scholar
  3. 3.
    Skarra, A H and SB Zdonik. The Management. of Changing Types in an Object-Oriented Database. In: OOPSLA’86. pp 483–495. 1986.Google Scholar
  4. 4.
    Björnerstedt, A and S Britts. AVANCE: An Object Management System. In: OOPSLA’86. pp 206–221. 1988.Google Scholar
  5. 5.
    Kim, H and H F Korth. Schema Versions and Views in Object-Oriented Databases. In: INFO Japan. pp 277–284. 1990.Google Scholar
  6. 6.
    Abiteboul, S and A Bonner. Objects and Views. SIGMOD Record 1991; 20 (2): 238–247.Google Scholar
  7. 7.
    Scholl, M H, C Laasch, and M Tresch. Updatable Views in Object-Oriented Databases. In Deductive and Object-Oriented Databases, 189–207. 1991.Google Scholar
  8. 8.
    Urban, S D and K Chalmers. An Investigation of the View Update Problem for Object-Oriented Views. In Computers and Communications, Phoenix, 156–163. 1992.Google Scholar
  9. 9.
    Monk, S R. The CLOSQL Query Language. Computing Dept, Lancaster University, Lancaster, LA1 4YR, UK, Internal Report Number SE-91–15. 1991.Google Scholar
  10. 10.
    Monk, S R and I Sommerville. A Model for Versioning of Classes in Object-Oriented Databases. In BNCOD 10, Aberdeen, ed. P M D Gray and R J Lucas, 42–58. Springer-Verlag. 1992.Google Scholar
  11. 11.
    Almarode, J. Issues in the Design and Implementation of a Schema Designer for an OODBMS. In ECOOP’91, Geneva, ed. P America, 200–218. Springer Verlag. 1991.Google Scholar
  12. 12.
    Deux, O et al. The O2 System. Comm. of the ACM 34 (10). 34–48. 1991CrossRefGoogle Scholar
  13. 13.
    Kim, W. Introduction to Object-Oriented Databases. The MIT Press. 1990.Google Scholar
  14. 14.
    Mariani, J A and R Lougher. Triplespace — An Experiment in a 3D Graphical Interface to a Binary Relational Database. Interacting with Computers 4 (2). 147–162. 1992.CrossRefGoogle Scholar
  15. 15.
    Keene, S E. Object-Oriented Programming in Common Lisp - A Programmers Guide to CLOS. Addison-Wesley. 1989.Google Scholar
  16. 16.
    Steele, G L. Common LISP — The Language. Second Edition, DIGITAL Press. 1990.MATHGoogle Scholar
  17. 17.
    Harlequin. LispWorks User Guide. Harlequin Ltd.,Barrington Hall, Barrington, Cambridge, CB2 5RG, UK, 1991.Google Scholar

Copyright information

© Springer-Verlag London 1995

Authors and Affiliations

  • Simon Monk
    • 1
  1. 1.Department of ComputingUniversity of Central LancashirePrestonUK

Personalised recommendations