Systematic requirements recycling through abstraction and traceability

Ad-hoc recycling between requirements documents of product variants is a major source of requirements defects. We present an approach for systematic requirements recycling based on a combination of abstraction (in terms of a template) and traceability (between requirements). The main features of our approach are the use of conceptual models to determine relationships necessary for correct recycling and the focus on minimizing link selling. This approach can also be used to develop abstraction and traceability guidelines tailored to other application domains and traceability goals, such as change or project management.

[1]  B. Ramesh,et al.  Issues in the development of a requirements traceability model , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[2]  Neil A. M. Maiden,et al.  Domain modeling for reuse , 1994, Proceedings of 1994 3rd International Conference on Software Reuse.

[3]  Mikael Lindvall,et al.  Practical implications of traceability , 1996 .

[4]  Balasubramaniam Ramesh,et al.  Factors influencing requirements traceability practice , 1998, CACM.

[5]  W. Lam,et al.  A case-;study of requirements reuse through product families , 1998, Ann. Softw. Eng..

[6]  L'ubor Sesera,et al.  Analysis Patterns , 2000, SOFSEM.

[7]  Sara Jones,et al.  Technology transfer for reuse: a management model and process improvement framework , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[8]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[9]  Ian F. Alexander,et al.  Towards recyclable system requirements , 2002, Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems.

[10]  Constance L. Heitmeyer,et al.  Hardware/Software Co-Design and Co-Validation Using the SCR Method , 1999 .

[11]  Klaus Pohl,et al.  Process-Centered Requirements Engineering , 1996 .

[12]  Stuart R. Faulk.  Product-line requirements specification (PRS): an approach and case study , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[13]  Neil A. M. Maiden,et al.  The Domain Theory for Requirements Engineering , 1998, IEEE Trans. Software Eng..

[14]  Antje von Knethen.  A trace model for system requirements changes on embedded systems , 2001, IWPSE '01.

[15]  Jacob L. Cybulski,et al.  Requirements Classification and Reuse: Crossing Domain Boundaries , 2000, ICSR.

[16]  Siegfried Bauer,et al.  Requirements archaeology: from unstructured information to high quality specifications [in the automotive industry] , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[17]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[18]  Antje von Knethen,et al.  Change-Oriented Requirements Traceability: Support for Evolution of Embedded Systems , 2002, ICSM.

[19]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[20]  Balasubramaniam Ramesh,et al.  Implementing requirements traceability: a case study , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[21]  Klaus Pohl.  A process centered requirements engineering environment , 1994 .

[22]  Mikael Lindvall.  A study of traceability in object-oriented systems development , 1994 .

[23]  Ted J. Biggerstaff,et al.  Software reusability: vol. 1, concepts and models , 1989 .