Variability Management in Embedded Product Line Analysis

Belategi, Lorea; Sagardui, Goiuria; Etxeberria, Leire

doi:10.1109/valid.2010.16

Cited by 7 publications

(5 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The aim of utility functions is to map the metric spaces onto a common scale [0, 1] representing the degree of satisfaction. Then the utility functions for different criteria are thus commensurate 6 . Reference levels are classically used to ensure this condition.…”

Section: Stage 2: Construction Of the Utility Functionsmentioning

confidence: 99%

“…• Completely Satisfactory the criteria is completely 6 It means that a same score -e.g. evaluation 0.3 -shall have the same interpretation whatever the criterion.…”

Section: Stage 2: Construction Of the Utility Functionsmentioning

confidence: 99%

“…The issues raised by safety assessment are apparent in many software-intensive systems [18,26,6]. In our context, the process of assessing and checking safety properties has to be applied to each (potential) solution (or variant).…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

A decision-making process for exploring architectural variants in systems engineering

Noir

Madelénat

Gailliard

et al. 2016

Proceedings of the 20th International Systems and Software Product Line Conference

View full text Add to dashboard Cite

In systems engineering, practitioners shall explore numerous architectural alternatives until choosing the most adequate variant. The decision-making process is most of the time a manual, time-consuming, and error-prone activity. The exploration and justification of architectural solutions is ad-hoc and mainly consists in a series of tries and errors on the modeling assets. In this paper, we report on an industrial case study in which we apply variability modeling techniques to automate the assessment and comparison of several candidate architectures (variants). We first describe how we can use a model-based approach such as the Common Variability Language (CVL) to specify the architectural variability. We show that the selection of an architectural variant is a multi-criteria decision problem in which there are numerous interactions (veto, favor, complementary) between criteria. We present a tooled process for exploring architectural variants integrating both CVL and the MYRIAD method for assessing and comparing variants based on an explicit preference model coming from the elicitation of stakeholders' concerns. This solution allows understanding differences among variants and their satisfactions with respect to criteria. Beyond variant selection automation improvement, this experiment results highlight that the approach improves rationality in the assessment and provides decision arguments when selecting the preferred variants.

show abstract

Section: Stage 2: Construction Of the Utility Functionsmentioning

confidence: 99%

“…• Completely Satisfactory the criteria is completely 6 It means that a same score -e.g. evaluation 0.3 -shall have the same interpretation whatever the criterion.…”

Section: Stage 2: Construction Of the Utility Functionsmentioning

confidence: 99%

See 1 more Smart Citation

A decision-making process for exploring architectural variants in systems engineering

Noir

Madelénat

Gailliard

et al. 2016

Proceedings of the 20th International Systems and Software Product Line Conference

View full text Add to dashboard Cite

show abstract

“…The embedded systems domain is frequently subject for variability and safety assessment issues [2,9,12]. From an industrial perspective, some papers report on their experience in managing safety in a product line context [3,13].…”

Section: Related Workmentioning

confidence: 99%

Tooling support for variability and architectural patterns in systems engineering

Degueule

Filho

Barais

et al. 2015

Proceedings of the 19th International Conference on Software Product Line

View full text Add to dashboard Cite

In systems engineering, the deployment of software components is error-prone since numerous safety and security rules have to be preserved. Furthermore, many deployments on different heterogeneous platforms are possible. In this paper we present a technological solution to assist industrial practitioners in producing a safe and secure solution out of numerous architectural variants. First, we introduce a pattern technology that provides correct-by-construction deployment models through the reuse of modeling artifacts organized in a catalog. Second, we develop a variability solution, connected to the pattern technology and based on an extension of the common variability language, for supporting the synthesis of model-based architectural variants. This paper describes a live demonstration of an industrial effort seeking to bridge the gap between variability modeling and model-based systems engineering practices. We illustrate the tooling support with an industrial case study (a secure radio platform).

show abstract

“…Model-driven development and software product line paradigms are integrated together to model and validate embedded software systems in [4]. Analysis method that takes into account scenarios, platform, and variability for embedded software product lines has been proposed.…”

Section: Related Workmentioning

confidence: 99%

Automatic Derivation of a Product Performance Model from a Software Product Line Model

Tawhid

Petriu

2011

2011 15th International Software Product Line Conference

View full text Add to dashboard Cite

We propose to integrate performance analysis in the early phases of the model-driven development process for Software Product Lines (SPL). We start with a multi-view UML model of the core family assets representing the commonality and variability between different products, which we call the SPL model. We add another perspective to the SPL model, annotating it with generic performance specifications expressed in the standard UML profile MARTE, recently adopted by OMG. The runtime performance of a product is affected by factors contained in the UML model of the product (derived from the SPL model), but also by external factors depending on the implementation and execution environments. The external factors not contained in the SPL model need to be eventually represented in the performance model. In order to do so, we propose to represent the variability space of different possible implementation and execution environments through a so called "performance completion (PC) feature model". These PC features are mapped to MARTE performancerelated stereotypes and attributes attached to the SPL model elements. A first model transformation realized in the Atlas Transformation Language (ATL) derives the UML model of a specific product with concrete MARTE annotations from the SPL model. A second transformation generates a Layered Queueing Network (LQN) performance model for the given product by applying an existing transformation named PUMA, developed in previous work. The proposed technique is illustrated with an e-commerce case study. A LQN model is derived for a product and the impact of different levels of secure communication channels on its performance is analyzed by using the LQN model.

show abstract

Variability Management in Embedded Product Line Analysis

Cited by 7 publications

References 26 publications

A decision-making process for exploring architectural variants in systems engineering

A decision-making process for exploring architectural variants in systems engineering

Tooling support for variability and architectural patterns in systems engineering

Automatic Derivation of a Product Performance Model from a Software Product Line Model

Contact Info

Product

Resources

About