Ten steps towards systematic requirements reuse

Reusability is widely suggested to be a key to improving software development productivity and quality 1,2]. It has been further argued that reuse at the requirements level can significantly increase reuse at the later stages of development 3,4]. However, there is little evidence in the literature to suggest that requirements reuse is widely practised. This paper describes ten practical steps towards systematic requirements reuse based on work at the Rolls-Royce Systems and Software University Technology Centre (UTC) for Rolls-Smiths Engine Controls Ltd (RoSEC) in the domain of aero-engine control systems. We believe these steps have made a significant overall contribution to the 50% reuse figure quoted by the management at RoSEC for current projects within the BR700 family of engine controllers.