Capacity-Augmenting Schema Changes on Object-Oriented Databases: Towards Increased Interoperability

Rundensteiner, Elke A.; Lee, Amy J.; Ra, Young-Gook

doi:10.1007/978-1-4471-0895-5_22

Cited by 6 publications

(4 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Since each primitive element of FMs can be changed by one of the meta-change transformations (Huersch, 1997;Rundensteiner, Leem, & Ra, 1998), we suggest a set of primitive operations on FMs in Table 2 (Guo & Wang, 2010). These operations are defined by the cross product of the set of FM primitive elements and the set of meta-changes ('Add', 'Remove', and 'Set').…”

Section: Changes To Feature Modelsmentioning

confidence: 99%

Consistency maintenance for evolving feature models

Guo

Wang

Trinidad

et al. 2012

Expert Systems with Applications

View full text Add to dashboard Cite

a b s t r a c tSoftware product line (SPL) techniques handle the construction of customized systems. One of the most common representations of the decisions a customer can make in SPLs is feature models (FMs). An FM represents the relationships among common and variable features in an SPL. Features are a representation of the characteristics in a system that are relevant to customers.FMs are subject to change since the set of features and their relationships can change along an SPL lifecycle. Due to this evolution, the consistency of FMs may be compromised. There exist some approaches to detect and explain inconsistencies in FMs, however this process can take a long time for large FMs.In this paper we present a complementary approach to dealing with inconsistencies in FM evolution scenarios that improves the performance for existing approaches reducing the impact of change to the smallest part of an FM that changes. To achieve our goal, we formalize FMs from an ontological perspective and define constraints that must be satisfied in FMs to be consistent. We define a set of primitive operations that modify FMs and which are responsible for the FM evolution, analyzing their impact on the FM consistency. We propose a set of predefined strategies to keep the consistency for error-prone operations.As a proof-of-concept we present the results of our experiments, where we check for the effectiveness and efficiency of our approach in FMs with thousands of features. Although our approach is limited by the kinds of consistency constraints and the primitive operations we define, the experiments present a significant improvement in performance results in those cases where they are applicable.

show abstract

Section: Changes To Feature Modelsmentioning

confidence: 99%

Consistency maintenance for evolving feature models

Guo

Wang

Trinidad

et al. 2012

Expert Systems with Applications

View full text Add to dashboard Cite

show abstract

“…As a result of an information capacity-reducing or preserving schema change, some new derived specifications can be defined. Therefore, in addition to including the definition of the new external schema in the repository, it will have to include the definition of the new derived specifications ( Figure 1.b) since, as mentioned previously and unlike other systems (Ra et al, 1997;Rundensteiner et al, 1998), the derived specifications are not included in the conceptual schema.…”

Section: Information Capacity-reducing or Preserving Schema Changesmentioning

confidence: 99%

“…In Rundensteiner et al (1998), a methodology to achieve transparent schema changes and that does not require information capacity-augmenting views is presented. In this methodology, when it is necessary to modify the base schema because an information capacity-augmenting schema change is required, the former base schema is reconstructed as a view schema from the augmented base schema in order to continue supporting all the existing view schemas.…”

Section: Related Workmentioning

confidence: 99%

An Approach for Schema Evolution in Odmg Databases

Delgado¹,

Samos²,

Torres³

2004

Proceedings of the 4th International Workshop on Pattern Recognition in Information Systems

View full text Add to dashboard Cite

Schema evolution is the process of applying changes to a schema in a consistent way and propagating these changes to the instances while the database is in operation. However, when a database is shared by many users, updates to the database schema are always difficult. To overcome this problem, in this paper we propose a version mechanism for schema evolution in ODMG databases that preserves old schemas for continued support of existing programs running on the shared database when schema changes are produced. Our approach uses external schema definition techniques and is based on the fact that if a schema change is requested on an external schema, rather than modifying the schema, a new schema, which reflects the semantics of the schema change, is defined.

show abstract

“…In transparent schema evolution systems [17,18,21], each user 3 constructs a customized interface by selecting a subset of classes from the shared database. All the schema change requests made by the developer are issued against her customized view schema with which she is familiar (Figure 1(a)).…”

Section: The Tse System: Problem Descriptionmentioning

confidence: 99%

Consistent schema version removal: an optimization technique for object-oriented views

Crestana-Jensen

Lee²,

Rundensteiner³

2000

IEEE Trans. Knowl. Data Eng.

View full text Add to dashboard Cite

Powerful solutions enabling interoperability must allow applications to evolve and requirements of shared databases to change, while minimizing such changes on other integrated applications. Several approaches, such as the transparent schema evolution system (TSE) by Ra et al., schema versions by Lautemann, and integrated views by Bertino, have been proposed to make interoperability possible by using object-oriented techniques. These approaches may generate a large number of schema versions over time resulting in an excessive build-up of classes and underlying object instances, not all being necessarily still in use. This results in degradation of system performance due to the view maintenance and the storage overhead costs. In this paper, we address the problem of removing obsolete view schemas. We characterize four potential problems of schema consistency that could be caused by removal of a single derived class. We demonstrate that schema version removal is sensitive to the order in which individual classes are processed, and present a formal dependency model that captures all dependencies between classes as logic clauses and manipulates them to make decisions on class deletions and non-deletions while guaranteeing the consistency of the schema. We have also developed and proven consistent a dependency graph (DG) representation of the formal model. Lastly, we present a cost model for evaluating alternative removal patterns on DG to assure selection of the optimal solution. The proposed techniques have been implemented in our Schema View Removal (SVR) tool. Lastly, we report experimental findings for applying our techniques for consistent schema version removal on the MultiView/TSE system.

show abstract

Capacity-Augmenting Schema Changes on Object-Oriented Databases: Towards Increased Interoperability

Cited by 6 publications

References 16 publications

Consistency maintenance for evolving feature models

Consistency maintenance for evolving feature models

An Approach for Schema Evolution in Odmg Databases

Consistent schema version removal: an optimization technique for object-oriented views

Contact Info

Product

Resources

About