Tracing all around

Abstract

Many information systems are reengineered and redeveloped in practice, since they are legacy software. Typically, no requirements and design specifications exist and, therefore, also no traceability information. While especially the long-term utility of such information is well known, an important question in reengineering is whether installing it can have immediate benefits in the course of the reengineering effort. Are there even special benefits of traceability for reengineering? In this paper, we argue for completely tracing all around from code over specifications to code in the course of reverse engineering an existing software system and its subsequent redesign and redevelopment. Experience from a realworld project indicates that it can indeed be useful in practice to provide traceability all around also for the developers and in terms of short-term benefits already during the development. We found several cases where traceability provided benefits that appear to be specific for reengineering. As a consequence, we recommend special emphasis on traceability during reengineering legacy software.