How do we trace requirements: an initial study of analyst behavior in trace validation tasks

Authors:
Wei-Keat Kong;Jane Huffman Hayes;Alex Dekhtyar;Jeff Holden
Affiliations:
University of Kentucky, Lexington, KY, USA;University of Kentucky, Lexington, KY, USA;California Polytechnic State University, San Luis Obispo, CA, USA;California Polytechnic State University, San Luis Obispo, CA, USA
Venue:
Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering
Year:
2011

Citing 12
Cited 5

Hints for Reviewing Empirical Work in Software Engineering

Empirical Software Engineering
Recovering Traceability Links between Code and Documentation

IEEE Transactions on Software Engineering
Automating Speculative Queries through Event-Based Requirements Traceability

RE '02 Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering
Recovering documentation-to-source-code traceability links using latent semantic indexing

Proceedings of the 25th International Conference on Software Engineering
Improving Requirements Tracing via Information Retrieval

RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
Text mining for software engineering: how analyst feedback impacts final results

MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
Humans in the traceability loop: can't live with 'em, can't live without 'em

TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods

IEEE Transactions on Software Engineering
Make the Most of Your Time: How Should the Analyst Work with Automated Traceability Tools?

ICSEW '07 Proceedings of the 29th International Conference on Software Engineering Workshops
Effort and Quality of Recovering Requirements-to-Code Traces: Two Exploratory Experiments

RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference
Automated Requirements Traceability: The Study of Human Analysts

RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference
Towards overcoming human analyst fallibility in the requirements tracing process (NIER track)

Proceedings of the 33rd International Conference on Software Engineering

Towards a model of analyst effort for traceability research

Proceedings of the 6th International Workshop on Traceability in Emerging Forms of Software Engineering
Observations on the connectedness between requirements-to-code traces and calling relationships for trace validation

ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Code patterns for automatically validating requirements-to-code traces

Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering
Departures from optimality: understanding human analyst's information foraging in assisted requirements tracing

Proceedings of the 2013 International Conference on Software Engineering
Enhancing software artefact traceability recovery processes with link count information

Information and Software Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

Traceability recovery is a tedious, error-prone, person-power intensive task, even if aided by automated traceability tools. Human analysts must vet candidate traceability links retrieved by such tools and must often go looking for links that such tools fail to locate as they build a traceability matrix. This paper examines a research version of the traceability tool REquirements TRacing On target (RETRO) that logs analyst actions. We examine the user logs in order to understand how analysts work on traceability recovery tasks. Such information is a pre-requisite to understanding how to better design traceability tools to best utilize analyst time while developing a high quality final traceability matrix.