Demi, Selina, Sánchez-Gordón, Mary, Colomo-Palacios, Ricardo · Figshare · 2020
Our goal is to identify and analyze the main factors that hinder the use and adoption of automated requirements traceability. To serve this purpose, we adopt a systematic literature review, following with rigor the guidelines for systematic literature reviews in software engineering. We selected 60 final primary studies, extracted specific data from these studies and developed a conceptual framework that categorizes the identified factors into technological, organizational and environmental contexts. Additionally, suggestions are derived and they may serve as guidelines for organizations attempting to shift from manual requirements traceability or no requirements traceability at all to automated requirements traceability.
Cited by 0Open access
Wei Li, Rayford B. Vaughn, Hossein Saiedian · Encyclopedia of Software Engineering · 2002
Abstract Requirements traceability (RT) can be viewed as “the ability to describe and follow the life of a requirement, in both the forward and backward direction” It is used to capture the relationships between requirements, design, and implementation of a system. RT not only can be a useful solution to align system evolution with changing stakeholder needs but also helps in finding unexpected problems, innovative opportunities and laying the groundwork for corporate knowledge management Techniques have been suggested in the research literature to address the RT problem. Their use, however, is still not as widespread as the importance of RT suggests. This is likely because there are still many issues to be addressed, for example, the lack of common definitions and conflicting underlying problems According to analysis, there are two different kinds of traceability: prerequirements specification (pre‐RS) traceability and postrequirements specification (post‐RS) traceability. In practice, requirement traceability users can be divided into two groups: low end and high end traceability users. Issues related to the RT definition and its importance are discussed. Pre‐RT and post‐RT traceability problems and approaches are also discussed. A brief introduction to the tools used in RT is presented and their usefulness in addressing the RT problem is discussed in the section on tools support for RT. The article concludes with suggestions for related future work.
Cited by 11
Demi, Selina, Sánchez-Gordón, Mary, Colomo-Palacios, Ricardo · Figshare · 2020
Our goal is to identify and analyze the main factors that hinder the use and adoption of automated requirements traceability. To serve this purpose, we adopt a systematic literature review, following with rigor the guidelines for systematic literature reviews in software engineering. We selected 60 final primary studies, extracted specific data from these studies and developed a conceptual framework that categorizes the identified factors into technological, organizational and environmental contexts. Additionally, suggestions are derived and they may serve as guidelines for organizations attempting to shift from manual requirements traceability or no requirements traceability at all to automated requirements traceability.
Cited by 0Open access
James A. Crowder, Curtis W. Hoff · 2022
Cited by 1
Hokkanen, Mia · LUTPub (LUT University) · 2008
Vaatimusmäärittely on tärkeä osa ohjelmistotuotantoa. Vaatimusten jäljitettävyys on osa vaatimustenhallinta prosessia. Jäljitettävyystieto helpottaa vaatimusten hallintaa läpi koko tuotekehitys projektin. Hyvin usein vaatimusten jäljitettävyyttä ei kuitenkaan ole toteutettu ohjelmistokehitysprojekteissa. Työn tavoitteena oli selvittää vaatimusten jäljitettävyyden tärkeyttä ohjelmistotuotannossa sekä kuinka jäljitettävyys voitaisiin toteuttaa ohjelmistokehitysprojekteissa. Vaatimusten jäljitettävyyttä sekä eri tekniikoita sen toteuttamiseksi on tutkittu kirjallisuuden avulla. Yrityksen vaatimusten jäljitettävyyden nykytilaa on selvitetty tutkimalla olemassa olevaa prosessimallia sekä todellisia tuotekehitysprojekteja. Tuloksena esitettiin perusteluja, miksi jäljitettävyystieto pitäisi sisällyttää ohjelmistokehitysprojekteihin sekä menetelmiä, kuinka jäljitettävyystieto voidaan toteuttaa projekteissa kustannustehokkaasti. Työssä on esitetty strategiavaihtoehto ja menetelmät jäljitettävyyden toteuttamiseksi. Pienillä korjauksilla jäljitettävyys pystytään toteuttamaan kevyellä tasolla. Suurin parannusehdotus prosessimalliin on jäljitettävyysmatriisien luominen. Matriisien avulla pystytään projekteissa toteuttamaan jäljitettävyys sekä eteen- että taaksepäin. Vaatimustenhallintatyökalu helpottaisi jäljitettävyystiedon ylläpitoa.
Cited by 1Open access
Asyrofi, Rakha · Zenodo (CERN European Organization for Nuclear Research) · 2021
Ini adalah sebuah source code dari judul paper yang sama dengan nama "Comparative Studies of Several Methods for Building Simple Traceability and Identifying The Quality Aspects of Requirements in SRS Documents" di proceeding conference EECCIS 2020 pada laman berikut ini, anda bisa lihat download dan menggunakannya. serta jangan lupa untuk citasi paper kami terima kasih..
Cited by 0Open access
Philip Morris, Andrew Coombes, John Mcdermid · 1994
This paper describes research which has been carried out into a framework for requirements analysis. This framework provides the basis for a rich set of traceability relationships, which as we shall see assists the user of requirements in a number of ways. The description makes no attempt to introduce any formal or mathematical concepts but it should be noted that work underpinning the approach described here with a fairly extensive formal notation is ongoing. The structure of the paper is as follows: Section 2 describes the principle of goal-structuring as it is applied to requirements definition. In section 3, we discuss the issues of traceability. Finally, in section 4, we discuss the uses of the richer traceability which is provided. 2. Hierarchical Decomposition It is our thesis that a requirements analysis process based upon a principle of goalstructuring is conducive to a well-structured, traceable requirements specification. Our definition of this process relies upon several primary concepts:
Cited by 0
Gavilan, Jorge · Zenodo (CERN European Organization for Nuclear Research) · 2025
Requirements Traceability Matrix (RTM) with EARS Requirements derived from the Dataspace Protocol Specification and Test Cases for compliance evaluation of the Prometheus-X Dataspace Connector.
Cited by 0Open access
Gavilan, Jorge · Zenodo (CERN European Organization for Nuclear Research) · 2025
Requirements Traceability Matrix (RTM) with EARS Requirements derived from the Dataspace Protocol Specification and Test Cases for compliance evaluation of the Prometheus-X Dataspace Connector.
Cited by 0Open access
Gavilan, Jorge · Zenodo (CERN European Organization for Nuclear Research) · 2025
Requirements Traceability Matrix (RTM) with EARS Requirements derived from the Dataspace Protocol Specification and Test Cases for compliance evaluation of the Eclipse Dataspace Connector.
Cited by 0Open access
Raja, Uzair Akbar, Kamran, Kashif · KTH Publication Database DiVA (KTH Royal Institute of Technology) · 2008
Requirements traceability provides support for many software engineering activities like impact analysis, requirements validation and regression testing. In addition requirements traceability is the recognized component of many software process improvement initiatives. Requirements traceability also helps to control and manage evolution of a software system. This thesis presents a systematic review and a framework for requirements traceability. The systematic review is aimed at presenting fair evaluation of research concerning requirements traceability over the period 1997 – 2007. The systematic review aims at identifying probable gaps in research about requirements traceability and opens new horizons to explore. Moreover, two companies have been interviewed to understand the practice of requirements traceability in industry. After the analysis of industrial interviews these companies have been classified into two categories of traceability users. These categories are high-end traceability users and low-end traceability users. Based on the analysis of systematic review results and industrial interviews, this thesis presents a framework for requirements traceability called ‘Three Level Framework for Requirements Traceability (TLFRT)’. This framework is composed of three levels. The level 0 of this framework focuses on pre-RS traceability where as level 1 and level 2 focuses on post-RS traceability. The level 1 provide traceability for the functional requirements, where as level 2 provide traceability for non-functional requirements. TLFRT provides guidelines to a process that can be tailored to fit the needs of the high-end traceability users and low-end traceability users as well. This framework has been statically validated in two companies. The validation of TLFRT in industry resulted in compilation of lessons learned, which ensures that this theoretical framework could also be used in real industrial environment. The results of the research presented in this thesis are aimed at supporting requirements traceability by taking its current issues/challenges into account.
Cited by 1Open access
Nasir Ali, Yann‐Gaël Guéhéneuc, Giuliano Antoniol · 2011
Information retrieval (IR) approaches have proven useful in recovering traceability links between free text documentation and source code. IR-based traceability recovery approaches produce ranked lists of traceability links between pieces of documentation and source code. These traceability links are then pruned using various strategies and, finally, validated by human experts. In this paper we propose two contributions to improve the precision and recall of traceability links and, thus, reduces the required human experts' manual validation effort. First, we propose a novel approach, Trustrace, inspired by Web trust models to improve the precision and recall of traceability links: Trustrace uses any traceability recovery approach to obtain a set of traceability links, which rankings are then re-evaluated using a set of other traceability recovery approaches. Second, we propose a novel traceability recovery approach, Histrace, to identify traceability links between requirements and source code through CVS/SVN change logs using a Vector Space Model (VSM). We combine a traditional recovery traceability approach with Histrace to build Trustrace <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">VSM, Histrace</sup> in which we use Histrace as one expert adding knowledge to the traceability links extracted from CVS/SVN change logs. We apply Trustrace <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">VSM, Histrace</sup> on two case studies to compare its traceability links with those recovered using only the VSM-based approach, in terms of precision and recall. We show that Trustrace <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">VSM, Histrace</sup> improves with statistical significance the precision of the traceability links while also improving recall but without statistical significance.
Cited by 36
Rob Pooley, Craig Warren · 2008
The Reuse of code artefacts can make development quicker, cheaper and more robust, but is complex and has many pitfalls: Code artefacts must exist, be available, be found, be understood, be valid and finally be integrated. Many software developers try to ensure that artefacts meet these requirements through a process of making code "reusable." If the generation of reusable artefacts from developed code could be automated development time could be reduced. Code artefacts must be gathered and indexed automatically with no extra work. Our review of requirement management and version control tools identified a way to generate reuse artefacts through traceability, using information from the requirement management system and code stored in the version control system. A prototype to search these indexed artefacts showed that this tool could substantially reduce development time for simple tasks, by up to 63%.
Cited by 6
pohl, K. · RWTH Publications (RWTH Aachen) · 1994
Cited by 0
Nitesh Narayan, Yang Li, Jonas Helming et al. · 2011
Cited by 0Open access
Gavilan, Jorge · Zenodo (CERN European Organization for Nuclear Research) · 2025
Requirements Traceability Matrix (RTM) with EARS Requirements derived from the Dataspace Protocol Specification and Test Cases for compliance evaluation of the Eclipse Dataspace Connector.
Cited by 0Open access
Adi Wibowo, Joseph G. Davis · Proceedings of the Australasian Computer Science Week Multiconference · 2020
research-article Share on Requirements Traceability Ontology to Support Requirements Management Authors: Adi Wibowo Petra Christian University, Indonesia Petra Christian University, IndonesiaView Profile , Joseph Davis The University of Sydney, Australia The University of Sydney, AustraliaView Profile Authors Info & Claims ACSW '20: Proceedings of the Australasian Computer Science Week MulticonferenceFebruary 2020 Article No.: 21Pages 1–9https://doi.org/10.1145/3373017.3373038Published:04 February 2020Publication History 0citation427DownloadsMetricsTotal Citations0Total Downloads427Last 12 Months77Last 6 weeks6 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteGet Access
Cited by 11
Justin K. Pearson, Royal Holloway · 1996
This paper is concerned with the interaction between formal software development and the issue of requirements traceability. The paper offers an analysis of the requirements traceability problem (see [1]) which takes into account software development using formal methods. Starting from the observation that formal software development is not an infallible method of producing error free and `correct&apos; code (see [2]); sources of error identified as in [3] are used to motivate a new analysis of the requirements traceability problem. Traceability is divided into: Pre-Requirements Specification, Pre-Formal Requirements Specification and Post-Formal Requirements traceability, a finer distinction than is made by Gotel and Finkelstein in [1]. This distinction is motivated by the problems associated with the process of formalizing a prose requirements specification document together with an The work described here forms part of the DATUM project (grant GR/H8994, project number IED4/19314) in t...
Cited by 0
Waraporn Jirapanthong · 2015
The development of software products is currently being expanded to be based on web applications. Due to the time constraints, software design and development for web applications are driven. It leads the software or applications become more complex. Identifying impacts of changes or relations takes a lot of time and effort. One challenge is to enable traceability on software artefacts created during the development of web applications. Moreover, it is believed that analysis of data obtained from traceability relations is another way to make software process more efficient. However, it is absolutely not an easy task due to lack of guidelines, support, and tools. This research thus aims to enable software traceability on the development of web applications which involve many types of documents.
Cited by 3
RSC chromatography monographs · 2007
Cited by 0