Abstract
This paper aims to enrich software requirements specification by integrating the concept of traceability. This integration, which will allow a more helpful reading of that specification, will provide a critical support to different requirements stakeholders. Indeed traceability will help for example designers in refining requirements into lower-level design components and analysts in understanding the implications of a proposed change, to ensure that no extraneous code exists and to minimize or eliminate the presence of faked or frivolous requirements that lack any justification. The main contribution of this paper is building a schema for software requirements specification that make it easily traceable by linking each requirement to real-world dimensions such as detail design deliverables, related system requirements and sources such as user requirement, analyst, regulation and standard.