Ten steps towards systematic requirements reuse

Author

Lam, W. ; McDermid, J.A. ; Vickers, A.J.

Author_Institution

Dept. of Comput. Sci., York Univ., UK

fYear

1997

Firstpage

6

Lastpage

15

Abstract

Reusability is widely suggested to be a key to improving software development productivity and quality. It has been further argued that reuse at the requirements level can significantly increase reuse at the later stages of development. 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 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

Keywords

aerospace control; aerospace engines; control systems; formal specification; software quality; software reusability; systems analysis; BR700 family; Rolls-Royce University Technology Centre; Rolls-Smiths Engine Controls Ltd.; aero-engine control systems; engine controllers; software development productivity; software quality; systematic requirements reuse; Computer science; Control systems; Electrical equipment industry; Engines; Industrial control; Productivity; Programming; Project management; Quality management; Software development management;

fLanguage

English

Publisher

ieee

Conference_Titel

Requirements Engineering, 1997., Proceedings of the Third IEEE International Symposium on

Conference_Location

Annapolis, MD

Print_ISBN

0-8186-7740-6

Type

conf

DOI

10.1109/ISRE.1997.566834

Filename

566834