Maintaining Traceability During ObjectOriented Software Evolution a Case Study.pdfVIP

Maintaining Traceability During Object-Oriented Software Evolution: a Case Study G. Antoniol, G. Canfora, A. De Lucia University of Sannio, Faculty of Engineering Palazzo Bosco Lucarelli, Piazza Roma I-82100 Benevento, Italy antoniol@ fg.canfora,andrea.deluciag@unina.it Abstract es, methods). However, results are too coarse grained and very difficult to summarize, visualize and interpret. This paper presents an approach to build and visualize Our process works on a code intermediate representation traceability links and properties of a set of OO software re- that encompasses the essentials of the class diagram in an leases. The process recovers an “as is” design from C++ OO design description language, the Abstract Object Lan- T software releases, compares recovered designs at the class guage (AOL). The process recovers an “as is” design from interface level, and helps the user to deal with inconsis- the code in AOL, compares recovered design of subsequent tencies by pointing out regions of code where differences software releases, and helps the user to deal with inconsis- are concentrated. The comparison process exploits edit dis- tencies by pointing out regions of code which do not match tance and a maximum match algorithm and has been exper- i.e., added, deleted and modified classes and methods. imented with 9 releases of a library of foundation classes.