An integration of traceability elements and their impact in consumer's trust
78
Citation
85
Reference
10
Related Paper
Citation Trend
Keywords:
Traceability
Requirements Traceability
The benefits of traceability are widely accepted nowadays, however, several issues still make it difficult a wide-scale adoption of traceability in the software engineering practice. There is a lack of a commonly accepted traceability definition further than the term definition, a standard way of specifying traceability among items, and a traceability type classification; besides, conflicts among a number of approaches exist. As a result traceability-schemes implementation in tools lacks of generality and exchangeability. Round trip engineering therefore cannot be well enough supported. The motivation behind is aligned with that of PIM within the MDA initiative. This paper analyzes several current traceability schemes, in order to obtain relevant features and identify overlaps and inconsistencies among the approaches. Then, and based on the analysis, it provides an initial approach for a Traceability Specification Scheme. This scheme is expected to facilitate traceability specification for a given project, to improve the traceability management, and help to automate some traces management processes.
Traceability
Requirements Traceability
Generality
Cite
Citations (31)
Analyzing and summarizing requirement traceability methods,it is proposed that the requirement traceability method should have the characteristics of being easy to grasp,able to trace complex systems,able to generate traceability chain automatically,easy to maintain traceability chain,supported by the tools and documentation,etc.
Traceability
Requirements Traceability
TRACE (psycholinguistics)
Cite
Citations (0)
Continuous and frequently changing requirements require proper requirements change management. Traceability is essential for management of change and analysis of its impact. This research paper presents a survey of existing techniques in the domain of traceability. We identify problems with traceability definition and present criteria which is used to evaluate the existing traceability techniques. Evaluation shows that current traceability techniques are deficient and may cause problems in managing requirements change properly. We categorizing techniques into three classes argue that existing techniques may be combined to address the short comings of each other and to avail maximum benefits from traceability.
Traceability
Requirements Traceability
Change impact analysis
Change Management
Cite
Citations (33)
The application of RFID in food safety traceability system would be beneficial to achieving the tracing of headstream food and the scientific and transparent management. The article was focusing on the principle of RFID and its application and cases in food safety traceability system. In addition, the article was reviewed about the questions to be adverted and solved and the developing ways of RFID in food safety traceability system.
Traceability
Food safety management
Requirements Traceability
Tracing
Cite
Citations (0)
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.
Traceability
Requirements Traceability
Change impact analysis
Functional requirement
Cite
Citations (1)
Investigates and discusses 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. 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.< >
Traceability
Requirements Traceability
Cite
Citations (1,223)
Requirements traceability is the ability to trace requirements to other software engineering artifacts. Traceability can be classified as either pre- or post-requirements specifications (RS) traceability. Pre-RS traceability is the ability to trace between requirements and their origin. However, the benefits of pre-RS traceability are often not clear. In this article, we systematically lay out the benefits of pre-RS traceability. We present results from both a literature review and a qualitative survey of practitioners involved with documenting and utilizing such trace links. We find that the benefits strongly depend on the practitioners, their tasks, and the project environment. Awareness of these relationships supports a clearer understanding of the benefits of pre-RS traceability and thus motivates successful implementation of the required practices. The results of our research motivates the adoption of pre-RS traceability and present problem areas for future research.
Traceability
Requirements Traceability
TRACE (psycholinguistics)
Cite
Citations (1)
Awareness of the importance of systems and software traceability, as well as tool support for traceability, have improved over the years. But an effective solution for traceability must align and integrate with an organization's engineering processes. Specifically, the phases of the traceability process model (traceability strategy, creation, use and maintenance of traceability) must be aligned with the organization's engineering processes. Previous research has discussed the benefits of integrating traceability into the configuration management process. In this paper, we propose Change Request management using traceability data. In our approach, new Change Requests (CRs) are created from the traceability model of the corresponding project. The created CRs contain a portion of the project's overall traceability model that is relevant to that change. A proof-of-concept issue tracking system is proposed that uses a traceability model at its core.
Traceability
Requirements Traceability
Cite
Citations (1)
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.
Traceability
Requirements Traceability
Cite
Citations (11)
Abstract : Department of Defense Standard 2167A mandates that requirements traceability be conducted during the development of government systems. This and other standards, as well as current literature, however, do not provide a comprehensive model of what information should be captured as a part of a traceability scheme. The primary goal of this research is to develop a model of requirements traceability at the level of systems design which relates requirements to all system components. An empirical study using focus groups was conducted with various stakeholders involved with the development of large, complex systems. Based on an analysis of the information obtained by the focus group sessions, a model for traceability was developed. This model describes the various relationships or linkages between requirements and system components that must be captured and maintained to support various system development activities. Finally, several issues which must be addressed in successfully implementing a comprehensive scheme for traceability are discussed. Requirements traceability, Systems development.
Traceability
Requirements Traceability
Cite
Citations (2)