A method for the identification of reusable units through the reengineering of legacy code
Journal of Systems and Software
Software Maintenance Management
Software Maintenance Management
Analysing Large COBOL Programs: the extraction of reusable modules
ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
Finding Components in a Hierarchy of Modules: a Step towards Architectural Understanding
ICSM '97 Proceedings of the International Conference on Software Maintenance
Reengineering Support for Software Evolution: An Evaluation through Case Study
COMPSAC '98 Proceedings of the 22nd International Computer Software and Applications Conference
Extracting Reusable Modules from Legacy Code: considering the issues of module granularity
WCRE '96 Proceedings of the 3rd Working Conference on Reverse Engineering (WCRE '96)
The Implications of Non-functional Requirements for the Reengineering of Legacy Code
WCRE '97 Proceedings of the Fourth Working Conference on Reverse Engineering (WCRE '97)
Identifying objects in legacy systems
WPC '97 Proceedings of the 5th International Workshop on Program Comprehension (WPC '97)
Enriching Program Comprehension for Software Reuse
WPC '97 Proceedings of the 5th International Workshop on Program Comprehension (WPC '97)
Investigating the Maintenance Implications of the Replication of Code
ICSM '97 Proceedings of the International Conference on Software Maintenance
ICSM '98 Proceedings of the International Conference on Software Maintenance
Moral Dominance Relations for Program Comprehension
IEEE Transactions on Software Engineering
Hi-index | 0.00 |
This paper will address how program comprehension can be aided within software maintenance through the use of high level representations of code, specifically the use of dominance trees. The paper proposes that dominance trees should be used as a standard approach within the program comprehension process. A number of ways in which the dominance trees are supportive of the comprehension process are highlighted. The evaluation considers if dominance trees are supportive of standard program comprehension strategies such as an as‐needed strategy, whether they provide an early identification of the consequences of changes and highlight areas where preventative maintenance is necessary. Their actual usefulness in achieving these goals is evaluated through the use of a number of case studies. The results have shown that there are a number of specific tasks performed during program comprehension that can be aided through the use of dominance trees.