An analysis of the requirements traceability problem

In this paper1, we investigate and discuss the underlying nature of the requirements traceability problem. Our work is based on empirical studies, involving over 100 practitioners, and an evaluation of current support. We introduce the distinction between pre-requirements specification (pre-RS) traceability and post-requirements specification (post-RS) traceability, to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework through which to understand its multifaceted nature. We report how the majority of the problems attributed to poor requirements traceability are due to inadequate pre-RS traceability and show the fundamental need for improvements here. In the remainder of the paper, we present an analysis of the main barriers confronting such improvements in practice, identify relevant areas in which advances have been (or can be) made, and make recommendations for research

An investigation of requirements traceability practices in software companies in Malaysia

Requirement traceability (RT) is one of the critical activity of good requirements management and an important part of development projects. At the same time, it improves the quality of software products. Nevertheless, industrial practitioners are challenged by this lack of guidance or results which serve as a rule or guide in establishing effective traceability in their projects. The outcome of this is that practitioners are ill-informed as to the best or most efficient means of accomplishing their tasks, such as found in software companies. Notwithstanding the lack of guidance, there are a number of commonly accepted practices which can guide industrial practitioners with respect to trace the requirements in their projects. This study aims to determine the practices of RT through conducting a systematic literature review. Also, this study conducted a survey for investigating the use of RT practices in the software companies at northern region of Malaysia. Finally, a series of interviews with practitioners were carried out to know the reasons that influence on the use of these practices in software development. The findings showed that majority software companies do not use traceability practices for tracing requirements due to financial issues and the lack of knowledge of these practices. This study presented empirical evidence about the use of RT practices among software companies. Thus, the findings of this study can assist practitioners to select RT practices, and also enables researchers to find gaps and pointers for future study in this study domain

Contribution structures

The invisibility of the individuals and groups that gave rise to requirements artifacts has been identified as a primary reason for the persistence of requirements traceability problems. This paper presents an approach, based on modelling the dynamic contribution structures underlying requirements artifacts, which addresses this issue. We show how these structures can be defined, using information about the agents who have contributed to artifact production, in conjunction with details of the numerous traceability relations that hold within and between artifacts themselves. We describe a scheme, derived from work in sociolinguistics, which can be used to indicate the capacities in which agents contribute. We then show how this information can be used to infer details about the social roles and commitments of agents with respect to their various contributions and to each other. We further propose a categorisation for artifact-based traceability relations and illustrate how they impinge on the identification and definition of these structures. Finally, we outline how this approach can be implemented and supported by tools, explain the means by which requirements change can be accommodated in the corresponding contribution structures, and demonstrate the potential it provides for "personnel-based" requirements traceability

An Introduction to Requirements Traceability

This report surveys the requirements traceability literature and gives some recommendations for further research and for an approach to consultancy concerning traceability in the 2RARE project. The problem of maintaining traceability in a development project is viewed as the problem of maintaining an information system that maintains the relevant links between items developed during the process. These items may vary from requirements to design and implementation documents. To develop and implement such an information system, we must identify the needs for tracking information, made a model of this information, design usage procedures for the system, and implement the system. Accordingly, the literature on traceability is organized under the headings needs, models and usage. Furthermore, tracking tools are briefly reviewed

Selection of traceability-based, automated decision-making methods in global production networks

Automating traceability-based decision-making can shorten the reaction time to supply chain disruptions. This paper develops a framework for choosing automated decision-making (ADM) methods based on traceability data. It contains a toolbox comprising methods suitable for ADM, respective selection criteria and a new process to select a suitable ADM method based on companies’ requirements. This process is based on an evaluation matrix matching methods and criteria. As a result, the ADM framework suggests the most suitable method to automate a specifically chosen decision. The developed framework is validated in the supply chain of a globally operating truck manufacturer

Traceability system for capturing, processing and providing consumer-relevant information about wood products: System solution and its economic feasibility

Current research and practice reports indicate the existence of purchase barriers concerning eco-friendly products, e.g. wood products. These can be ascribed to consumers' mistrust regarding the non-observable environmental impact of wood products. To counter the mistrust, wood products are commonly endowed with eco-labels, which may be perceived mostly as a marketing tool, therefore not fulfilling their intended purpose. Current studies have shown that providing consumers with wood product information based on traceability systems increases product trust and purchase intentions, with those information items most valued by consumers being identified as well. Based on this, the paper proposes a traceability information system for the capturing, processing, and provision of product information using examples of wood furniture. Furthermore, a cost-benefit model for the proposed solution is developed. The calculations indicate the possibility of implementing traceability at the item level based on a four-layer system architecture enabling the capture and delivery of all information valued by consumers at acceptable costs. The proposed system helps to overcome purchase barriers of eco-friendly products, increasing consumers' product trust and purchase intentions

Methodology for automating software systems

Applying ITS technology to the shuttle diagnostics would not require the rigor of the Petri Net representation, however it is important in providing the animated simulated portion of the interface and the demands placed on the system to support the training aspects to have a homogeneous and consistent underlying knowledge representation. By keeping the diagnostic rule base, the hardware description, the software description, user profiles, desired behavioral knowledge, and the user interface in the same notation, it is possible to reason about the all of the properties of petri nets, on any selected portion of the simulation. This reasoning provides foundation for utilization of intelligent tutoring systems technology

Evaluasi Pendekatan Pembangunan Traceability Link Dalam Evolusi Perangkat Lunak

Traceability merupakan hal penting pada proyek perangkat lunak, terutama pada proyek skala besar. Traceability berfungsi untuk mengetahui ketelusuran antar artefak dalam fase-fase yang berbeda (analisis kebutuhan, analisis desain, dan analisis implementasi) maupun antara artefak dan pihak pengembang yang terlibat. Sistem traceability otomatis diperlukan untuk membangun ketelusuran antar artefak. Penelitian ini bertujuan untuk mengeksplorasi sejumlah literatur pendekatan terbaru yang digunakan untuk membangun traceability link. Eksplorasi literatur mengacu pada taksonomi berbasis evolusi perangkat lunak terhadap sejumlah mekanisme karakterisasi Perubahan dan faktor-faktor yang mempengaruhi mekanisme. Hasil penelitian dapat digunakan untuk mengidentifikasi bagaimana pendekatan tersebut dapat mendukung evolusi perangkat lunak serta memberikan garis besar dari kriteria yang dibutuhkan untuk membangun metode traceability yang lebih baik. Kesimpulan dari penelitian ini adalah variasi faktor suatu pendekatan tidak berbeda jauh dengan pendekatan lainnya kecuali jika terdapat perbedaan pada faktor temporal