This paper investigates the requirements traceability problem, highlighting the distinction between pre-requirements specification (pre-RS) and post-requirements specification (post-RS) traceability. It argues that an all-encompassing solution is unlikely due to the multifaceted nature of the problem. The paper presents empirical studies involving over 100 practitioners and evaluates current support for requirements traceability. It identifies inadequate pre-RS traceability as the main cause of poor traceability and emphasizes the need for improvements here. The paper also discusses the main barriers to improvement, identifies areas for advancement, and makes recommendations for research. The paper defines requirements traceability as the ability to describe and follow the life of a requirement in both forward and backward directions. Pre-RS traceability refers to aspects of a requirement's life before it is included in the requirements specification, while post-RS traceability refers to aspects after inclusion. The paper argues that pre-RS traceability is often neglected, leading to problems in traceability. It discusses the challenges of improving pre-RS traceability, including the need for better information management and the importance of context-sensitive solutions. The paper also discusses the current state of support for requirements traceability, noting that most tools do not adequately support it. It highlights the need for better tools and methods to support both pre-RS and post-RS traceability. The paper concludes that there is a need for further research into pre-RS traceability, particularly in the context of improving the ability to locate and access information related to requirements specification and refinement. The paper emphasizes the importance of continuous and explicit modeling of the social infrastructure in which requirements are produced, specified, maintained, and used.This paper investigates the requirements traceability problem, highlighting the distinction between pre-requirements specification (pre-RS) and post-requirements specification (post-RS) traceability. It argues that an all-encompassing solution is unlikely due to the multifaceted nature of the problem. The paper presents empirical studies involving over 100 practitioners and evaluates current support for requirements traceability. It identifies inadequate pre-RS traceability as the main cause of poor traceability and emphasizes the need for improvements here. The paper also discusses the main barriers to improvement, identifies areas for advancement, and makes recommendations for research. The paper defines requirements traceability as the ability to describe and follow the life of a requirement in both forward and backward directions. Pre-RS traceability refers to aspects of a requirement's life before it is included in the requirements specification, while post-RS traceability refers to aspects after inclusion. The paper argues that pre-RS traceability is often neglected, leading to problems in traceability. It discusses the challenges of improving pre-RS traceability, including the need for better information management and the importance of context-sensitive solutions. The paper also discusses the current state of support for requirements traceability, noting that most tools do not adequately support it. It highlights the need for better tools and methods to support both pre-RS and post-RS traceability. The paper concludes that there is a need for further research into pre-RS traceability, particularly in the context of improving the ability to locate and access information related to requirements specification and refinement. The paper emphasizes the importance of continuous and explicit modeling of the social infrastructure in which requirements are produced, specified, maintained, and used.