Reusable SW Requirements Development Process: Embedded SW Industry Experiences

Embedded system development confronts to the needs of guaranteeing both short time release and the product's high quality. Emphasizing proactive SW reuse, it is necessary to identify reusable SW requirements for the product families. Once the standard features of product family are defined as reusable requirements, a derived model reuses most of them and adds little efforts on specifying new requirements. Its reuse can also smoothly make design models, implementation code, and corresponding test cases be reusable. This paper focuses on the systematic management process of developing reusable SW requirements for the embedded product families; we define the feature as the requirement unit; propose reusable requirements development process (RRDP); finally evaluate our process applying to industrial practices.

[1]  Armin Eberlein,et al.  Requirements Reuse and Feature Interaction Management , 2002 .

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

[3]  Paul Strooper.  Proceedings of the 2005 Australian Software Engineering Conference , 2004 .

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

[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]  Anthony Finkelstein.  Reuse of formatted specifications , 1987 .

[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]  Jaejoon Lee,et al.  Concepts and Guidelines of Feature Modeling for Product Line Software Engineering , 2002, ICSR.

[9]  Jaejoon Lee,et al.  FORM: A feature-;oriented reuse method with domain-;specific reference architectures , 1998, Ann. Softw. Eng..

[10]  Peter Kilpatrick,et al.  Feature-Guided Architecture Development for Embedded System Families , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[11]  Wolfgang Schröder-Preikschat,et al.  Functional and non-functional properties in a family of embedded operating systems , 2005, 10th IEEE International Workshop on Object-Oriented Real-Time Dependable Systems.

[12]  Howard B. Reubenstein,et al.  Automated Acquisition of Evolving Informal Descriptions , 1990 .

[13]  David Chenho Kung,et al.  Status report: requirements engineering , 1993, IEEE Software.

[14]  Peter Kilpatrick,et al.  Weaving behavior into feature models for embedded system families , 2006 .

[15]  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.

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

[17]  Jürgen Börstler,et al.  Marrying Features and Use Cases for Product Line Requirements Modeling of Embedded Systems , 2004 .

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

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

[20]  John A. McDermid,et al.  Ten steps towards systematic requirements reuse , 2008, Requirements Engineering.

[21]  Matthias Weber,et al.  Managing variability and reuse of features and requirements for large and complex organizational structures , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).