Results 1 - 10
of
15
Strategy for database application evolution: The DB-MAIN approach
- In Proc. ER’03, volume 2813 of LNCS
, 2003
"... Abstract. While recent data management technologies, e.g., object-oriented, address the problem of databases schema evolution, standard information systems currently in use raise challenging problems when evolution is concerned. This paper studies database evolution from the developer point of view. ..."
Abstract
-
Cited by 8 (1 self)
- Add to MetaCart
Abstract. While recent data management technologies, e.g., object-oriented, address the problem of databases schema evolution, standard information systems currently in use raise challenging problems when evolution is concerned. This paper studies database evolution from the developer point of view. It shows how requirements changes are propagated to the database schemas, to the data and to the programs through a general strategy. This strategy requires the documentation of the database design. When absent, this documentation has to be rebuilt through reverse engineering techniques. The approach relies on a generic database model and on the transformational paradigm that states that database engineering processes can be modelled by schema transformations. Indeed, a transformation provides both structural and instance mappings that formally define how to modify database structures and contents. The paper then analyses the problem of program modification and describes a CASE tool that can assist developers in their task of system evolution. 1
Recovering data models via guarded dependences
- In Proc. WCRE
, 2007
"... All in-text references underlined in blue are linked to publications on ResearchGate, letting you access and read them immediately. ..."
Abstract
-
Cited by 8 (1 self)
- Add to MetaCart
(Show Context)
All in-text references underlined in blue are linked to publications on ResearchGate, letting you access and read them immediately.
Using Grid Technologies for Web-enabling Legacy Systems
- in Proceedings of the Software Technology and Engineering Practice (STEP), The workshop Software Analysis and Maintenance: Practices, Tools, Interoperability
, 2003
"... The adoption of the Internet technologies favors the diffusion of Web and Grid-based applications. However, the development of new applications exploiting the modern interfaces and distribution channels have to face the problems connected with the integration of existing software systems. This aspec ..."
Abstract
-
Cited by 7 (0 self)
- Add to MetaCart
(Show Context)
The adoption of the Internet technologies favors the diffusion of Web and Grid-based applications. However, the development of new applications exploiting the modern interfaces and distribution channels have to face the problems connected with the integration of existing software systems. This aspect often requires the migration of legacy systems toward the Web technologies. In fact, they cannot be simply discarded as they are very important for the business they support and because they encapsulate a great deal of knowledge and expertise about the application domain. Many migration strategies have been proposed in the literature. Many of them are referred to decomposable and/or semi-decomposable software systems where the interface component is separated from the business logic and the data model components. In this case, the interface component can be re-implemented, while the other ones are encapsulated into a software wrapper. Unfortunately, the legacy systems are very often non-decomposable. It is necessary to apply strategies that work also leaving unchanged the control flow of the legacy system and allowing its integration with Web and Grid environments. This paper proposes a solution using Web and Grid technologies for migrating Cobol software systems with character-based user interface. 1.
Database Wrappers Development: Towards Automatic Generation
"... Wrapping databases allows them to be reused in formerly unplanned contexts, such as web-based applications or federated systems. Indeed, a wrapper can provide external clients of an existing (legacy) database with a neutral interface and augmented capabilities. However, except in simplistic cases wh ..."
Abstract
-
Cited by 6 (1 self)
- Add to MetaCart
Wrapping databases allows them to be reused in formerly unplanned contexts, such as web-based applications or federated systems. Indeed, a wrapper can provide external clients of an existing (legacy) database with a neutral interface and augmented capabilities. However, except in simplistic cases where the wrapper and the database schemas are similar, the wrapper must implement complex mappings: it must translate queries from the wrapper data manipulation language to the database primitives, and, conversely, translate extracted data into the external wrapper format. We have developed a generic schema mapping framework in which wrappers can be specified formally and generated automatically. This framework comprises a highlevel generic data model and a set of schema transformations defined for this model. This reference model makes it possible to specify different data models in a uniform formalism. Mappings between schemas are expressed as sequences of reversible schema transformations. We show how these transformations can be used to translate data and queries between two schemas and hence to generate as much as possible of the code of the wrappers. The generation is supported by DB-MAIN, a wide-spectrum CASE tool.
Wrapper-based evolution of legacy information systems
- ACM Trans. Softw. Eng. Methodol
"... System evolution most often implies the integration of legacy components, such as databases, with newly developed ones, leading to mixed architectures that suffer from severe heterogeneity problems. For instance, incorporating a new program in a legacy database application can create an integrity mi ..."
Abstract
-
Cited by 5 (0 self)
- Add to MetaCart
System evolution most often implies the integration of legacy components, such as databases, with newly developed ones, leading to mixed architectures that suffer from severe heterogeneity problems. For instance, incorporating a new program in a legacy database application can create an integrity mismatch, since the database model and the program data view can be quite different (e.g. standard file model versus OO model). In addition, neither the legacy DBMS (too weak to address integrity issues correctly) nor the new program (that relies on data server responsibility) correctly cope with data integrity management. The component that can reconciliate these mismatched subsystems is the R/W wrapper, which allows any client program to read, but also to update the legacy data, while controlling the integrity constraints that are ignored by the legacy DBMS. This article describes a generic, technology-independent, R/W wrapper architecture, a method-ology for specifying them in a disciplined way, and a CASE tool for generating most of the corre-sponding code. The key concept is that of implicit construct, which is a structure or a constraint that has not been declared in the database, but which is controlled by the legacy application code. The implicit constructs are elicited through reverse engineering techniques, and then translated into validation
Distribution public Knowledge Web Consortium
, 2007
"... D2.1.2.2.v2 Report on realizing practical approximate and distributed reasoning for ontologies Pascal Hitzler (Universität Karlsruhe) (coordinator) ..."
Abstract
- Add to MetaCart
D2.1.2.2.v2 Report on realizing practical approximate and distributed reasoning for ontologies Pascal Hitzler (Universität Karlsruhe) (coordinator)
An approach for mining services in database–oriented applications
"... The diffusion of service oriented architectures is slowed down by the lack of enough services available for satisfying service integrator needs. Nevertheless, many features desired by service integrators have already been implemented in existing software systems. To this aim, approaches able to iden ..."
Abstract
- Add to MetaCart
(Show Context)
The diffusion of service oriented architectures is slowed down by the lack of enough services available for satisfying service integrator needs. Nevertheless, many features desired by service integrators have already been implemented in existing software systems. To this aim, approaches able to identify potential services into a legacy system source code are highly desirable. This paper proposes an approach to identify, from database–oriented applications, pieces of functionality to be potentially exported as services. The identification is performed by clustering, through formal concept analysis, queries dynamically extracted by observing interactions between the application and the database. The approach has been assessed by identifying potential services in two Java software systems. Keywords: service mining, migration towards SOA, Formal Concept Analysis 1
Updating Legacy Databases through Wrappers: Data Consistency Management
- WCRE PROCEEDINGS
, 2004
"... Wrapping databases allows them to be reused in earlier unforeseen contexts, such as Web-based applications or federated systems. Data wrappers, and more specifically updating wrappers (that not only access legacy data but also update them), can provide external clients of an existing (legacy) databa ..."
Abstract
- Add to MetaCart
Wrapping databases allows them to be reused in earlier unforeseen contexts, such as Web-based applications or federated systems. Data wrappers, and more specifically updating wrappers (that not only access legacy data but also update them), can provide external clients of an existing (legacy) database with a neutral interface and augmented capabilities. For instance, a collection of COBOL files can be wrapped in order to allow external application programs to access them through a relational, object-oriented or XML interface, while providing referential integrity control. In this paper, we explore the principles of a wrapper architecture that addresses the problems of legacy data consistency management. The transformational paradigm is used as a rigorous formalism to define schema mappings as well as to generate as much as possible of the code of the wrappers. The generation is supported by an operational CASE tool.
Information Technology and Management Special issue on Information Sharing across Multiple Organizations INFORMATION SHARING ACROSS MULTIPLE HUMANITARIAN ORGANIZATIONS – A WEB-BASED INFORMATION EXCHANGE PLATFORM FOR PROJECT REPORTING
"... Abstract. This article analyzes information sharing problems in the humanitarian development sector and proposes the concept of a web-based exchange platform to face some of the technical challenges. The “Development Information Exchange System ” is a mediator-wrapper-architecture that uses XML docu ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract. This article analyzes information sharing problems in the humanitarian development sector and proposes the concept of a web-based exchange platform to face some of the technical challenges. The “Development Information Exchange System ” is a mediator-wrapper-architecture that uses XML documents to loosely couple autonomous and heterogeneous information systems. Detailed project information of humanitarian organizations that resides on data provider systems can be formatted with XSL stylesheets according to the needs of the users and shared within or between organizations. The system can help to close the control loop by providing qualitative information about humanitarian projects. This makes project management more efficient. The proposed architecture solves an interface problem between the various partners and stakeholders of humanitarian projects. It is a first step towards a service-oriented architecture between humanitarian organizations. The next step could be the definition of cross-organizational business processes. These processes may be defined platform-independently with the Business Process Execution Language for Web Services. A prototype of the exchange platform is presented and evaluated in this article. Keywords: loosely coupled information systems, XML-based project reporting,
