Towards a Model-Driven Product Line Engineering Process

Bilic, Damir; Sundmark, Daniel; Afzal, Wasif; Wallin, Peter; Čaušević, Adnan; Amlinger, Christoffer; Barkah, Dani

doi:10.1145/3385032.3385043

Cited by 8 publications

(5 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This section discusses studies P285 [59], P377 [66], P503 [70], P129 [50], P218 [53], E8 [75], E53 [76], and E59 [77], which were assigned to the overall approaches/processes category. Several studies propose an overall approach and/or outline a process for automotive software product line development.…”

Section: Overall Approach/processmentioning

confidence: 99%

“…Bilic et al [77] identify and define a product line engineering (PLE) process at the engines control department of Volvo CE. For this purpose, they analyze the existing model-based systems engineering activities and discuss the implications of the migration from the current development process to a model-based PLE-oriented process.…”

Section: Overall Approach/processmentioning

confidence: 99%

“…In contrast, [70] remains fairly vague and does not contain a process description; instead, it provides an experience report. The work in [77] introduces a model-driven process using languages such as OVM and SysML. The other studies [59,66] propose frameworks for software product line development: [59] focuses on model-based development using techniques such as model transformation.…”

Section: Overall Approach/processmentioning

confidence: 99%

“…Compared to our classification schema (Section 2.2), neither approach [50,53,59,66,70,77] covers all activities. For instance, recovery and discovery is only supported by [59].…”

Section: Overall Approach/processmentioning

confidence: 99%

See 3 more Smart Citations

Managed Evolution of Automotive Software Product Line Architectures: A Systematic Literature Study

et al. 2022

View full text Add to dashboard Cite

The rapidly growing number of software-based features in the automotive domain as well as the special requirements in this domain ask for dedicated engineering approaches, models, and processes. Nowadays, software development in the automotive sector is generally developed as product line development, in which major parts of the software are kept adaptable in order to enable reusability of the software in different vehicle variants. In addition, reuse also plays an important role in the development of new vehicle generations in order to reduce development costs. Today, a high number of methods and techniques exist to support the product line driven development of software in the automotive sector. However, these approaches generally consider only partial aspects of development. In this paper, we present an in-depth literature study based on a conceptual model of artifacts and activities for the managed evolution of automotive software product line architectures. We are interested in the coverage of the particular aspects of the conceptual model and, thus, the fields covered in current research and research gaps, respectively. Furthermore, we aim to identify the methods and techniques used to implement automotive software product lines in general, and their usage scope in particular. As a result, this in-depth review reveals that none of the studies represent a holistic approach for the managed evolution of automotive software product lines. In addition, approaches from agile software development are of growing interest in this field.

show abstract

Section: Overall Approach/processmentioning

confidence: 99%

Section: Overall Approach/processmentioning

confidence: 99%

Section: Overall Approach/processmentioning

confidence: 99%

“…Compared to our classification schema (Section 2.2), neither approach [50,53,59,66,70,77] covers all activities. For instance, recovery and discovery is only supported by [59].…”

Section: Overall Approach/processmentioning

confidence: 99%

See 2 more Smart Citations

Managed Evolution of Automotive Software Product Line Architectures: A Systematic Literature Study

et al. 2022

View full text Add to dashboard Cite

show abstract

“…Recovering such information in systems with many features and sizable codebases is laborious, time-consuming, and inaccurate at best. Also, migration can be invasive, risky, and costly, especially hard to achieve under market pressure [48], [18], [36], [20], [17], [49].…”

Section: A Motivating Running Examplementioning

confidence: 99%

Seamless Variability Management with the Virtual Platform

Mahmood

Strüber

Berger

et al. 2021

2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE)

View full text Add to dashboard Cite

Customization is a general trend in software engineering, demanding systems that support variable stakeholder requirements. Two opposing strategies are commonly used to create variants: software clone&own and software configuration with an integrated platform. Organizations often start with the former, which is cheap, agile, and supports quick innovation, but does not scale. The latter scales by establishing an integrated platform that shares software assets between variants, but requires high up-front investments or risky migration processes. So, could we have a method that allows an easy transition or even combine the benefits of both strategies? We propose a method and tool that supports a truly incremental development of variantrich systems, exploiting a spectrum between both opposing strategies. We design, formalize, and prototype the variabilitymanagement framework virtual platform. It bridges clone&own and platform-oriented development. Relying on programminglanguage-independent conceptual structures representing software assets, it offers operators for engineering and evolving a system, comprising: traditional, asset-oriented operators and novel, feature-oriented operators for incrementally adopting concepts of an integrated platform. The operators record meta-data that is exploited by other operators to support the transition. Among others, they eliminate expensive feature-location effort or the need to trace clones. Our evaluation simulates the evolution of a real-world, clone-based system, measuring its costs and benefits.

show abstract