Abstract
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.
Article PDF
Similar content being viewed by others
Avoid common mistakes on your manuscript.
References
Lim WC. Effects of Reuse on Quality Productivity, and Economics, IEEE Software, 1994; 11(5): 23–30.
Sommerville I. Software Engineering (5th Edition), Addison Wesley, ISBN 0-201-42765-6. 1996
SPC (1992) Software Productivity Consortium Reuse Adoption Guidebook, Version 01.00.03, SPC-92051-CMC, November, 1992
Biggerstaff T, Ritcher C. Reusability framework, assessment and directions, IEEE Software, 1987; 41(3): 41–49 March
Guerrieri E. Case study: Digital’s application generator. IEEE Software, 1994; 11(5): 95–96
Joos R. Software reuse at Motorola, IEEE Software, 11(5): 42–47
Kelly TP, Lam W, Whittle BR. Diary of a domain analyst: a domain analysis case-study from avionics, In Proceedings of IFIP Working Groups 8.1/13.2 Conference, Domain Knowledge for Interactive System Design, Geneva, May 8–10, 1996
Lam W, Whittle BR, McDermid J, Wilson S. An integrated Approach to Domain Analysis and Reuse for Engineering Complex Systems, In Proceedings of International IEEE Symposium and Workshop on Engineering of Computer-Based Systems (ECBS ’96), Friedrichafen, Germany, March 11–15, 1996
Lam W, Whittle BR. A Taxonomy of Domain-Specific Reuse Problems and their Resolution—Version 1.0, Software Engineering Notes 21(5): 72–77 1996
Whittle BR, Lam W, Kelly TP. A Pragmatic Approach to Reuse Introduction in an Industrial-Setting, In Proceedings of the International Workshop on Systemmatic Reuse, Liverpool John-Moores University, Springer-Verlag, 1996
Whittle BR, Vickers AJ, Lam W, McDermid J, Hill JA, Rimmer R, Essam P. Structuring Requirements Specifications for Reuse. International Journal on Applied Software Technology 1(3–4), 1995
Finkelstein A. Reuse of formatted requirements specifications. Software Engineering Journal, 1988; 3(5): 186–197
Maiden N, Sutcliffe A. Exploiting reusable specification through analogy, Communications of the ACM, 1993; 35(4): 55–64
Lam W. Reasoning about requirements from past cases, PhD thesis, Kings College, University of London, 1994
Bolton D, Jones S, Til D, Furber D, Green S. Using domain knowledge in requirements capture and formal specification construction, In Jirotka, M. and Goguen J. (Eds.), Requirements Engineering: Social and Technical Issues, Academic Press, London, 1994
Reubenstein HB. Automated Acquisition of Evolving Informal Descriptions, Report No. AI-TR 1205, Artificial Intelligence Laboratory, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139 1990
Miriyala K, Harandi TH. Automatic derivation of formal software specifications from informal descriptions. IEEE Transactions on Software Engineering, 1991; 17(10): 1126–1142
Ryan K, Mathews B. Matching conceptual graphs as an aid to requirements reuse, In Proceedings of the IEEE International Symposium on Requirements Engineering, ISBN 0-8186-3120-1, page 112–120, 1993
Griss ML, Favaro J, Walton P. Managerial and Organisational Issues—Starting and Running a Software Reuse Program, In Software Reusability, eds W. Schaefer, R. Prieto-Diaz and M. Matsumoto, Ellis Horwood, Chichester, GB, 1994; pp. 51–78
WISR. Proceedings of the 7th Annual Workshop on Software Reuse, St. Charles Illinois, August 28–30, 1995
Prieto-Diaz R. (1990) Domain analysis: an introduction, ACM Software Engineering Notes, 1990; 15(2): 47–54
Wartik S, Prieto-Diaz P. Criteria for comparing reuse-oriented domain analysis approaches. International Journal of Software Engineering and Knowledge Engineering, 1992; 2(3): 403–431
Gomaa H. Reusable software requirements and architectures for families of systems. Journal of Systems and Software, 1995; 28: 189–202
Tracz W. DSSA (Domain-Specific Software Architecture) pedagogical example, ACM SIGSOFT Software Engineering Notes, 1995; 20(3): 49–62
Tracz W, Coglianese L, Young P. A domain-specific software architecture engineering process outline, ACM SIGSOFT Software Engineering Notes, 1993; 18(2): 40–49
WSRET. Proceedings of the 4th International Workshop on Software Reuse Education and Training, Morgantown, West Virginia, 14–18th August, 1995
Bate IJ et al. Technology Transfer: An Integrated ‘Culture-Friendly’ Approach, In Proceedings of Workshop on Technology Transfer, 18th International Conference on Software Engineering, Berlin, Germany, 25–29 March, 1996
Vickers AJ, Whittle BR, McDermid JA. Technology Transfer by Case Study; An Experience Report, Presented at 3rd International Conference on Concurrent Engineering & Electronic Design Automation, Poole, 1996
Kramer J. Generalisations are false? In Proceedings of the IEEE International Symposium on Requirements Engineering, ISBN 0-8186-3221-1, IEEE Computer Society Press, Los Alamitus, CA 1993
Mili H, Mili F, Mili A. Reusing Software: issues and research directions, IEEE Transactions on Software Engineering, 1995; 21(6): 528–561
Littman DC. Modeling human expertise in knowledge engineering: some preliminary observations. International Journal of Man-machine Studies, 1997; 26: 81–92
Spanoudakis G, Constantopoulos P. Analogical Reuse of Requirements Specifications: A Computational Model, Applied Artificial Intelligence (to appear) 1996
Carbonell JG. Learning by analogy: Formulating and generalising plans from past experience. In Michalski RS, Carbonell JG, Mitchell TM (Eds.) Machine Learning: an Artificial Intelligence approach, Los Altos, CA, Kaufmann, 1983
Coplien JO, Schmidt DC. Eds. Pattern Languages of Program Design, Addison-Wesley, ISBN 0-201-6073-4, 1995
Wray T. The everyday risks of playing it safe New Scientist, September 8, pp. 61–65, 1988
Osterweil L. Software processes are software too, In Proceedings of the International Conference on Software Engineering, IEEE Computer Society Press, Los Alamitus, CA 1987
Curtis B, Kellner MI, Over J. Process modelling, Communications of the ACM, 35(9): 91–100, 1992
McChesney IR. Towards a classification scheme for software process modeling approaches Information and Software Technology, 1995; 37(7): 363–374
Holt AW, Ramsey HR, Grimes JD. Co-ordination System Technology as the Basis for a programming environment, Electrical Communication, 1983; 57(4): 307–314
Lam W. Process reuse using a template approach: a casestudy from Avionics. Software Engineering Notes 22(2): 35–38, 1997
Fafchamps D. Organisational factors and reuse, IEEE Software, 1994; 11(5): 31–41
Frakes WB, Isoda S. Success Factors for systematic reuse, IEEE Software, 1994; 11(5): 15–19
Fuchs NE, Schwitter R. Attempt to Controlled English (ACE), CLAW 96, First International Workshop on Controlled Language Applications, University of Leuven, Belgium, March 1996
Software Reuse Success Stories prepared by: Reuse Acquisition Action Team (RAAT), Association for Computing Machinery (ACM) SIG on Ada Reuse Working Group, 1994
Tracz W. DSSA (Domain-Specific Software Architecture) pedagogical example. ACM SIGSOFT Software Engineering Notes, 1995; 20(3): 49–62
Lam W, McDermid JA, Vickers AJ. Reuse Through Standardisation: Towards Industry-Standard Engine Control Software, In Proceedings of the 1996 Avionics Conference, Ramada Hotel Heathrow, UK 20–21st November, 1996. (Publication available from ERA Technology, Cleeve Road, Leatherhead, Surrey, KT22 7SA, UK), 1996
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Lam, W., McDermid, J.A. & Vickers, A.J. Ten steps towards systematic requirements reuse. Requirements Eng 2, 102–113 (1997). https://doi.org/10.1007/BF02813029
Issue Date:
DOI: https://doi.org/10.1007/BF02813029