In conjunction with the 31st International Conference on Software Engineering


The 5th International Workshop on Traceability in Emerging Forms of Software Engineering will host a traceability recovery challenge. The TEFSE Traceability Challenge brings together researchers and practitioners who are interested in applying, comparing, and challenging their traceability recovery tools and approaches on two small/medium size artefact repositories containing different types of artefacts (i.e., use cases, interaction diagrams, test cases, and interface description of code classes). Indeed, the artefacts contained in the two repositories describe the same system, namely EasyClinic, a system developed at the University of Salerno to manage a doctor's office. The difference between the two repositories is represented by the language of the artefacts. In particular, in the first repository the language is Italian, while English is the language of the artefacts in the second repository.

The challenge materials are available for download here.

The correct answers are available for download here.

The research questions addressed in the challenge are related to the recovery of traceability links between code (i.e., class descriptions) and documentation (i.e., use cases and test cases). In particular, the following research questions are of interest here:


Researchers and practitioners that want to participate need to send an email to or by March 2, 2009 specifying the following information in the email subject line:

TEFSE 2009 - TR Challenge: <First name> <Second name>

To participate in the challenge it is necessary to submit a report. The challenge report (maximum length of 2 pages) describes the proposed traceability recovery approach. Moreover, the two ranked lists (in an Excel format) of links recovered by the proposed approach, i.e., tracing classes onto use cases and tracing classes onto test cases will be also need to be submitted. The ranked list will be analyzed by the organizers in order to evaluate the accuracy, in terms of precision and recall, of the proposed traceability recovery method. The traceability matrix provided by the original developers will be used as oracle for evaluating the accuracy of the traceability recovery method.

Report submissions should be sent via email to or . Reports are due on May 11, 2009. For more details please send an email to one of the organizers.

The results of the challenge will be presented at the workshop in a dedicated session. The winner will be given the Traceability Recovery Challenge Award. Furthermore, we would like to encourage all challenge attendees to demo their methods and tools in this session or during coffee breaks.