2002 · 46 citations · 17 references
ComputingComputer ScienceKnowledge RepresentationMaintenance EngineeringSoftware EngineeringSoftware DesignSoftware MaintenanceCode ComprehensionLegacy Software MaintenanceMaintenance Request ManagementProgram ComprehensionSoftware Restructuring
Many legacy programs are so large and so complex that they cannot be comprehended in their entirety no matter what forms of representation are used. Yet these programs must be maintained. The contention of this paper is that it is not necessary to comprehend a program in order to maintain it. It is only necessary to comprehend those sectors affected by the maintenance request. Only seven questions are required to pinpoint and comprehend program sectors well enough to be able to alter them without undesired side effects. These questions and their answers are proposed in the following paper.
17
David Harel · Communications of the ACM · 1988 · 1.3K citations · Full text
Design recovery for maintenance and reuse
Ted J. Biggerstaff · Computer · 1989 · 363 citations
Computing, Design, Design Automation +13
Understanding function behaviors through program slicing
Andrea De Lucia, Anna Rita Fasolino, Malcolm Munro · 2002 · 142 citations