Using Requirements Management Tools in Software Product Line Engineering: The State of the Practice

Beuche, Danilo; Birk, Andreas; Dreier, Heinrich; Fleischmann, Andreas; Galle, Heidi; Heller, G. S.; Janzen, Dirk; John, Isabel; Kolagari, Ramin Tavakoli; Maßen, Thomas von der; Wolfram, Andreas

doi:10.1109/spline.2007.4339258

Cited by 7 publications

(9 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Other studies agree with ours in that there is a lack of information about RE tools and information gathering requires great effort [22], along with the fact that a certain degree of subjective interpretation that is difficult to mitigate is still possible even though in principle the evaluation criteria for assessing RE tools may seem to be well defined [24]. Like us, Schmid et al [22] also experienced a high diversity of responsiveness when contacting the tool vendors.…”

Section: Research Contributionssupporting

confidence: 82%

“…The authors examined the issues, trends, and challenges confronted by researchers and practitioners during the process of seeking, uncovering, acquiring, and elaborating requirements for computer based systems. Beuche et al [24] suggested important requirements that must be observed if RE tools are to be usefully applied to product lines. Four notorious RE tools were evaluated on the basis of these requirements in their daily industrial use.…”

Section: Re Tool Surveysmentioning

confidence: 99%

“…Zowghi and Coulin [23] claim that a wide variety of tools have been developed and used to support elicitation, regardless of whether or not they have been specifically designed for it, which may be related to our findings on the relative maturity of the RE tools as regards elicitation features. Beuche et al [24] took the requirements catalogue for single product developments written by Homann et al [2] as a basis, and adapted it in order to make it suitable for product line development, while Toval et al [15] depicted the features needed for their reuse-centered RE tool. In both cases, the results of their evaluation are highly biased towards product lines features and requirements reuse features respectively, and it is not therefore possible to compare these results with those achieved in our study.…”

Section: Research Contributionsmentioning

confidence: 99%

See 2 more Smart Citations

Requirements engineering tools: Capabilities, survey and assessment

Gea

Nicolás

Fernández-Alemán

et al. 2012

Information and Software Technology

View full text Add to dashboard Cite

Section: Research Contributionssupporting

confidence: 82%

Section: Re Tool Surveysmentioning

confidence: 99%

Section: Research Contributionsmentioning

confidence: 99%

See 1 more Smart Citation

Requirements engineering tools: Capabilities, survey and assessment

Gea

Nicolás

Fernández-Alemán

et al. 2012

Information and Software Technology

View full text Add to dashboard Cite

“…What does this mean for the development process and the different development steps respectively? For the requirements, this means that they have to be formulated in a generic way (Heinä nen et al, 2006;Beuche et al, 2007).…”

Section: Integrating Variability In the Automotive Sw Development Promentioning

confidence: 99%

A development methodology for variant-rich automotive software architectures

Leitner

Mader

Kreiner

et al. 2011

Elektrotech. Inftech.

View full text Add to dashboard Cite

Ever accelerating product cycles together with multi-discipline engineering processes are typical for safety-critical automotive embedded systems development. This demands for both efficient and effective development and reuse strategies.A development process following the V-model incorporating model-driven prototyping and development, safety engineering, and verification (unit testing, integration testing, cosimulation, etc.) is commonly found.Product line engineering enables fast and efficient product configuration through systematic reuse. The V-model has been extended by an integrated product line engineering environment for automotive embedded systems. This ensures the consistent configuration across system architecture description (EAST-ADL2), model driven development (Matlab/Simulink), software component deployment on an ECU network (AUTOSAR-based), Simulink-based software unit testing, Simulink-based software integration testing, and co-simulation model variants. Using the automotive architecture description language EAST-ADL2 enables the integration of safety engineering aspects.Keywords: variability management; automotive software development; extended V-model Eine Entwicklungsmethode fü r variantenreiche automotive Softwarearchitekturen.Hohe Marktdynamik fü hrt zu immer schneller werdenden Produktentwicklungszyklen automotiver eingebetteter Systeme. Der multidisziplinä re Charakter in der Entwicklung derartiger sicherheitsgerichteter Systeme stellt hohe Anforderungen an eine effiziente und effektive Wiederverwendungsstrategie.Das V-Modell ist ein weitverbreiteter Entwicklungsprozess in dieser Branche. Es beinhaltet typischerweise modellgetriebene Entwicklung, Sicherheitstechnik und Verifikation (Komponententest, Integrationstest, Co-simulation etc.)Produktlinienorientierte Entwicklung verspricht schnelle und effiziente Produktentwicklung durch systematische Wiederverwendung und gestattet konsistente Ansteuerung aller Varianten.In dieser Arbeit wird das V-Modell durch eine Produktlinienumgebung fü r automotive eingebettete Systeme erweitert. Damit wird die konsistente Konfiguration der Systemarchitekturbeschreibung (EAST-ADL2), der modellgetriebenen Entwicklung (Matlab/Simulink), der Softwarekomponentenverteilung auf den Steuergerä ten (AUTOSAR-basierend), der Simulink-basierenden Komponentenund Integrationstests und der Co-simulationmodellvarianten sichergestellt.Durch die Verwendung der Architekturbeschreibungssprache EAST-ADL2 ist es mö glich, auch sicherheitsrelevante Aspekte zu integrieren.Schlü sselwö rter: Variantenmanagement; automotive Software-Entwicklung; erweitertes V-Modell

show abstract

“…The next step in the effort towards a new generation software product line was the adaptation of the requirement management and planning facilities [4]. As both projects were originally following agile development paradigms, they featured the according process for eliciting, managing and realising both functional and non-functional requirements.…”

Section: From Requirements Management To Feature and Variation Managementioning

confidence: 99%

An experience report on the incremental adoption and evolution of an SPL in eHealth

Strobl

Bernhart

Grechenig

2010

Proceedings of the 2010 ICSE Workshop on Product Line Approaches in Software Engineering

View full text Add to dashboard Cite

This work presents an experience report on the evolutionary development of a software product line (SPL) in the eHealth domain. The effort was triggered by the concurrent development of two similar products and the ambition to reduce redundant development and quality assurance. The result is a scalable base for a complex, highly adaptable information system. This system is required to be applicable in multiple business domains and diverging environments ranging from large scale hospitals to single practitioner clinics.During this effort we were able to extract the common denominator in the form of core assets from existing applications specific to a medical field. For customisations well defined variation points were developed. Our solution allows for easy implementation of medical documentation requirements compared to tedious development of new applications from scratch. It significantly reduced the necessary development effort and time to market. The resulting core documentation platform can be used for an arbitrary medical field completely eliminating the dependence on the specific customer domain.

show abstract

Using Requirements Management Tools in Software Product Line Engineering: The State of the Practice

Cited by 7 publications

References 0 publications

Requirements engineering tools: Capabilities, survey and assessment

Requirements engineering tools: Capabilities, survey and assessment

A development methodology for variant-rich automotive software architectures

An experience report on the incremental adoption and evolution of an SPL in eHealth

Contact Info

Product

Resources

About