How do we trace requirements? An initial study of analyst behavior in trace validation tasks

Wei Keat Kong, Jane Huffman Hayes, Alex Dekhtyar, Jeff Holden

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

12 Scopus citations

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.

Original languageEnglish
Title of host publicationCHASE 2011 - Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering, Co-located with ICSE 2011
Pages32-39
Number of pages8
ISBN (Electronic)9781450305761
StatePublished - May 21 2011
Event4th International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2011 - Waikiki, Honolulu, United States
Duration: May 21 2011May 21 2011

Publication series

NameCHASE 2011 - Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering, Co-located with ICSE 2011
Volume2011-January

Conference

Conference4th International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2011
Country/TerritoryUnited States
CityWaikiki, Honolulu
Period5/21/115/21/11

Bibliographical note

Funding Information:
This work is funded in part by the National Science Foundation under NSF grant CCF-0811140 and in part by a grant from Lockheed Martin Corporation. We thank John Dalbey and David Cuddeback for the ChangeStyle dataset. We thank Clark Savage Turner for allowing the experiments in his course; we thank all the Cal Poly and UK participants. We thank Jody Larsen for RETRO.NET.

Keywords

  • Effort
  • Logging
  • Study of the Analyst
  • Traceability

ASJC Scopus subject areas

  • Organizational Behavior and Human Resource Management
  • Management of Technology and Innovation
  • Software
  • Social Psychology

Fingerprint

Dive into the research topics of 'How do we trace requirements? An initial study of analyst behavior in trace validation tasks'. Together they form a unique fingerprint.

Cite this