Humans in the traceability loop: can't live with 'em, can't live without 'em

The human analyst is required as an active participant in the trace-ability process. Work to date has focused on automated methods that generate traceability information. There is a need for study of what the analysts do with traceability information as well as a study of how they make decisions.

[1]  Giuliano Antoniol,et al.  Recovering Traceability Links between Code and Documentation , 2002, IEEE Trans. Software Eng..

[2]  Jane Huffman Hayes,et al.  Improving requirements tracing via information retrieval , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[3]  Jane Huffman Hayes,et al.  Baselines in requirements tracing , 2005, PROMISE '05.

[4]  Tim Menzies,et al.  Text is Software Too , 2004, MSR.

[5]  Andrian Marcus,et al.  Recovering documentation-to-source-code traceability links using latent semantic indexing , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[6]  Jane Huffman Hayes,et al.  Helping analysts trace requirements: an objective look , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[7]  Oussama Ben Khadra,et al.  Goal-centric traceability for managing non-functional requirements , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[8]  Jane Huffman Hayes,et al.  Text mining for software engineering: how analyst feedback impacts final results , 2005, MSR '05.