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. © Springer-Verlag Berlin Heidelberg 2003.
|Title of host publication||Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)|Lect. Notes Comput. Sci.|
|Number of pages||17|
|Publication status||Published - 2003|