What you see is what you trace: a two-stage interview study on traceability practices and eye tracking potential

Publikation: Beitrag in FachzeitschriftArtikelForschungPeer-Review

Autoren

Organisationseinheiten

Forschungs-netzwerk anzeigen

Details

OriginalspracheEnglisch
Seiten (von - bis)329-355
Seitenumfang27
FachzeitschriftRequirements engineering
Jahrgang29
Ausgabenummer3
Frühes Online-Datum9 Juli 2024
PublikationsstatusVeröffentlicht - Sept. 2024

Abstract

The benefits of traceability have widely been discussed in research. However, studies have also shown that traceability practices are still not prevalent in industrial settings due to the high manual effort and lack of tool support. In this paper, we explore the feasibility of using eye tracking to automatically detect trace links to reduce manual effort and thereby increase practical applicability. We conducted a two-stage interview study in industry. In Stage 1 we interviewed 20 practitioners to provide an overview of how traceability is established in practice and how an eye tracking approach would need to be applied in order to be useful. In Stage 2 we conducted interviews with 16 practitioners from one project context to elicit role-specific workflows and analyzed which activities are suitable to obtain useful traceability links based on gaze data. As there is no one-fits-all solution to traceability, and technical limitations of eye tracking still exist, we collected information on used artifact types, tools and requirements management practices to adjust an approach to actual traceability stakeholders’ needs. We report on perspectives from different roles in software projects and give an overview of traced artifacts, current traceability experiences, as well as benefits and doubts concerned with using eye tracking to obtain links automatically. We discuss the implications for the evaluation and implementation of an automatic tracing approach in practice and how eye tracking can support requirements engineering activities.

ASJC Scopus Sachgebiete

Zitieren

What you see is what you trace: a two-stage interview study on traceability practices and eye tracking potential. / Ahrens, Maike; Nagel, Lukas; Schneider, Kurt.
in: Requirements engineering, Jahrgang 29, Nr. 3, 09.2024, S. 329-355.

Publikation: Beitrag in FachzeitschriftArtikelForschungPeer-Review

Download
@article{ec692407221b46a584b7b2f4b832f712,
title = "What you see is what you trace: a two-stage interview study on traceability practices and eye tracking potential",
abstract = "The benefits of traceability have widely been discussed in research. However, studies have also shown that traceability practices are still not prevalent in industrial settings due to the high manual effort and lack of tool support. In this paper, we explore the feasibility of using eye tracking to automatically detect trace links to reduce manual effort and thereby increase practical applicability. We conducted a two-stage interview study in industry. In Stage 1 we interviewed 20 practitioners to provide an overview of how traceability is established in practice and how an eye tracking approach would need to be applied in order to be useful. In Stage 2 we conducted interviews with 16 practitioners from one project context to elicit role-specific workflows and analyzed which activities are suitable to obtain useful traceability links based on gaze data. As there is no one-fits-all solution to traceability, and technical limitations of eye tracking still exist, we collected information on used artifact types, tools and requirements management practices to adjust an approach to actual traceability stakeholders{\textquoteright} needs. We report on perspectives from different roles in software projects and give an overview of traced artifacts, current traceability experiences, as well as benefits and doubts concerned with using eye tracking to obtain links automatically. We discuss the implications for the evaluation and implementation of an automatic tracing approach in practice and how eye tracking can support requirements engineering activities.",
keywords = "Empirical interview study, Eye tracking, Industry, Requirements traceability, Software project artifacts, Trace links",
author = "Maike Ahrens and Lukas Nagel and Kurt Schneider",
note = "Publisher Copyright: {\textcopyright} The Author(s) 2024.",
year = "2024",
month = sep,
doi = "10.1007/s00766-024-00419-0",
language = "English",
volume = "29",
pages = "329--355",
journal = "Requirements engineering",
issn = "0947-3602",
publisher = "Springer London",
number = "3",

}

Download

TY - JOUR

T1 - What you see is what you trace

T2 - a two-stage interview study on traceability practices and eye tracking potential

AU - Ahrens, Maike

AU - Nagel, Lukas

AU - Schneider, Kurt

N1 - Publisher Copyright: © The Author(s) 2024.

PY - 2024/9

Y1 - 2024/9

N2 - The benefits of traceability have widely been discussed in research. However, studies have also shown that traceability practices are still not prevalent in industrial settings due to the high manual effort and lack of tool support. In this paper, we explore the feasibility of using eye tracking to automatically detect trace links to reduce manual effort and thereby increase practical applicability. We conducted a two-stage interview study in industry. In Stage 1 we interviewed 20 practitioners to provide an overview of how traceability is established in practice and how an eye tracking approach would need to be applied in order to be useful. In Stage 2 we conducted interviews with 16 practitioners from one project context to elicit role-specific workflows and analyzed which activities are suitable to obtain useful traceability links based on gaze data. As there is no one-fits-all solution to traceability, and technical limitations of eye tracking still exist, we collected information on used artifact types, tools and requirements management practices to adjust an approach to actual traceability stakeholders’ needs. We report on perspectives from different roles in software projects and give an overview of traced artifacts, current traceability experiences, as well as benefits and doubts concerned with using eye tracking to obtain links automatically. We discuss the implications for the evaluation and implementation of an automatic tracing approach in practice and how eye tracking can support requirements engineering activities.

AB - The benefits of traceability have widely been discussed in research. However, studies have also shown that traceability practices are still not prevalent in industrial settings due to the high manual effort and lack of tool support. In this paper, we explore the feasibility of using eye tracking to automatically detect trace links to reduce manual effort and thereby increase practical applicability. We conducted a two-stage interview study in industry. In Stage 1 we interviewed 20 practitioners to provide an overview of how traceability is established in practice and how an eye tracking approach would need to be applied in order to be useful. In Stage 2 we conducted interviews with 16 practitioners from one project context to elicit role-specific workflows and analyzed which activities are suitable to obtain useful traceability links based on gaze data. As there is no one-fits-all solution to traceability, and technical limitations of eye tracking still exist, we collected information on used artifact types, tools and requirements management practices to adjust an approach to actual traceability stakeholders’ needs. We report on perspectives from different roles in software projects and give an overview of traced artifacts, current traceability experiences, as well as benefits and doubts concerned with using eye tracking to obtain links automatically. We discuss the implications for the evaluation and implementation of an automatic tracing approach in practice and how eye tracking can support requirements engineering activities.

KW - Empirical interview study

KW - Eye tracking

KW - Industry

KW - Requirements traceability

KW - Software project artifacts

KW - Trace links

UR - http://www.scopus.com/inward/record.url?scp=85197773031&partnerID=8YFLogxK

U2 - 10.1007/s00766-024-00419-0

DO - 10.1007/s00766-024-00419-0

M3 - Article

AN - SCOPUS:85197773031

VL - 29

SP - 329

EP - 355

JO - Requirements engineering

JF - Requirements engineering

SN - 0947-3602

IS - 3

ER -

Von denselben Autoren