Reusing operational requirements: a process-oriented approach

Advocates a process-oriented approach to reusing operational requirements. In process-oriented approaches, a development (and reuse is just a particular case of development) keeps track of the intermediate states and the steps leading to the final artifacts. This paper shows that it is worth recording the reuse process for developing the operational requirements and not just the final product artifacts generated by the reuse process. The motivation behind this is that the syntactical constructs of the specification languages are generally not sufficient to trace the reuse process. Such traces are important for documentation purposes, for maintenance, for execution replay and for software evolution.