Ten steps towards systematic requirements reuse

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.

[1]  T. Biggerstaff,et al.  Reusability Framework, Assessment, and Directions , 1987, IEEE Software.

[2]  J. Carbonell.  Learning by Analogy: Formulating and Generalizing Plans from Past Experience , 1983 .

[3]  Ali Mili,et al.  Reusing Software: Issues and Research Directions , 1995, IEEE Trans. Software Eng..

[4]  David C. Littman.  Modelling Human Expertise in Knowledge Engineering: Some Preliminary Observations , 1987, Int. J. Man Mach. Stud..

[5]  Brian Mathews,et al.  Matching conceptual graphs as an aid to requirements re-use , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[6]  Will Tracz,et al.  DSSA (Domain-Specific Software Architecture): pedagogical example , 1995, SOEN.

[7]  Wayne C. Lim,et al.  Effects of reuse on quality, productivity, and economics , 1994, IEEE Software.

[8]  Stewart Green,et al.  Using domain knowledge in requirements capture and formal specification construction , 1994 .

[9]  W. Lam.  Process reuse using a template approach: a case-study from avionics , 1997, SOEN.

[10]  Wing-Hong Lam.  Reasoning about requirements from past cases , 1994 .

[11]  Wing Lam,et al.  Diary of a domain analyst: a domain analysis case-study from avionics , 1996 .

[12]  Kanth Miriyala,et al.  Automatic Derivation of Formal Software Specifications From Informal Descriptions , 1991, IEEE Trans. Software Eng..

[13]  Sadahiro Isoda,et al.  Success factors of systematic reuse , 1994, IEEE Software.

[14]  Hassan Gomaa,et al.  Reusable software requirements and architectures for families of systems , 1995, J. Syst. Softw..

[15]  Leon J. Osterweil,et al.  Software processes are software too , 1987, ISPW.

[16]  George Spanoudakis.  Analogical Reuse of Requirements Specifications: A Computational Model , 1996, Appl. Artif. Intell..

[17]  Ruben Prieto-Diaz,et al.  Criteria for Comparing Reuse-Oriented Domain Analysis Approaches , 1992, Int. J. Softw. Eng. Knowl. Eng..

[18]  W. Lam,et al.  An integrated approach to domain analysis and reuse for engineering complex systems , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[19]  Will Tracz,et al.  A domain-specific software architecture engineering process outline , 1993, SOEN.

[20]  Danielle Fafchamps.  Organizational factors and reuse , 1994, IEEE Software.

[21]  Anthony Finkelstein.  Reuse of formatted specifications , 1987 .

[22]  Ian Sommerville,et al.  Software engineering (5th ed.) , 1995 .