Complex object versioning

Oussalah, C.; Urtado, Christelle

doi:10.1007/3-540-63107-0_19

Cited by 5 publications

(3 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…An object is said to be statically bound if it uses a direct reference to a specific version of its component objects (Ahmed and Navathe, 1991;Krishnamurthy and Law, 1995;Oussalah and Urtado, 1997;Andonoff et al, 1996;Santoyridis et al, 1997;Kafer and Schoning, 1992). On the other hand, if an object refers to the generic version of a constituent object instead of a specific version of that object then it is said to be dynamically bound (Kim et al, 1989(Kim et al, , 1991Sciore, 1994;Dittrich and Lorie, 1988;Carnduff, 1993;Katz, 1990).…”

Section: Introductionmentioning

confidence: 98%

Configuration management in evolutionary engineering design using versioning and integrity constraints

Carnduff

Goonetillake²

2004

Advances in Engineering Software

View full text Add to dashboard Cite

Section: Introductionmentioning

confidence: 98%

Configuration management in evolutionary engineering design using versioning and integrity constraints

Carnduff

Goonetillake²

2004

Advances in Engineering Software

View full text Add to dashboard Cite

“…However, it regarded a diagram as a graph consisting of nodes and edges and it did not consider logical properties specific to the diagrams. The techniques to calculate differences on XML [20] and on complex objects [17] were studied. However, they did not discuss the flexible variation of the logical components that should be targets of version control.…”

Section: Introductionmentioning

confidence: 99%

Meta-Modeling Based Version Control System for Software Diagrams

Oda¹

2006

IEICE Transactions on Information and Systems

View full text Add to dashboard Cite

In iterative software development methodology, a version control system is used in order to record and manage modification histories of products such as source codes and models described in diagrams. However, conventional version control systems cannot manage the models as a logical unit because the systems mainly handle source codes. In this paper, we propose a version control technique for handling diagrammatical models as logical units. Then we illustrate the feasibility of our approach with the implementation of version control functions of a meta-CASE tool that is able to generate a modeling tool in order to deal with various diagrams.

show abstract

“…Note that object versioning is an essential requirement in complex applications such as CAD, etc., where there is often a need to create new versions of an object from its existing single or multiple versions. Work has been carried out to provide versioning support for objects residing in object-oriented databases [2,3,[19][20][21][22][23]. However, these all concentrate on version modelling and workgroup support and tend to lose sight of the global pictureevolution.Our approach, in contrast to those above, views evolution as a process which affects the whole database and, therefore, concentrates on database evolution.…”

mentioning

confidence: 99%

A database evolution taxonomy for object-oriented databases

Rashid

Sawyer

2005

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

Like any other database application, object database applications are subject to evolution. Evolution, however, is a critical requirement in object-oriented databases as it is a fundamental characteristic of complex applications such as computer-aided design and manufacturing (CAD/CAM) and office information systems. Object-oriented databases are inherently suited to supporting such applications. In this paper we present a database evolution taxonomy for object-oriented databases. We describe a conceptual database model and use it to define the taxonomy. We also present the various invariants and rules governing the various evolution operations. The execution sequence of rules is described. An implementation of the database model and the evolution taxonomy in the Semi-Autonomous Database Evolution System (SADES), is discussed. The implementation employs aspect-oriented programming techniques to provide a flexible means of transforming objects upon evolution, and implementing some application-specific evolution primitives. A case study compares the evolution taxonomy with existing evolution approaches. The comparison demonstrates that the taxonomy and its corresponding implementation in SADES provide improved coverage of the fundamental evolution operations to which an object database might be subjected. At the same time, erosion of the database structure is avoided by maintaining a coherent and comprehensible view of historical changes. A. RASHID AND P. SAWYER• to correct mistakes in the database design; • to add new features during incremental design; and • to reflect changes in the structure of the real-world artefacts modelled in the database. Therefore, like any other database application, object database applications are subject to evolution.However, evolution is a critical requirement in object-oriented databases because their inherent support for complex data types makes them highly suitable for supporting complex applications such as computer-aided design and manufacturing (CAD/CAM) and office information systems. Due to the underlying rich data model (in contrast with conventional data-intensive record-processing applications), these applications require dynamic modifications to both the data residing within the database and the way the data has been modelled, i.e., both the objects residing within the database and the schema of the database are subject to change. Furthermore, there is a requirement to keep track of the change in case it needs to be reverted. Therefore, in addition to offering traditional database functionality such as persistence, transaction management, recovery and querying facilities, an objectoriented database management system needs to provide the ability to evolve dynamically, through various versions, both the objects and the class definitions (which form the database schema) in the database.An object database is, therefore, subject to three types of changes over its lifetime.• Class hierarchy modification: introduction of new classes, deletion of existing classes and modificatio...

show abstract

Complex object versioning

Cited by 5 publications

References 10 publications

Configuration management in evolutionary engineering design using versioning and integrity constraints

Configuration management in evolutionary engineering design using versioning and integrity constraints

Meta-Modeling Based Version Control System for Software Diagrams

A database evolution taxonomy for object-oriented databases

Contact Info

Product

Resources

About