Feature-Oriented Evolution of Automation Software Systems in Industrial Software Ecosystems

Hinterreiter, Daniel; Prähofer, Herbert; Linsbauer, Lukas; Grünbacher, Paul; Reisinger, Florian; Egyed, Alexander

doi:10.1109/etfa.2018.8502557

Cited by 24 publications

(14 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For instance, Figure 2 shows an example of a feature model for the well-known Pick-and-Place Unit (PPU) system. The diagram shows mandatory and optional features of the initial (base) platform, as well as extensions to the platform added in 10 evolution steps (Hinterreiter et al, 2018; Vogel-Heuser et al, 2014). Feature-oriented development (FOSD; Apel et al, 2012) has been proposed to map features with their realization.…”

Section: Research Challengesmentioning

confidence: 99%

“…Our research thus aims at supporting the development and evolution in industrial automation product lines at the level of features. In a long-term research cooperation with our industry partner Keba AG we have been developing and exploring a feature-oriented development approach for industrial automation product lines to address key research challenges in industrial automation ecosystems (Hinterreiter et al, 2018; Lettner et al, 2014a, 2014b; Schultis et al, 2013). In this paper we thus present the tool-supported FORCE 2 approach, which integrates a feature-oriented development approach (Rabiser et al, 2018) with a variation control system (VCS; Linsbauer et al, 2017) to support feature-level evolution.…”

Section: Introductionmentioning

confidence: 99%

“…In a conference publication (Hinterreiter et al, 2018) we outlined the industrial challenges and usage scenarios of our approach. This article significantly extends this earlier paper in several directions and provides the following contributions: (i) We describe the key elements and operations of FORCE 2 , including details of their implementation; (ii) we evaluate the functional correctness of our approach based on application scenarios from the Pick-and-Place Unit (PPU) system (Vogel-Heuser et al, 2014); and (iii) we report results from a comprehensive industrial case study investigating the usefulness and scalability of our approach in the context of the large-scale KePlast product line of our industry partner.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Supporting feature-oriented evolution in industrial automation product lines

Hinterreiter

Linsbauer

Feichtinger

et al. 2020

Concurrent Engineering

Self Cite

View full text Add to dashboard Cite

In the domain of industrial automation companies nowadays need to serve a mass market while at the same time customers demand highly customized solutions. To tackle this problem, companies frequently define software product lines (SPLs), which allow to automatically derive and further customize individual solutions based on a common platform. SPLs rely on defining common and variable platform features together with mappings, which define how the features are realized in implementation artifacts. In concurrent engineering such a feature-oriented process is challenged by the evolution of features, the complexity of feature-to-artifact mappings, and the diversity of the implementation artifacts. To address these challenges this paper introduces an approach supporting feature-oriented development and evolution in industrial SPLs. We outline the key elements and operations of our approach, including an implementation in a development environment. We report results of evaluating our approach regarding functional correctness, usefulness, and scalability based on a case study of a Pick-and-Place Unit (PPU) and an industrial case system.

show abstract

Section: Research Challengesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Supporting feature-oriented evolution in industrial automation product lines

Hinterreiter

Linsbauer

Feichtinger

et al. 2020

Concurrent Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Many companies in industrial automation domain nowadays need to serve a mass market while at the same time customers demand individual customer-specific solutions [40]. These customizations often apply to individual products.…”

Section: Variability In Software Ecosystemsmentioning

confidence: 99%

“…To handle this problem, development is frequently organized in SECOs. Hinterreiter et al [40] proposed an approach for supporting feature-oriented, distributed development and evolution in industrial SECOs. Their approach allowed to share new or updated features by transferring them to other product lines in the ecosystem.…”

Section: Variability In Software Ecosystemsmentioning

confidence: 99%

A study on dynamic aspects variability in the SOLAR educational software ecosystem

Coutinho

Bezerra

2020

J Braz Comput Soc

View full text Add to dashboard Cite

A Software Ecosystem (SECO) refers to a collection of software products with some degree of symbiotic relationship. SOLAR is a Virtual Learning Environment (VLE) that enables the publication of courses and interaction with them among its various users. In this context, SOLAR SECO emerges, where diverse situations of software evolution and maintenance are part of its development process. The aim of this paper is to discuss the dynamic variability of SOLAR educational software ecosystem and software modeling. As an example, dynamic variability aspects of the feature model of SOLAR VLE discussion forum functionality were discussed, one of the most widely used services within SOLAR SECO. As a major conclusion of this work, we identified that the use of the contextual feature diagram allows the study of the dynamic aspects of a system, even more supported by tools to support automatic measurement collection.

show abstract