Software maintainers often have to recover requirements traceability in old code. In other words, they need to answer the question: "In which parts of this program is functionality X implemented?" This paper proposes a methodology for answering this question based on the use of carefully designed test cases as probes into the code. While the methodology is not applicable to all kink of requirements and may not find all relevant code components, it should often provide a maintainer with good starting points for studying a large and poorly documented system. Two formulations of the methodology are suggested and some encouraging experimental results are presented from a case study of a typical old program.

No abstract

No abstract

No abstract

No abstract