Reusing single system requirements from application family requirements

Reuse and requirements engineering are very important for efficient and successful systems development. However there are many open issues for performing them well in practice, especially raise of requirements. We present a new approach to reusing requirements based on application families i.e. several systems in a given problem domain. In contrast to precious approaches, an application family model in our approach consists of a pool of requirements (linked in a lattice structure), a domain model and a set of discriminants (a special kind of requirement that differentiate one system from another). We focus on how to make an efficient and clean selection of the requirements for a new system from an application family model. We have developed a method for solving this problem and a prototypical tool for supporting it. The method and the prototype were successfully developed under a study contract for ESA (European Space Agency). We present a case study, where we generated commanding requirements for an individual mission from an application family model of commanding requirements for spacecraft control operating systems. As a consequence, we propose this approach for reusing requirements based an application families.

[1]  Ivar Jacobson,et al.  Software Reuse: Architecture, Process And Organization For Business Success , 1998, Proceedings. Technology of Object-Oriented Languages. TOOLS 26 (Cat. No.98EX176).

[2]  Daniel Hoffman,et al.  Commonality and Variability in Software Engineering , 1998, IEEE Softw..

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

[4]  Neil A. M. Maiden,et al.  Exploiting reusable specifications through analogy , 1992, CACM.

[5]  A SimosMark Organization domain modeling (ODM) , 1995 .

[6]  Philippe Massonet,et al.  GRAIL/KAOS: An Environment for Goal-Driven Requirements Engineering , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[7]  Mike Mannion,et al.  SMARTRe requirements: writing reusable requirements , 1995, Proceedings of the 1995 International Symposium and Workshop on Systems Engineering of Computer-Based Systems.

[8]  Hermann Kaindl,et al.  The missing link in requirements engineering , 1993, SOEN.

[9]  Mike Mannion,et al.  Using Viewpoints to Define Domain Requirements , 1998, IEEE Softw..

[10]  Anthony Finkelsteiin,et al.  Re-use of formatted requirements specifications , 1988 .

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

[12]  Hermann Kaindl,et al.  How to identify binary relations for domain models , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[13]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[14]  B. Cheng,et al.  Specification matching for software reuse: a foundation , 1995, SSR '95.

[15]  Martin L. Griss,et al.  Integrating feature modeling with the RSEB , 1998, Proceedings. Fifth International Conference on Software Reuse (Cat. No.98TB100203).

[16]  Hermann Kaindl,et al.  A case study of decomposing functional requirements using scenarios , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[17]  Philippe Massonet,et al.  Analogical reuse of requirements frameworks , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[18]  Hermann Kaindl,et al.  A practical approach to combining requirements definition and object‐oriented analysis , 1997, Ann. Softw. Eng..