Adapting integrity enforcement techniques for data reconciliation
Information Systems - Data extraction, cleaning and reconciliation
Software Change Impact Analysis
Software Change Impact Analysis
A method for the manual extraction of business rules from legacy source code
BT Technology Journal
Extracting Business Rules from Information Systems
BT Technology Journal
Deriving Production Rules for Incremental View Maintenance
VLDB '91 Proceedings of the 17th International Conference on Very Large Data Bases
Production Rules in Parallel and Distributed Database Environments
VLDB '92 Proceedings of the 18th International Conference on Very Large Data Bases
Compiling a Declarative High-Level Language for Semantic Integrity Constraints
DS-6 Proceedings of the Sixth IFIP TC-2 Working Conference on Data Semantics: Database Applications Semantics
A Change Propagation Model and Platform For Multi-Database Applications
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Modularization with Externalization of Control Flow
ACoM '07 Proceedings of the First International Workshop on Assessment of Contemporary Modularization Techniques
Hi-index | 0.00 |
The ability of a business to change its working practices, in order to gain or retain competitive edge, is closely aligned to its ability to change the business rules implemented by its information systems. Unfortunately, adding a new business rule to an existing system is both time-consuming and error-prone. It is all too easy, for example, for the programmer to overlook some program elements that are affected by the addition of the new rule, with the result that it is not enforced uniformly by the system as a whole. When this happens, the information system can begin to behave in confusing and anomalous ways. In this paper, we describe an impact analysis technique that aims to support the programmer in the difficult task of implementing an important class of business rules, namely, integrity constraints. We have adapted techniques from database integrity maintenance to allow us to identify whether a program is likely to be affected by the addition of a new constraint, and to pinpoint the specific program statements that must be guarded against the possibility of constraint violation. Our technique can also be used to provide guidance to the programmer as to the conditions that must be included in any new guards.