Make the Most of Your Time: How Should the Analyst Work with Automated Traceability Tools?
Authors:
- 1 May 2007
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 4
Abstract
Several recent studies employed traditional information retrieval (IR) methods to assist in the mapping of elements of software engineering artifacts to each other. This activity is referred to as candidate link generation because the final say in determining the final mapping belongs to the human analyst. Feedback techniques that utilize information from the analyst (on whether the candidate links are correct or not) have been shown to improve the quality of the mappings. Yet the analyst is making an investment of time in providing the feedback. This leads to the question of whether or not guidance can be provided to the analyst on how to best utilize that time. This paper simulates a number of approaches an analyst might take to evaluating the same candidate link list, and discovers that more structured and organized approaches appear to save time/effort of the analyst.Keywords
This publication has 10 references indexed in Scilit:
- The Strangest Thing About SoftwareComputer, 2007
- Humans in the traceability loop2005
- Baselines in requirements tracing2005
- Text mining for software engineering2005
- Improving requirements tracing via information retrieval2004
- Automating speculative queries through event-based requirements traceability2003
- Recovering code to documentation links in OO systems2003
- Recovering documentation-to-source-code traceability links using latent semantic indexing2003
- An analysis of the requirements traceability problem2002
- Recovering traceability links between code and documentationIEEE Transactions on Software Engineering, 2002