Author(s)

S. Ajila, H. Basson & J.-C. Derniame

Abstract

Software maintenance is generally known to be time consuming and ex- pensive. One of the main reasons for this is that it is difficult for software engineers and analysts to understand fully a software system that they did not design or implement. Even when they develop their own system, it is easy to forget the details of the design or code developed at earlier stages. Some of the questions a software engineer may want to ask when making a change are : what other parts of the software must I change if I carry out this modification? who in the developing team must be informed of this modification? what other versions or configurations of the software system must I change? The

Keywords