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

or analysis of other literature. This paper, in contrast, follows an empirical approach. Focus groups and interviews conducted in 26 major software development organizations demonstrate a wide range of traceability practices with distinct low-end and high-end users of traceability. From these observations

, which emphasizes the tangible threats blacks might pose to whites' private lives; and a sociocultural theory of prejudice termed symbolic racism, which emphasizes abstract, moralistic resentments of blacks, presumably traceable to preadult socialization. The main dependent variable in our analysis

of information about the human sources of requirements. This suggestion is directly based upon findings from an empirical analysis of the RT problem conducted with over one hundred practitioners. In these studies, we found that practitioners predominantly claim to have experienced RT problems when, being unable

relations; development of architectures, tools, and environments for the representation and maintenance of traceability relations; and empirical investigations into organisational practices regarding the establishment and deployment of traceability relations in the software development life cycle. However

development, increased ease of system understanding, and more precise impact analysis of proposed changes. An industry-scale project applying the analysis and design method Objectory has been examined and documented with a number of traceability examples generated from the perspective of a maintainer

Abstract—We present an empirical study to statistically analyze the equivalence of several traceability recovery methods based on Information Retrieval (IR) techniques. The analysis is based on Principal Component Analysis and on the analysis of the overlap of the set of candidate links provided

Abstract—Traceability between development artefacts and mainly from and to requirements plays a major role in system lifecycle, supporting activities such as system validation, change impact analysis, and regulation compliance. Many researchers have been working on this topic and have published

and Frutus for providing the data and Eng. Antonio Fragata, of DEESA-INIA for his logistical support and collaboration. This research was supported by a doctoral fellowship

rights reserved. Readers may make verbatim copies of this document for non- commercial purposes by any means, provided that this copyright notice appears on all such copies. 1 Firms ’ strategies and voluntary traceability: an empirical analysis in Italian food chains