| Summary: | Requirements tracing is a universally neglected practice in industry, despite clear knowledgement that it supports high-end practices, such as change management and control and impact analysis. Requirements tracing is comprised of two principal types; pre- and post-requirement specification tracing. Post-requirement.specificadon tracing, or post-RST, is concerned with tracing requirements after they have already bncluded in the specification. Pre-RST is concerned with life before inclusion, and therefore represents the origin of each requirement. Pre-RST is less often implemented in practice than post-RST. The principal reason for this is that equirements tracing of any kind doesn't appear to offer enough tangible benefits to the organisation that is developing the software to make it worthwhile, especially given the high cost of tracing by hand. Automating the process of pre-RST is therefore likely to increase its appeal to practitioners by significantly reducing the cost ing pre-RST.
|
|---|
