Unified class evolution by object-oriented views

Bratsberg, Svein Erik

doi:10.1007/3-540-56023-8_26

Cited by 25 publications

(10 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In addition, unlike the database conversion, it is not possible to migrate all the conversations to the new protocol. Instead of the conversion technique, if we adopt the approach of simulating the schema evolution by object-oriented views [Bratsberg 1992;Tresch and Scholl 1993], which enables different applications to use different views (seen as different schemas), there is no need for conversion. However, applying this approach to the protocol evolution causes a similar problem, like the case of class versioning.…”

Section: Database Schema Evolutionmentioning

confidence: 99%

Supporting the dynamic evolution of Web service protocols in service-oriented architectures

Ryu

Casati

Skogsrud³

et al. 2008

ACM Trans. Web

View full text Add to dashboard Cite

In service-oriented architectures, everything is a service and everyone is a service provider. Web services (or simply services) are loosely coupled software components that are published, discovered, and invoked across the Web. As the use of Web service grows, in order to correctly interact with them, it is important to understand the business protocols that provide clients with the information on how to interact with services. In dynamic Web service environments, service providers need to constantly adapt their business protocols for reflecting the restrictions and requirements proposed by new applications, new business strategies, and new laws, or for fixing problems found in the protocol definition. However, the effective management of such a protocol evolution raises critical problems: one of the most critical issues is how to handle instances running under the old protocol when it has been changed. Simple solutions, such as aborting them or allowing them to continue to run according to the old protocol, can be considered, but they are inapplicable for many reasons (for example, the loss of work already done and the critical nature of work). In this article, we present a framework that supports service managers in managing the business protocol evolution by providing several features, such as a variety of protocol change impact analyses automatically determining which ongoing instances can be migrated to the new version of protocol, and data mining techniques inferring interaction patterns used for classifying ongoing instances migrateable to the new protocol. To support the protocol evolution process, we have also developed

show abstract

Section: Database Schema Evolutionmentioning

confidence: 99%

Supporting the dynamic evolution of Web service protocols in service-oriented architectures

Ryu

Casati

Skogsrud³

et al. 2008

ACM Trans. Web

View full text Add to dashboard Cite

show abstract

“…A literature review showed that as in the case of relational databases the view mechanism can be applied to object-oriented ones to cope with schema changes [2], [3], [4]. The prime tool for view support in relational and object-oriented databases is mapping [5], [6], [7], [8].…”

Section: E Sustaining Changesmentioning

confidence: 99%

Enabling enterprise composite applications on top of ERP systems

Borovskiy

Zeier

2009

2009 IEEE Asia-Pacific Services Computing Conference (APSCC)

View full text Add to dashboard Cite

Along with benefits of ERP system companies experience high costs associated to them. Setting up and maintaining the infrastructure and adjusting standard ERP software to a specific customers requirements drive the costs of such systems. To lower the total cost of ownership companies employ software as a service (SaaS) paradigm: instead of owning software they subscribe to it. However, this does not reduce customization costs. To address specific requirements companies develop custom applications on top of their ERP systems. The challenge with this extension approach is that most ERP systems have poorly designed APIs and developing a composite application on top of such system becomes a difficult exercise. In this paper we propose an architecture of an ERP system that supports simple and fast development of composite applications on top of it. We define five requirements towards such an architecture and show how the requirements are satisfied by the proposed architecture. Our proposal emphasizes the importance of ERP data accessibility and contributes with a concept of business object query language that allows building fine-grained queries. All suggestions made in the paper have been prototyped.

show abstract

“…We can consider such interpretation to be a generalization of the interpretation in ordinary support for views; we map operations and data between two definitions [Sockut 1985, pp. 17-18;Bratsberg 1992;.…”

Section: Strategies For Online Logical Redefinitionmentioning

confidence: 99%

Online reorganization of databases

Sockut

Iyer

2009

ACM Comput. Surv.

View full text Add to dashboard Cite

In practice, any database management system sometimes needs reorganization, that is, a change in some aspect of the logical and/or physical arrangement of a database. In traditional practice, many types of reorganization have required denying access to a database (taking the database offline) during reorganization. Taking a database offline can be unacceptable for a highly available (24-hour) database, for example, a database serving electronic commerce or armed forces, or for a very large database. A solution is to reorganize online (concurrently with usage of the database, incrementally during users' activities, or interpretively). This article is a tutorial and survey on requirements, issues, and strategies for online reorganization. It analyzes the issues and then presents the strategies, which use the issues. The issues, most of which involve design trade-offs, include use of partitions, the locus of control for the process that reorganizes (a background process or users' activities), reorganization by copying to newly allocated storage (as opposed to reorganizing in place), use of differential files, references to data that has moved, performance, and activation of reorganization. The article surveys online strategies in three categories of reorganization. The first category, maintenance, involves restoring the physical arrangement of data instances without changing the database definition. This category includes restoration of clustering, reorganization of an index, rebalancing of parallel or distributed data, garbage collection for persistent storage, and cleaning (reclamation of space) in a logstructured file system. The second category involves changing the physical database definition; topics include construction of indexes, conversion between B + -trees and linear hash files, and redefinition (e.g., splitting) of partitions. The third category involves changing the logical database definition. Some examples are changing a column's data type, changing the inheritance hierarchy of object classes, and changing a relationship from one-to-many to many-to-many. The survey encompasses both research and commercial implementations, and this article points out several open research topics. As highly available or very large databases continue to become more common and more important in the world economy, the importance of online reorganization is likely to continue growing.

show abstract

Unified class evolution by object-oriented views

Cited by 25 publications

References 9 publications

Supporting the dynamic evolution of Web service protocols in service-oriented architectures

Supporting the dynamic evolution of Web service protocols in service-oriented architectures

Enabling enterprise composite applications on top of ERP systems

Online reorganization of databases

Contact Info

Product

Resources

About