Extended Requirements Traceability a Framework for Changing Requirements
A. Gotel, Anthony Finkelstein · UCL Discovery (University College London) · 1996
We consider it an undisputed fact that requirements emerge and evolve during the lifetime of most system and software development projects. When they do, a mechanism is needed to assimilate both the change and its repercussions into an existing body of interrelated project material. This has traditionally been made possible, with varying degrees of success, through the ability to carry out requirements traceability. Nowadays, the activity of providing for requirements traceability is likely to be achieved using some form of cross referencing or indexing. Dedicated tool support for such techniques provides the added opportunity to exploit the results in interesting ways. However, and despite use of these tools, practitioners still encounter problems with continuous requirements change. We point to some of the more obvious reasons for this situation below: