When testing existing systems, we often discover that we miss some important input to base the test cases on: the specification of the system. That is when we start to reverse engineer and complete the documentation on the system. This activity yields us a big number of requirements, that need to be managed accordingly. The introduction of requirements management in a later system release has a number of specificities compared to requirements management started from the very first release of a system. This presentation highlights some of these differences and describes the difficulties encountered in a recent project that aimed to introduce requirements management for an existing system.
|Title of host publication||Proceedings VVSS2009 (Eindhoven, The Netherlands, June 11, 2009)|
|Publication status||Published - 2009|