A model for Assembly program maintenance
Journal of Software Maintenance: Research and Practice
A reverse engineering model for C programs
Information Sciences: an International Journal
Journal of Software Maintenance: Research and Practice
Re-engineering legacy Cobol programs
Communications of the ACM
Data-Centered Program Understanding
ICSM '94 Proceedings of the International Conference on Software Maintenance
Omega - an integrated environment for C++ program maintenance
ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
Business Rule Extraction from Legacy Code
COMPSAC '96 Proceedings of the 20th Conference on Computer Software and Applications
Ensuring System and Software Reliability in Safety-Critical Systems
ASSET '98 Proceedings of the 1998 IEEE Workshop on Application - Specific Software Engineering and Technology
Hi-index | 0.00 |
The data-centered approach uses variable classifications, dependence analysis, generalised program slicing and ripple effect analysis. In the Year 2000 problem, this approach can be useful. Variable classification is used to identify all input and output variables, and once the initial set of variables that are Year 2000 related is identified, dependence analysis can be used to identify all the variables that are potentially affected by the initial set of variables. The second set of variables is then examined to see if they are Year 2000 related. This process is repeated until all the Year 2000 related variables are identified. This process is essentially ripple effect analysis and uses generalized program slicing and dependence analysis. Once Year 2000 related variables are identified, generalized program slicing is performed to identify all the statements that potentially need to be changed. Once a statement is changed, it may induce additional changes. Ripple effect analysis can be used to ensure that all the parts that need to modified are examined. Finally, the changed software should be validated and regression testing can be used in this stage. Ripple effect analysis can be used in this stage by identifying the relevant test cases that needed to evaluated. This is done by maintaining traceability links between the software and its test cases.