RequiLine: A Requirements Engineering Tool for Software Product Lines

Maßen, Thomas von der; Lichter, Horst

doi:10.1007/978-3-540-24667-1_13

Cited by 37 publications

(18 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…First, there are diVerent Xavors of techniques that solely focus on modeling variability with features, such as FODA [31], featureRSEB [24], Riebisch et al [45], Forfamel [2], RequiLine [37], and CBFM [18]. Second, there are diVerent Xavors of variability modeling with use cases, such as von der Maßen and Lichter [38], and Halmans and Pohl [25].…”

Section: Related Workmentioning

confidence: 99%

“…Over the past few years, several variability modeling techniques have been developed that are aimed to support variability management during product derivation, e.g., FODA [31], featureRSEB [24], Riebisch et al [45], Forfamel [2], RequiLine [37], Cardinality-Based Feature Modeling (CBFM) [18], von der Maßen and Lichter [38], Halmans and Pohl [25], ConIPF [28], COVAMOF [48], CONSUL/ PureϻVariants [13,44], GEARS [35], Koalish [3], OVM [43], VSL [9], van der Hoek et al [26], and Webber and Gomaa [23]. These techniques aim at representing the variability in a product family, in such a way that software engineers can manage variability more easily during product derivation.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Classifying variability modeling techniques

Sinnema

Deelstra

2007

Information and Software Technology

158

View full text Add to dashboard Cite

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Classifying variability modeling techniques

Sinnema

Deelstra

2007

Information and Software Technology

158

View full text Add to dashboard Cite

“…An initial prototype was proposed ConfigEditor [11]. ReqiLine [16] is a tool integrating feature modeling and requirements engineering. This tool allows the definition of various relationships between features but does not support cardinalities and the checking of models for consistency.…”

Section: Related Workmentioning

confidence: 99%

“…Some authors have proposed to change use case diagrams or class diagrams. Von der Maßen et al [16] propose the extension of UML Meta model by the adding of new relationships "option" and "alternative". Clauß proposes the use of stereotypes to express the variability in architecture models [19].…”

Section: Related Workmentioning

confidence: 99%

Model Driven Software Product Line Process for Service/Component-Based Applications

Ouali¹,

Kraïem²,

Al-Khanjari³

et al. 2020

JSW

View full text Add to dashboard Cite

Abstract:The software reuse becomes the key for companies to improve development costs, time-to-market, and software quality. The Software Product Line Engineering (SPLE) and the Model Driven Engineering (MDE) are two new forms of software reuse. Software product lines are recognized as a successful approach to reuse in many domains (cars, printers, phones…) and especially in software development. Software Product Line Engineering proposes a set of methods, techniques and a common set of software artifacts for the production of customized software products as atomic or composite services to be reused in SOA-based applications. The main purpose of MDE is to enhance productivity by maximizing compatibility between software systems and simplifying the process of design via reuse of standardized models and design patterns. This paper presents a process for the construction of software product lines using model driven techniques. This process is based on a combination of SPLE and the MDE throw the use of visual techniques for modeling product lines and model driven techniques. We have validated the approach with a common example of software product line to evaluate the approach (airline travel agency reservation system). We propose a tool that supports some software product line visual techniques and model driven techniques.

show abstract

“…Reference [36] discusses the derivation of test cases from use cases containing variability to verify if the implementation corresponds. In [37], the requirements verification for feature models is done by the use of logical expressions representing feature models.…”

Section: Software Product Line Approachesmentioning

confidence: 99%