Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Empirical Evaluation of Taxonomic Trace Links: A Case Study
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0001-8142-9631
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-4118-0952
Ericsson Karlskrona, Sweden.
Ericsson Karlskrona, Sweden.
Show others and affiliations
2026 (English)In: Empirical Software Engineering, ISSN 1382-3256, E-ISSN 1573-7616, Vol. 31, no 2, article id 34Article in journal (Refereed) Published
Abstract [en]

Context: Traceability is a key quality attribute of artifacts that are used in knowledge-intensive tasks and supports software engineers in producing higher-quality software. Despite its clear benefits, traceability is often neglected in practice due to challenges such as granularity of traces, lack of a common artifact structure, and unclear responsibility. The Taxonomic Trace Links (TTL) approach connects source and target artifacts through a domain-specific taxonomy, aiming to address these common traceability challenges.

Objective: In this study, we empirically evaluate TTL in an industrial setting to identify its strengths and weaknesses for real-world adoption.

Method: We conducted a mixed-methods study at Ericsson involving one of its software products. Quantitative and qualitative data were collected across two traceability use cases. We established trace links between 463 business use cases, 64 test cases, and 277 ISO-standard requirements. Additionally, we held three focus group sessions with practitioners.

Results: We identified two practically relevant scenarios where traceability is required and evaluated TTL in each. Overall, practitioners found TTL to be a useful solution for identifying trace links with reasonable effort. However, developing a domain-specific taxonomy and managing heterogeneous artifact structures were noted as significant challenges.

Conclusion: TTL is a promising approach that can be adopted in practice and enables traceability use cases. However, TTL are not a replacement for traditional trace links, but complementary to enable more traceability use cases, and encourage early trace links creation.

Place, publisher, year, edition, pages
Springer, 2026. Vol. 31, no 2, article id 34
Keywords [en]
Evaluation, Requirements traceability, Taxonomy, Trace link
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-28444DOI: 10.1007/s10664-025-10764-5ISI: 001632325800013Scopus ID: 2-s2.0-105024065754OAI: oai:DiVA.org:bth-28444DiVA, id: diva2:1987119
Part of project
SERT- Software Engineering ReThought, Knowledge FoundationAvailable from: 2025-08-05 Created: 2025-08-05 Last updated: 2026-01-05Bibliographically approved
In thesis
1. Taxonomic Trace Links in Requirements Engineering
Open this publication in new window or tab >>Taxonomic Trace Links in Requirements Engineering
2025 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

Background: Software engineering is a knowledge-intensive activity that requires engineers to manage information to collaborate efficiently and effectively. Within Software Engineering, the Requirements Engineering process bridges the knowledge gap between the customer and the development team by eliciting, managing, and communicating product requirements. The traceability of these requirements supports developers in producing higher-quality software that aligns with customer needs. In addition, traceability supports other activities, such as change impact analysis, software quality assurance, and requirements-based verification.

Problem: Despite decades of research on traceability, practical challenges still hinder the adoption of traceability in practice. This signals a need for new ways of practicing traceability that fit real-world needs. 

Goal: Building on previous work, this thesis instantiates, develops, and empirically evaluates Taxonomic Trace Links, a new way to trace requirements to various software artifacts through domain knowledge captured in a taxonomy. 

Method: The studies included in this theses follows mixed research methods, which are case study, systematic mapping studies, validation study, controlled experiments, and focus groups.

Results: The current state of practice in customer-supplier communication shows persistent challenges that we mapped to solutions in the literature. Our literature study shows that traceability through domain-specific taxonomies has not been empirically evaluated. Our development and evaluation of the technical solution for taxonomic trace links show that semi-automation of trace link creation and maintenance is possible. Finally, our empirical evaluation of taxonomic trace links shows that the solution is feasible in practice and can create trace links for multiple purposes.

Conclusion: Traceability between software artifacts has more benefits than currently realized by practitioners. However, current traceability solutions, based on direct trace links, do not appear to be easily adapted in different scenarios to trace different artifacts. Taxonomic trace links are an alternative approach that could overcome the shortcomings of direct trace links. 

Place, publisher, year, edition, pages
Karlskrona: Blekinge Tekniska Högskola, 2025. p. 187
Series
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 2025:08
Keywords
requirements, traceability, domain-knowledge, taxonomy
National Category
Software Engineering
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-28451 (URN)978-91-7295-504-2 (ISBN)
Public defence
2025-10-07, C413A, Karlskrona, 13:00 (English)
Opponent
Supervisors
Available from: 2025-08-07 Created: 2025-08-07 Last updated: 2025-09-30Bibliographically approved

Open Access in DiVA

fulltext(2002 kB)18 downloads
File information
File name FULLTEXT01.pdfFile size 2002 kBChecksum SHA-512
5d28b69d8f8821d60e6f8e55a820de18200b6b5af8976e586b8ae5d1cb5ef9d57645788470b4c17afd0db9031a8801b24ac36e386aa362b04a42fdc5dc1d577c
Type fulltextMimetype application/pdf

Other links

Publisher's full textScopus

Authority records

Abdeen, WaleedUnterkalmsteiner, MichaelWnuk, Krzysztof

Search in DiVA

By author/editor
Abdeen, WaleedUnterkalmsteiner, MichaelWnuk, Krzysztof
By organisation
Department of Software Engineering
In the same journal
Empirical Software Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 18 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 192 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf