Supporting Systems Development by Capturing Deliberations During Requirements Engineering
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Adapting traceability environments to project-specific needs
Communications of the ACM
A three-faceted view of information systems
Communications of the ACM
Semiautomatic generation of glossary links: a practical solution
Proceedings of the tenth ACM Conference on Hypertext and hypermedia : returning to our diverse roots: returning to our diverse roots
Requirements traceability: Theory and practice
Annals of Software Engineering
A practical approach to combining requirements definition and object-oriented analysis
Annals of Software Engineering
Reverse Engineering and Design Recovery: A Taxonomy
IEEE Software
An Object-Oriented Tool for Tracing Requirements
IEEE Software
Combining Goals and Functional Requirements in a Scenario-based Design Process
HCI '98 Proceedings of HCI on People and Computers XIII
Bridging the Gap Between Past and Future in RE: A Scenario-Based Approach
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Extended Requirements Traceability: Results of an Industrial Case Study
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
| Hi-index | 0.00 |
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 real-world 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.