Reusable Subsystems from an Overall System Specification

Firstly, decomposition of multifunctional embedded systems into subsystems implies a long list of relevant criteria to be taken into consideration. Secondly, reuse of such subsystems is already done in practice but is often just performed for code or lacks a systematic approach. In this paper, we describe a method for defining and outlining subsystems from the overall system requirements and specification, then extracting a subsystem by tracing all its relevant artifacts, and finally we describe the steps for its reuse within a new surrounding system that is being developed.

[1]  Rebecca E. Grinter.  From local to global coordination: lessons from software reuse , 2001, GROUP.

[2]  Eva Geisberger,et al.  Requirements Engineering Reference Model (REM) , 2007, Softwaretechnik-Trends.

[3]  Rubén Prieto-Díaz.  Implementing faceted classification for software reuse , 1991, CACM.

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

[5]  Klaus Pohl,et al.  Software Product Line Engineering - Foundations, Principles, and Techniques , 2005 .

[6]  Michael Pidd,et al.  Simulation model reuse: definitions, benefits and obstacles , 2004, Simul. Model. Pract. Theory.

[7]  Barbara Paech,et al.  Component-based product line engineering with UML , 2001, Addison Wesley object technology series.

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

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

[10]  Rubén Prieto-Díaz,et al.  Status report: software reusability , 1993, IEEE Software.

[11]  Rubén Prieto Díaz.  Status Report: Software Reusability. , 1993 .

[12]  JORGE L. DÍAZ-HERRERA.  EMBEDDED SYSTEMS PRODUCT LINES : PROCESS AND MODELS , 2000 .

[13]  Manfred Broy,et al.  Specification and development of interactive systems: focus on streams, interfaces, and refinement , 2001 .

[14]  Rob C. van Ommering.  Beyond Product Families: Building a Product Population? , 2000, IW-SAPF.

[15]  Linda Rising,et al.  Patterns: a way to reuse expertise , 1999, IEEE Commun. Mag..

[16]  Charles W. Krueger,et al.  Software reuse , 1992, CSUR.

[17]  Colin Atkinson,et al.  Component-based product line development: the KobrA Approach , 2000, SPLC.

[18]  Paul Clements,et al.  Attribute-Driven Design (ADD), Version 2.0 , 2006 .

[19]  R. Prieto-Diaz,et al.  Implementing faceted classification for software reuse , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[20]  Philippe Krutchen,et al.  Architectural blueprints--the '4+1' view model of software architecture , 1995 .

[21]  Alberto L. Sangiovanni-Vincentelli,et al.  Electronic-System Design in the Automobile Industry , 2003, IEEE Micro.

[22]  Edsger W. Dijkstra,et al.  Structured programming , 1972, A.P.I.C. Studies in data processing.

[23]  David Lorge Parnas,et al.  On the Design and Development of Program Families , 2001, IEEE Transactions on Software Engineering.

[24]  Philippe Kruchten,et al.  Architecture blueprints—the “4+1” view model of software architecture , 1995, TRI-Ada '95.

[25]  Luciano Lavagno,et al.  Metropolis: An Integrated Electronic System Design Environment , 2003, Computer.

[26]  Hassan Gomaa,et al.  A reuse-oriented approach for structuring and configuring distributed applications , 1993, Softw. Eng. J..

[27]  Jan Gerben Wijnstra,et al.  Component Oriented Platform Architecting for Software Intensive Product Families , 2002 .

[28]  F. Robert A. Hopgood.  "Structured Programming, " by O.-J. Dahl, E. W. Dijkstra and C. A. R. Hoare (Book Review) , 1974, Int. J. Man Mach. Stud..

[29]  Змеев Олег Алексеевич,et al.  Расширение модели UML 2 для поддержки описаний вариантов использования , 2007 .

[30]  Klaus Schmid,et al.  PuLSE: a methodology to develop software product lines , 1999, SSR '99.

[31]  Felix Bachmann,et al.  The Architecture Based Design Method , 2000 .

[32]  D. L. Parnas,et al.  On the criteria to be used in decomposing systems into modules , 1972, Software Pioneers.

[33]  Kim Lauenroth,et al.  Why is it not Sufficient to Model Requirements Variability with Feature Models? 1 , 2004 .

[34]  David Lorge Parnas,et al.  Software aging , 1994, Proceedings of 16th International Conference on Software Engineering.

[35]  Andreas Hein,et al.  Configuring Software Product Line Features , 2001, FICS.

[36]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..