DMCA
How do we trace requirements? an initial study of analyst behavior in trace validation tasks
| Venue: | in Proc. CHASE |
| Citations: | 10 - 5 self |
BibTeX
@INPROCEEDINGS{Kong_howdo,
author = {Wei-keat Kong and Jane Huffman Hayes and Alex Dekhtyar and Jeff Holden},
title = {How do we trace requirements? an initial study of analyst behavior in trace validation tasks},
booktitle = {in Proc. CHASE},
year = {},
pages = {32--39}
}
Share
 |
 |
 |
 |
||
OpenURL
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.
Keyphrases
trace validation task analyst behavior initial study design traceability tool human analyst traceability tool requirement tracing candidate traceability link log analyst action automated traceability tool traceability recovery task person-power intensive task utilize analyst time traceability recovery research version high quality final traceability matrix traceability matrix user log
