A Case Study on the Evolution of a Component-based Product...

A Case Study on the Evolution of a

Component-based Product Line

Wolfgang Heider1, Michael Vierhauser2, Daniela Lettner1, Paul Grünbacher1

1 Christian Doppler Lab. for ASE,

Johannes Kepler University 2 Siemens VAI Metals Technologies

Linz, Austria

August 23, 2012

August 23, 2012 Christian Doppler Laboratory for Automated Software Engineering

Context, Motivation, Goal

• Maintenance and evolution of product lines

is increasingly complex

• We developed a product line engineering tool suite,

the DOPLER tool suite

• We observed the evolution of this industrial product line

while it was refactored for industrial use cases by Siemens VAI

Analyze developer challenges and tool support requirements

Involved Artifacts

Component InterfaceDependency

Involved Artifacts

Component InterfaceProduct Line

FeatureDependency

Solution SpaceProblem Space

Product LineRelease

Involved Artifacts

FeatureDependency

Product LineRelease

Involved Artifacts

FeatureDependency

Derived Product

Product LineRelease

Generated Executable Product

ComponentsComponentsComponents

generate

Involved Artifacts

FeatureDependency

Derived Product

Product LineRelease

generate

Research Questions

Goal: Developer challenges and tool support requirements

RQ1: Which basic development activities

are performed by developers

to evolve the product line?

RQ2: Which types of change impact analyses

are performed by developers?

RQ3: Which tool features are needed to perform these analyses?

… a project for transitioning the research tool to industrial settings

• Siemens VAI project

• Siemens managers and business users were involved as stakeholders

• 4 hired developers

• Researchers advised and observed development

• 30 person-months of professional development

• 6 derived products that need to be maintained

The Case

Siemens VAI Project to Refactor the DOPLER Tool Suite

v2.0 v2.10 Δ

LoC (measured with cloc 1.53) 192,427 154,924 -20%

Java Classes 1,902 1,776 -6%

Eclipse Plugins, Features 61 101 +66%

Research Process

Changes relevant to PL evolution

TeamForge Artifacts

(epics, stories, tasks)

Daily SCRUM Meeting Protocols

(action items, open issues)

Development

Activities

Trace Information Model & Desired Trace Links

categorize

select

Impact

Analyses

categorize

select

derive

map to

Scenarios

derive derive

Research Process

TeamForge Artifacts

Development

Activities

categorize

select select

- Add / change / remove component

- Add / change / remove interface

- Add / remove dependency

- Define release

Research Process

TeamForge Artifacts

Development

Activities

categorize

select

Impact

Analyses

categorize

select

- Which components are affected?

- Which interfaces are changed?

- Which dependencies are added?

- Which features do change?

- Which product files need to be adapted?

Research Process

TeamForge Artifacts

Development

Activities

categorize

select

Impact

Analyses

categorize

select

map to

Scenarios

- Add feature

- Remove feature

- Define feature variability

- Maintain architecture

- Maintain assets

Research Process

TeamForge Artifacts

Development

Activities

Trace Information Model & Desired Trace Links

categorize

select

Impact

Analyses

categorize

select

derive

map to

Scenarios

derive derive

Changed artifact type Analyzed artifact type

Research Process

TeamForge Artifacts

Epic: Refactor Configuration Workflow

Story: Add additional authentication

Task: Define authentication extension point

Action Item: Develop authentication interface

Open Issues: How to adapt old authentication?

Which products need which authentication?

Impediment: The fu*beep* build server is offline!

Research Process

TeamForge Artifacts

select select

Add Smartcard Authentication

Research Process

TeamForge Artifacts

Development

Activities

categorize

select select

- Change configuration UI plugin

- Add authentication interface

- Add authentication plugins

Research Process

TeamForge Artifacts

Development

Activities

categorize

select

Impact

Analyses

categorize

select

- Which plugins are affected

by the new authentication?

- Which product files need to be adapted

to include the new authentication?

Research Process

TeamForge Artifacts

Development

Activities

categorize

select

Impact

Analyses

categorize

select

map to

Scenarios

- Add authentication feature

- Define authentication variability

Research Process

TeamForge Artifacts

Development

Activities

categorize

select

Impact

Analyses

categorize

select

map to

Scenarios

While defining feature variability,

the configuration UI plugin was changed

and developers analyzed which product files need to be adapted?

Resulting Trace Information Model

FeatureDependency

Derived Product

Product LineRelease

FeatureDependency

Derived Product

Product LineRelease

reuse5

FeatureDependency

Derived Product

Product LineRelease

FeatureDependency

Derived Product

Product LineRelease

Developers need to see the effects of changes

on features and feature variability

FeatureDependency

Derived Product

Product LineRelease

The tool presents features related to a component under change.

FeatureDependency

Derived Product

Product LineRelease

The tool presents affected features and violated feature variability

(if dependencies between components are added or removed).

FeatureDependency

Derived Product

Product LineRelease

Developers need to see the impact of changes

on derived products

FeatureDependency

Derived Product

Product LineRelease

The tool presents already derived products or ongoing product derivations

based on a previous PL release to analyze the possibility of product updates.

Summary / Future work

Before we developed approaches and solutions …

• We conducted a case study to find industrial challenges

• We observed the evolution of an industrial product line

• We derived scenarios of impact analysis as requirements

• Our approach to provide impact analysis:

Regression testing with variability models

[Heider et al. @SPLC2012]

A Case Study on the Evolution of a Component-based Product...

Documents

Copernicus Space Component Status & Evolution › sites › default › files › 6_ICC21... · 2018-01-30 · ESA UNCLASSIFIED - For Official Use Copernicus Space Component Status

PatEvol - A Pattern Language for Evolution in Component-based Software Architectures

Combination Testing Strategies - soberit.hut.fi€¦ · Combination testing strategies identify test combinations by combining values of different test object parameters based on

Technical specification - soberit.hut.fi · Technical specification ... Lönnberg Corrected obsolete communication description in chapter 3. ... Lönnberg Required communication between

Product Data Management - soberit.hut.fi · Title: Microsoft PowerPoint - PDM_051019.ppt Author: Asko Martio Created Date: 10/20/2005 11:33:35 AM

WIGOS Space-Component Vision: anticipated evolution Picture · PDF fileWIGOS Space-Component Vision: anticipated evolution Picture of 2040 --Development of a Vision of WIGOS Space-based

A Pattern Language for Evolution Reuse in Component-Based ... · A Pattern Language for Evolution Reuse in Component-Based Software Architectures Abstract Context: Modern software

The Evolution of Phonetic Capabilities: Causes Constraints ...pubman.mpdl.mpg.de/pubman/item/escidoc:2351030:3/component/es… · The Evolution of Phonetic Capabilities: Causes Constraints

Characterising Precipitate Evolution in Multi-component

Stellar migrations and metal flows – Chemical evolution of the … · 16 hours ago · the chemical evolution of the inner galaxy regions, and (ii) an accreted component of metal-poor

Maintainability and Agile development - soberit.hut.fi · 2 ISO 9126 Software Quality Characteristics ISO/IEC 9126 Functionality Portability Reliability Maintainability Efficiency

Star Formation and Evolution - Ursinus Collegewebpages.ursinus.edu/dnagy/physics101q/lectures/11St… · · 2011-11-05Star Formation and Evolution Low and Medium Mass Stars Component

MLCask: Efﬁcient Management of Component Evolution in

The Impact of Component Modularity on Design Evolution ... Files/08-038_187f1243-7d1… · Component Modularity on Design Evolution: Evidence from the Software Industry Alan MacCormack

Static Component Evolution with Extensible Modules

Perspectives in Plant Ecology, Evolution and Systematics · Seipel et al. / Perspectives in Plant Ecology, Evolution and Systematics 20 (2016) 46–55 47 component of a proactive

JANUARY 2018 THE EVOLUTION OF ETF CLEARING …/media/Files/Downloads/WhitePapers/... · and evolution of the ETF marketplace. ... NAV, component securities, share weightings, and

A Component-Based and Aspect-Oriented Model for … · A Component-Based and Aspect-Oriented Model for Software Evolution ... with CORBA middleware. ... A component-based and aspect-oriented

The Evolution of Multi-component Visual Signals in Darters ... · The evolution of multi-component visual signals in darters (genus Etheostoma) Jennifer M. GUMM*, Tamra C. MENDELSON

Extending the Socio-economics of Software Architecturewicsa2012.soberit.hut.fi/wp/assets/WICSAECSA-Sutcliffe.pdf · Extending the Socio-economics of Software Architecture Alistair