Developing long-term stable product line architectures

Boss, Birgit; Müller, Andréas; Thums, Andreas; Acharya, Rajneesh; Schmid, Klaus

doi:10.1145/2362536.2362551

Cited by 14 publications

(3 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This involves supporting a huge variety of product functionalities and an even bigger number of system and software variants to meet all the customer needs. The PS-EC engine control software is developed as a software product line, and was introduced in more detail by Tischer et al in [31].…”

Section: Contextmentioning

confidence: 99%

Reverse engineering variability in an industrial product line

El-Sharkawy

Jyoti

Krafczyk

et al. 2018

Proceedings of the 22nd International Systems and Software Product Line Conference - Volume 1

Self Cite

View full text Add to dashboard Cite

Ideally, a variability model is a correct and complete representation of product line features and constraints among them. Together with a mapping between features and code, this ensures that only valid products can be configured and derived. However, in practice the modeled constraints might be neither complete nor correct, which causes problems in the configuration and product derivation phases. This paper presents an approach to reverse engineer variability constraints from the implementation, and thus improve the correctness and completeness of variability models.We extended the concept of feature effect analysis [22] to extract variability constraints from code artifacts of the Bosch PS-EC large-scale product line. We present an industrial application of the approach and discuss its required modifications to handle non-Boolean variability and heterogeneous artifact types.

show abstract

Section: Contextmentioning

confidence: 99%

Reverse engineering variability in an industrial product line

El-Sharkawy

Jyoti

Krafczyk

et al. 2018

Proceedings of the 22nd International Systems and Software Product Line Conference - Volume 1

Self Cite

View full text Add to dashboard Cite

show abstract

“…Cloning of classes and components can be also deliberately used as a variability mechanism if their later similarity is expected to be low [42]. In this case, the rationale for using Cloning is the high effort and low benefit of using other variability mechanisms such as Conditional Compilation for the dissimilar code.…”

Section: Cloningmentioning

confidence: 99%

Variability mechanisms and lessons learned in practice

Zhang

Duszynski

Becker

2016

Proceedings of the 1st International Workshop on Variability and Complexity in Software Design

View full text Add to dashboard Cite

In the design of complex and variable software systems, one of the key steps is to select the variability mechanism that defines how variable features are realized on the design and code level. Although different variability mechanisms were invented and applied in practice for decades, there are not many studies that compare these mechanisms based on practical experiences. This paper characterizes and compares seven variability mechanisms in terms of their techniques, binding time, granularity, and further aspects. It provides experiences of their usage, the practical benefits and challenges, as well as discusses existing solutions to the challenges based on related studies and our practice in industry

show abstract

“…Tischer presented a form of domain decomposition that he called conceptual architecture for embedded electronic systems [22]. Beside the static view, the conceptual architecture gives two additional views: The dynamic view which focuses on the detailed system state control and scheduling behaviour and the organizational view which documents the relationship between every software product line artifact unit and individual organizational units.…”

Section: Software Product Line Assessmentmentioning

confidence: 99%

Towards a co-evolution model for software product lines based on cladistics

Benlarabi¹

2014

2014 IEEE Eighth International Conference on Research Challenges in Information Science (RCIS)

View full text Add to dashboard Cite

The evolution of a software product line is more challenging than the evolution of a single product, because its artifacts depend on many products. If a change is not well studied, it can break the integrity of the reference architecture of the software product line and all the derived products.Hence, when dealing with evolution, the understanding of change and its impact must be the most important activity.Biology is the science which studied evolution the most.Therefore it was necessary for us to understand evolution in biology in order to handle evolution in software product lines.This paper presents our approach to deal with change understanding in software product line using co-evolution analysis which was used in biology to understand how organisms influence each other during their evolution over time. Similarly to biological co-evolution, the co-evolution of artifacts of a software product line consists on analyzing how the evolution of an artifact influences the evolution of the others. The input data used in our approach are extracted from the history of changes that happened to each version of the software product. Our objective is to establish a co evolution model for software product lines using Cladistics classification which illustrates the evolution of a population through an evolutionary tree.

show abstract

Developing long-term stable product line architectures

Cited by 14 publications

References 17 publications

Reverse engineering variability in an industrial product line

Reverse engineering variability in an industrial product line

Variability mechanisms and lessons learned in practice

Towards a co-evolution model for software product lines based on cladistics

Contact Info

Product

Resources

About