Modelling requirements variability across product lines

Bühne, Stan; Lauenroth, Kim; Pohl, Klaus

doi:10.1109/re.2005.45

Cited by 72 publications

(61 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Jaring and Bosch [21] have also examined the difference sources of variability and argued that the type of variability depends on dependencies between points of variation. This observation is consistent with the work of Buhne et al [22] in which they used Use Cases to model requirement variability. However, representations such as use cases [22] and feature diagrams [23] have been observed by Liaskos et al [19] to be inadequate for expressing intentional and contextual variability.…”

Section: Related Worksupporting

confidence: 91%

Specifying Monitoring and Switching Problems in Context

Salifu

Nuseibeh

2007

15th IEEE International Requirements Engineering Conference (RE 2007)

View full text Add to dashboard Cite

Section: Related Worksupporting

confidence: 91%

Specifying Monitoring and Switching Problems in Context

Salifu

Nuseibeh

2007

15th IEEE International Requirements Engineering Conference (RE 2007)

View full text Add to dashboard Cite

“…Hierarchical product lines [58] are an example of an approach that can be applied when there is a family with a broad domain scope focusing on a number of product categories. Bühne et al [59] extend an existing meta-model for variability modeling to structure product lines into a hierarchy. Reiser and Weber [60] suggest to model complex product lines with a hierarchy of feature models called multi-level feature trees.…”

Section: Related Workmentioning

confidence: 99%

Supporting distributed product configuration by integrating heterogeneous variability modeling approaches

Galindo

Dhungana

Rabiser

et al. 2015

Information and Software Technology

View full text Add to dashboard Cite

Context: In industrial settings products are developed by more than one organization. Software vendors and suppliers commonly typically maintain their own product lines, which contribute to a larger (multi) product line or software ecosystem. It is unrealistic to assume that the participating organizations will agree on using a specific variability modeling technique-they will rather use different approaches and tools to manage the variability of their systems. Objective: We aim to support product configuration in software ecosystems based on several variability models with different semantics that have been created using different notations. Method: We present an integrative approach that provides a unified perspective to users configuring products in multi product line environments, regardless of the different modeling methods and tools used internally. We also present a technical infrastructure and a prototype implementation based on web services. Results: We show the feasibility of the approach and its implementation by using it with the three most widespread types of variability modeling approaches in the product line community, i.e., feature-based, OVM-style, and decision-oriented modeling. To demonstrate the feasibility and flexibility of our approach, we present an example derived from industrial experience in enterprise resource planning. We further applied the approach to support the configuration of privacy settings in the Android ecosystem based on multiple variability models. We also evaluated the performance of different model enactment strategies used in our approach. Conclusions: Tools and techniques allowing stakeholders to handle variability in a uniform manner can considerably foster the initiation and growth of software ecosystems from the perspective of software reuse and configuration.

show abstract

“…At the requirement engineering level, how to create the right requirements assets of the PL and dependencies among them to develop the right products have been extensively studied [7] [25], but understanding the derivation process itself has received little attention.…”

Section: Related Workmentioning

confidence: 99%

RED-PL, a Method for Deriving Product Requirements from a Product Line Requirements Model

Djebbi

Salinesi²

2007

Advanced Information Systems Engineering

View full text Add to dashboard Cite

Abstract. Software product lines (SPL) modeling has proven to be an effective approach to reuse in software development. Several variability approaches were developed to plan requirements reuse, but only little of them actually address the issue of deriving product requirements. Indeed, while the modeling approaches sell on requirements reuse, the associated derivation techniques actually focus on deriving and reusing technical product data. This paper presents a method that intends to support requirements derivation. Its underlying principle is to take advantage of approaches made for reuse PL requirements and to complete them by a requirements development process by reuse for single products. The proposed approach matches users' product requirements with PL requirements models and derives a collection of requirements that is (i) consistent, and (ii) optimal with respect to users' priorities and company's constraints. The proposed methodological process was validated in an industrial setting by considering the requirement engineering phase of a product line of blood analyzers.

show abstract

Modelling requirements variability across product lines

Cited by 72 publications

References 6 publications

Specifying Monitoring and Switching Problems in Context

Specifying Monitoring and Switching Problems in Context

Supporting distributed product configuration by integrating heterogeneous variability modeling approaches

RED-PL, a Method for Deriving Product Requirements from a Product Line Requirements Model

Contact Info

Product

Resources

About