Current literature as well as standards that mandate requirements trac
eability do not provide a comprehensive model of what information shou
ld be captured and used as a part of a traceability scheme, leading to
wide variation in the quality and usefulness of traceability practice
across systems development efforts. In this paper, we present a frame
work for representing and developing a traceability scheme. The experi
ences of an organization using traceability as an important component
of a quality software engineering process are discussed. Models descri
bing the traceability practice in the organization, as well as issues
and lessons learned, both from organizational and technical perspectiv
es, from implementing a comprehensive traceability practice are presen
ted.