A systematic review of requirement traceability techniques and tools

Tufail, Hanny; Masood, Muhammad Faisal; Zeb, Babar; Azam, Farooque; Anwar, Muhammad Waseem

doi:10.1109/icsrs.2017.8272863

Cited by 22 publications

(8 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These challenges provided the inspiration for the present study. They concur with those identified by Tufail et al (2017) in a survey which included ten challenges that could also be interpreted as traceability problems. This paper focuses on those challenges that are the most relevant to industrial applications, such as poor tool support, lack of guidance and commitment, and the different viewpoints of stakeholders.…”

Section: Methodssupporting

confidence: 83%

See 1 more Smart Citation

Lean requirements traceability automation enabled by model-driven engineering

Escalona

Koch

García-Borgoñón

2022

PeerJ Computer Science

View full text Add to dashboard Cite

Background The benefits of requirements traceability, such as improvements in software product and process quality, early testing, and software maintenance, are widely described in the literature. Requirements traceability is a critical, widely accepted practice. However, very often it is not applied for fear of the additional costs associated with manual efforts or the use of additional tools. Methods This article presents a “low-cost” mechanism for automating requirements traceability based on the model-driven paradigm and formalized by a metamodel for the creation and monitoring of traces and an integration process for traceability management. This approach can also be useful for information fusion in industry insofar that it facilitates data traceability. Results This article extends an existing model-driven development methodology to incorporate traceability as part of its development tool. The tool has been used successfully by several companies in real software development projects, helping developers to manage ongoing changes in functional requirements. One of those projects is cited as an example in the paper. The authors’ current work leads them to conclude that a model-driven engineering approach, traditionally used only for the automatic generation of code in a software development process, can also be used to successfully automate and integrate traceability management without additional costs. The systematic evaluation of traceability management in industrial projects constitutes a promising area for future work.

show abstract

Section: Methodssupporting

confidence: 83%

“…A more recent literature review was carried out by Tufail et al (2017) . This review focused on requirements traceability techniques, models, and tools, offering detailed analysis and comparison and providing a set of comparative tables.…”

Section: Methodsmentioning

confidence: 99%

Lean requirements traceability automation enabled by model-driven engineering

Escalona

Koch

García-Borgoñón

2022

PeerJ Computer Science

View full text Add to dashboard Cite

show abstract

“…The study considers primary studies during the period 1997 to 2007 and aims at answering two main research questions, regarding (a) the existing definitions of the requirements traceability and (b) the existing requirements traceability techniques, their challenges, and the related tools found in literature. In 2017, Tufail et al 36 performed a Systematic Literature Review also in the area of requirements traceability aiming to identify the leading models, challenges, and tools in the domain during 2010 to 2017, as well as the pros and cons of the leading requirement traceability models and tools. In the same year, Omar and Dahr conducted also a systematic literature review on the same field, aiming to present to practitioners interested into finding a suitable method for tracing requirements, the most recent (from 2008 to 2017) requirement traceability practices and tools available 37 .…”

Section: Related Workmentioning

confidence: 99%

Empirical studies on software traceability: A mapping study

Charalampidou

Ampatzoglou

Karountzos

et al. 2020

J Software Evolu Process

View full text Add to dashboard Cite

During the last decades, software traceability has been studied in a large number of studies, from different perspectives (e.g., how to create traces and what are its benefits). This large body of knowledge needs to be better explored and exploited by both practitioners and researchers: We need an overview of different aspects of traceability and a structured way to assess and compare existing work in order to extend it with new research or apply it in practice, Thus, we have conducted a secondary study on this large corpus of primary studies, focusing on empirical studies on software traceability, without setting any further restrictions in terms of investigating a specific domain or concrete artifacts. The study explores the goals of existing approaches and the empirical methods used for their evaluation. Its main contributions are the investigation of (a) the type of artifacts linked through traceability approaches; (b) the benefits of using artifact traceability approaches; (c) the ways of measuring their benefit; and (d) the research methods used. The results of the study suggest that (i) requirements artifacts are dominant in traceability; (ii) the research corpus focuses on the proposal of novel techniques for establishing traceability; and (iii) the main benefits are the improvement of software correctness and maintainability. Finally, although many studies include some empirical validation, there is still room for improvements and research methods that can be used more extensively. The obtained results are discussed under the prism of both researchers and practitioners and are compared against the state‐of‐the‐art.

show abstract

“…They found that few studies focused on heterogeneous artifacts, traceability tools, and precise semantics for trace links. Tufail et al [12] focused on analyzing the models and tools used in requirement traceability studies and collected papers published from 2010 to 2017. They identified seven requirement traceability models, ten requirement traceability challenges, and fourteen requirement traceability tools.…”

Section: Related Workmentioning

confidence: 99%

A Systematic Literature Review of Issue-Based Requirement Traceability

et al. 2023

View full text Add to dashboard Cite

Issue reports are software artifacts that often specify the changed requirements of software systems. As software systems evolve according to these changed requirements, issue reports have become the essential artifacts that should be covered by requirement traceability. While researchers have developed automatic approaches for establishing the traceability links of issue reports, no papers have surveyed these approaches. In this paper, we conduct a systematic literature review of issue-based requirement traceability. We searched for articles published in renowned conferences and journals in the software engineering field from 2011 to 2022. From 1,347 initial articles, we identified 40 relevant articles. We investigated four aspects of issue-based traceability: problems, artifact pairs, techniques, and evaluation targets. Our findings are as follows. First, the challenges of issue-based requirement traceability are relevant to accuracy, effort, support, information, and trustworthiness. Second, issue reports are linked to commits, source code, user reviews, and test cases. Third, the studies mainly adopted machine learning and information retrieval techniques to generate and recover trace links. Finally, the main evaluation targets were open-source projects, but open datasets were also provided.

show abstract

A systematic review of requirement traceability techniques and tools

Cited by 22 publications

References 12 publications

Lean requirements traceability automation enabled by model-driven engineering

Lean requirements traceability automation enabled by model-driven engineering

Empirical studies on software traceability: A mapping study

A Systematic Literature Review of Issue-Based Requirement Traceability

Contact Info

Product

Resources

About