Design And Implementation Of Database Change Impact Analyzing Based On Program Slicing

Nowadays, as the software scale enlarging and the requirement changing frequently, to develop software becomes more and more complex. The idea of Agile Programming reduces the workload for developers in a certain way. But when the schema of database on which application relies changes, developers always have to investigate all code to find where the code needs to be changed to work with the new database schema because there is no mature technology to support such changes. This is no doubt a complex and time-consuming work. Besides, it is very possible to make mistakes or miss some changes because of the heavy workload.As research in this area is not sufficient, this paper describes a solution to analyze impact on application when database schema changes after investigates lots of literatures and papers. In this solution, firstly we extract schema information of database on which application relies, including information of tables, attributes, and constraints between attributes. Secondly, we by monitoring source code of the application, we extract information of the software, including information of classes and sentences in class which have some relationship with database operation, including code where SQLs are defined, executed, and where the SQLs are used. Then we compute where the application is impacted according to the database schema change scripts. Finally, we make a scenario in which database schema is changed to verify how accuracy can this case compute the impact analysis on applications when database schema got changed.This paper brings the concept of program slicing to ripple analysis area, and realizes a system to compute impact to applications when database schema on which the application rely changes. Firstly, current related research in this area is introduced, and requirement is defined based on the research. Then we design slicing rules and algorithm to extract key information from application source code, and design rules to compute impact on applications when database schema gets changed. Finally, we verify the function and ease-to-use of this system through a real scenario.